ArangoImport local IP connection refused

My Environment

ArangoDB Version: 3.4.2-1
Storage Engine: RocksDB
Deployment Mode: Single Server
Deployment Strategy: init.d
Configuration:
Infrastructure: Linode
Operating System: Debian 9
Total RAM in your machine: 1GB
Disks in use: 1
Used Package: official Debian package (via apt)

Component, Query & Data
Affected feature: arangoimport

Steps to reproduce

run arangoimport or arangoimport --server.endpoint tcp://<IP_ADDRESS>:8529 with additional arguments following the 2019 graph course
provide password

(Same steps providing the server's global IP works, however.)
Problem:
ERROR Could not connect to endpoint 'tcp://<IP_ADDRESS>:8529', database: '_system', username: 'root'
FATAL Could not connect to 'http+tcp://<IP_ADDRESS>:8529' 'connect() failed with #111 - Connection refused''

Expected result: Similar output to arangosh which seems to have no problem. ArangoDB is running on the same machine, and thus I expect localhost to work without hiccups.

please note that <IP_ADDRESS> is the BIND IP which makes processes bind all possible IPs the system offers. To connect from the client, you need to specify one of the ips listed when invoking ifconfig

I did a few tests with some interesting results in bold.
I bound the server to tcp://<IP_ADDRESS>:8529 and then tried to connect to it:
arangoimport & arangosh
✔ tcp://<IP_ADDRESS>:8529
✔ tcp://localhost:8529
❌ tcp://[::1]:8529
✔ tcp://<IP_ADDRESS>:8529 (lan ip of the machine the server runs on)
✔ tcp://<IP_ADDRESS>:8529 (funny, but seems to work)
❌ tcp://[::]:8529 (<IP_ADDRESS> of IPv6)

Then I stopped the server and restarted it bound to tcp://<IP_ADDRESS>:8529:
arangoimport & arangosh
✔ tcp://<IP_ADDRESS>:8529
✔ tcp://localhost:8529
❌ tcp://[::1]:8529
❌ tcp://<IP_ADDRESS>:8529
✔ tcp://<IP_ADDRESS>:8529
❌ tcp://[::]:8529

With the server bound to tcp://[::1]:8529 (the localhost equivalent in IPv6):
arangoimport
❌ tcp://<IP_ADDRESS>:8529
❌ tcp://localhost:8529
✔ tcp://[::1]:8529
❌ tcp://<IP_ADDRESS>:8529
❌ tcp://<IP_ADDRESS>:8529
✔ tcp://[::]:8529
arangosh
❌ tcp://<IP_ADDRESS>:8529
✔ tcp://localhost:8529 (why does it work here but not in arangoimport?)
✔ tcp://[::1]:8529
❌ tcp://<IP_ADDRESS>:8529
❌ tcp://<IP_ADDRESS>:8529
✔ tcp://[::]:8529

With the server bound to tcp://[::]:8529 (the <IP_ADDRESS> equivalent in IPv6):
arangoimport & arangosh
✔ tcp://<IP_ADDRESS>:8529
✔ tcp://localhost:8529
✔ tcp://[::1]:8529
✔ tcp://<IP_ADDRESS>:8529 (it's an IPv4 address, not sure if this is expected or not)
✔ tcp://<IP_ADDRESS>:8529
✔ tcp://[::]:8529

@wraybowling What endpoint is the server bound to? Is it tcp://<IP_ADDRESS>:8529 in your case? If so, then connecting to it with a client tool such as arangoimport using the same endpoint should work. If the server is bound to tcp://[::1]:8529 then try that exact endpoint in the client tool. If nothing works, then try tcp://[::]:8529 for both perhaps.

For the server <IP_ADDRESS> means indeed bind to any address (also addresses that pop up later).
For the client <IP_ADDRESS> is not well defined. Actually the RFC only defines <IP_ADDRESS> as source. The problem is that this might work on version of the operating system and then suddenly stops to work (see for example stackoverflow: https://superuser.com/questions/557168/cant-access-ip-0-0-0-0).
@Simran-B we should explicit state that "<IP_ADDRESS>" is only supported in the server and not in the client, as it might or might not work.


refactor: Move clasp * --help test to one test with many assertions

Move clasp * --help test to one test with many assertions.
Helps with #593.

This actually isn't helping yet:
Test --help for each function
    ✓ should print help for clasp * --help (85076ms)

LGTM, but I'm not sure it would be much faster. Looks like it's timing out on some of the builds.
Can you put in test-level timeout: https://mochajs.org/#test-level
Setting this.timeout(0) should just disable the timeout.
Also perhaps, looking forward, we can skip these tests and skip the coverage on the--help functionality?

Even after the refactor it's still running clasp <command> --help once for each expectHelp call, and that's probably where the time is coming from.
More generally, I'm not a fan of tests that are checking for exact strings to be returned. I think you should be free to completely change the help text without it breaking tests.

I disagree. I think that changing the help texts should break tests, making us more conscious of making those changes.
That being said, I'm fine with skipping all of these tests for now and taking the coverage hit, as it will help with velocity.

IMO the tests should be confirming that the "contract" is met; that the program does what it claims it will do. The contact for the --help is that we will show some relevant help text for the command, not that we'll show a very specific piece of text. I think the point of these tests is to ensure that every command has help text, not to prevent the help text from changing. When testing a command line tool like this it may be hard to test one without testing the other, but I think we should strive to separate those when possible.

Closing:

This PR isn't helping
The tests need to be more useful to be refactored as Eric mentions.


Hrtim common

@burrbull

Sorry I do not know to read this from the memory map but I believe HRTIM_TIMA.SET[1-4]R is supposed to be different from the ones in the other timers. Since they all have different neighbors. I just want to make sure that is still the case here

Is it possible to get that nice web render thing directly from a PR, for easier comparison with the register tables in the RMs?

Is it possible to get that nice web render thing directly from a PR, for easier comparison with the register tables in the RMs?

You can do it locally with:
make html

or
CRATES=stm32g4 make html

Sorry I do not know to read this from the memory map but I believe HRTIM_TIMA.SET[1-4]R is supposed to be different from the ones in the other timers. Since they all have different neighbors. I just want to make sure that is still the case here
I believe it is the same thing with RSTR and possibly more event subscription related places

Accordingly to RM (if it does not lie) there are SET[12]R, RST[12]R which are identical and RSTR which is different on G4 and identical on F3 and F7.

Accordingly to RM (if it does not lie) there are SET[12]R, RST[12]R [...]

Sorry my bad.
What I was thinking of was the TIMEVNT[1-9] bits. They are described in Table 219 of RM0440. It would help from a users perspective if those names were direcly in the register fields descriptions so one does not have to look it up through the table. However I understand if that is out of scope for stm32-rs.
Example:
HRTIM_TIMA

TIMEVNT[1] - CMPB1 Event from HRTIM_TIMB's CMP1
TIMEVNT[2] - CMPB2
TIMEVNT[3] - CMPC2
etc...

HRTIM_TIMB

TIMEVNT[1] - CMPA1
TIMEVNT[2] - CMPA2
TIMEVNT[3] - CMPC3
etc...

Again I understand if that is out of scope for stm32-rs.

Is it possible to get that nice web render thing directly from a PR, for easier comparison with the register tables in the RMs?

You can do it locally with:
make html

or
CRATES=stm32g4 make html

Thanks, will try

What I was thinking of was the TIMEVNT[1-9] bits. They are described in Table 219 of RM0440.

Makes sense. But I'd leave this for another PR.

@usbalbin Look at https://github.com/stm32-rs/stm32-rs/tree/hrtim-set
Is it what you expect?

Sorry, must have looked in the wrong RM. Bit 31 and 0 in RSTR for timer A-E are TIMFCMP2 and TIMFCMP1 wich checks out.
However for timer F RSTR should be identical to E's with the exception of bit 31 and 0 which should instead be TIMECMP2 and TIMECMP1 (see 27.5.38 in RM0440)


Patch "createmanagedcluster" annotation on Cluster Claims

Summary of Changes
I've validated that this patch skips cluster import if you don't specify --import and that it imports if you set --import.

/lgtm


Enhance docs for mac users

As discussed in the community meeting today the docs can either be made more beginner-friendly by covering the "Create or bring a Kubernetes cluster" section in the installation of keptn for different operating systems separately.
Being a mac user I faced issues setting up OpenShift and k3s(requiring more storage than my system has).
My suggestion:
For the time being, Create or bring a Kubernetes cluster can contain a table having a different OS and process that is working fine in that OS until we have a solid doc to provide installation for the system that does not use arch x64. For Example - k3d works fine with mac m1(without doing any changes in memory or CPU requirements)
cc- @DavidPHirsch @agardnerIT @bradmccoydev

I have assigned this to you, @SuperAayush .  Why don't you create a PR with what you know.  I'm not sure if I agree that it belongs in "Create or bring a Kubernetes cluster" since this is not really related to k8s per se.  You might want to look at what is in https://keptn.sh/docs/1.0.x/install/troubleshooting/ ,  which has some other information about installation issues related to specific platforms, etc.  That is written more as small targeted tidbits, which are easier to provide than a comprehensive table about each O/S and option.  And it already includes some other info related to OpenShift and resources.


user12986714: Watch andrei\d*+ciobanu.wordpress

user12986714 requests the watch of the watch_keyword andrei\d*+ciobanu\.wordpress. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

andrei\d*+ciobanu\.wordpress has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Eliah Kagan in Charcoal HQ


Makefile help

Document developer facing make targets in convenient make help
Inspired by https://victoria.dev/blog/how-to-create-a-self-documenting-makefile/

Looks like this:
$ make help
debug-test-etcd      Run temporary etcd pod for debug
demo-failover        Execute failover demo
demo-roundrobin      Execute round-robin demo
deploy-full-local-setup Deploy full local multicluster setup
deploy-gslb-cr       Apply Gslb Custom Resources
deploy-gslb-operator Deploy k8gb operator
deploy-test-apps     Deploy testing workloads
destroy-full-local-setup Destroy full local multicluster setup
dns-tools            Run temporary dnstools pod for debugging DNS issues
help                 Show this help

Signed-off-by: Yury Tsarev<EMAIL_ADDRESS>

good idea

good idea


Using "pump" with/without return

The docs suggests "using pump" for error handling:
https://github.com/gulpjs/gulp/blob/master/docs/why-use-pump/README.md
The example (unlike most Gulp tasks) does not return pump, but this works great and cleaned up my error reporting. The pump example:
gulp.task('compress', function (cb) {
  pump([
      gulp.src('lib/*.js'),
      uglify(),
      gulp.dest('dist')
    ],
    cb
  );
});

Not returning pump fails for gulp-imagemin though:
https://github.com/sindresorhus/gulp-imagemin/issues/285
The author patiently replied that the pump example is incorrect, and Gulp tasks should always return.
That seems to be true, but the developer experience is worse when returning pump because the console fills with junk (the reason I like pump is not having that happen):
https://github.com/sindresorhus/gulp-imagemin/issues/285#issuecomment-350189618
Are "correct" and "good" at odds here? Seems like an area to improve in Gulp or module integration.

pump doesn't return anything and you are using it correctly.  That module is broken, sorry.

@brendanfalkowski I noticed you have reportErrors as the callback in the linked code.  You need to actually pass the task's cb as that argument or call it within reportErrors (but that isn't within the closure).

I'd take everything sindre says with a grain of salt.  Pretty sure he hasn't looked at gulp for the past 5 years...

@phated — Thanks for the tips, much appreciated.
I think I'm missing your point on callbacks. My errorHandler() function is imported and assigned as a global var. This seems to work fine:
gulpfile.js
var errorHandler = require('./gulp/error-handler.js');

gulp.task('css', function () {
    var task = config.task.css;

    pump([
        gulp.src(task.src),
        sass(task.sassOptions),
        gulp.dest(task.dest
    ], errorHandler);
});

error-handler.js
module.exports = function (error) {
    // Read `error` properties
    // Log something useful
};

Logged message (my function)

— — — — — — — — — —
Modified with callback
var errorHandler = require('./gulp/error-handler.js');

gulp.task('css', function (errorHandler) {
    var task = config.task.css;

    pump([
        gulp.src(task.src),
        sass(task.sassOptions),
        gulp.dest(task.dest
    ], errorHandler);
});

Logged message (not my function)

— — — — — — — — — —
I'm not sure if there's a sync/async benefit from reading here:
https://github.com/gulpjs/gulp/blob/master/docs/API.md#gulptaskname--deps--fn
Otherwise using the callback seems to output the whole error object instead of using the function.
I'm sure I'm not doing that right, but what's the benefit of the callback?

When using pump you need to call the callback given to your task by gulp,
usually by passing it as the second argument to pump.
In your first example you're never calling it (and, in fact, never even
giving it a name) so gulp doesn't know your task is finished. (You're also
not returning anything, so gulp has no idea what your task is trying to do)
On Dec 12, 2017 10:24 PM, "Brendan Falkowski"<EMAIL_ADDRESS>wrote:

@phated https://github.com/phated — Thanks for the tips, much
appreciated.
I think I'm missing your point on callbacks. My errorHandler() function
is imported and assigned as a global var. This seems to work fine:
gulpfile.js
var errorHandler = require('./gulp/error-handler.js');
gulp.task('css', function () {
var task = config.task.css;
pump([
    gulp.src(task.src),
    sass(task.sassOptions),
    gulp.dest(task.dest
], errorHandler);

});
error-handler.js
module.exports = function (error) {
// Read error properties
// Log something useful
};
Logged message (my function)
[image: screen shot 2017-12-12 at 10 19 13 pm]
https://user-images.githubusercontent.com/214924/33924373-a96ada5e-df8a-11e7-8144-932268922616.png
— — — — — — — — — —
Modified with callback
var errorHandler = require('./gulp/error-handler.js');
gulp.task('css', function (errorHandler) {
var task = config.task.css;
pump([
    gulp.src(task.src),
    sass(task.sassOptions),
    gulp.dest(task.dest
], errorHandler);

});
Logged message (not my function)
[image: screen shot 2017-12-12 at 10 18 14 pm]
https://user-images.githubusercontent.com/214924/33924410-d3059836-df8a-11e7-81f6-d09427b594a1.png
— — — — — — — — — —
I'm not sure if there's a sync/async benefit from reading here:
https://github.com/gulpjs/gulp/blob/master/docs/API.md#
gulptaskname--deps--fn
Otherwise using the callback seems to output the whole error object
instead of using the function.
I'm sure I'm not doing that right, but what's the benefit of the callback?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gulpjs/gulp/issues/2058#issuecomment-351295462, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAQsZYLC-YsEEZVLlOSA3vpPvBgVW4dSks5s_22XgaJpZM4Q-K2r
.

@brendanfalkowski It seems like you are missing some JS fundamentals but hopefully @terinjokes' response helps you.
However, we are not a support forum and I feel like we've outlined your issue enough so I'm going to have to lock this.  If you need further help, I'd suggest opening this on StackOverflow.


ImageLayer doesn't update when OverviewMap control is displayed

Hi all,
When you use an ImageLayer with ImageWMS source and an OverviewMap control, there is something strange :
while the overview map is not displayed, the image layer is correctly updated when you scroll or move the map.
But after dislaying it once, the overview map image is updated but not the main map image when you scroll or move the map. All server calls are done, image is returned, but not displayed. I did some trys on Firefox and Chrome, with OL 5.2.0 and 4.6.x, and seen the same bug.
Here's a feedle with it, just zoom and unzoom with overview map displayed to see the bug :
http://jsfiddle.net/Inikaam/7qkjprfa/7/

So, I assume it has something to do with calling the source from two different "maps". Once you open the overview with your original code it is constantly firing the loadstart and loadend events, solved it by having two separate sources.
Here is the updated code, works okay so far:
`var source = new ol.source.ImageWMS({
url: 'https://ahocevar.com/geoserver/wms',
params: {'LAYERS': 'ne:ne'},
serverType: 'geoserver',
crossOrigin: 'anonymous'
});
var source2 = new ol.source.ImageWMS({
url: 'https://ahocevar.com/geoserver/wms',
params: {'LAYERS': 'ne:ne'},
serverType: 'geoserver',
crossOrigin: 'anonymous'
});
source2.on('imageloadstart', function(evt) {
console.log('loadingStart2');
});
source2.on('imageloadend', function(evt) {
console.log('loadingEnd2');
});
source.on('imageloadstart', function(evt) {
console.log('loadingStart');
});
source.on('imageloadend', function(evt) {
console.log('loadingEnd');
});
var ovMap = new ol.control.OverviewMap(
{
collapsed: true,
collapsible: true,
layers: [
new ol.layer.Image({
source: source2
})
]
}
);
var map = new ol.Map({
layers: [
new ol.layer.Image({
source: source
})
],
controls: [ovMap],
target: 'map',
view: new ol.View({
extent: [14471533.80, -5465442.18, 18256396.49, -4865942.28],
center: [16363965.145, -5165692.23],
projection: 'EPSG:3857',
maxZoom: 22,
minZoom: 6,
zoom: 8
})
});`

Hi IsSexy,
Thanks for your help, it works fine.
But it seems i must always duplicate all layers i want to display in overview map, especially if i want see the same layers on both overview and main map. It's a problem when i add or remove layers dynamically.
I run with it for now, but thats need to be fix i think.

I'll do a deep dive into their code later today, I agree that it shouldn't be a problem, and with larger data sets I feel duplicating sources could cause issues.


Correct class to remove vector (circle)

Remove vector (circle) from input bar to allow padding to be reduced

@harbassan


changeThreadColor() callback parameter listed as optional, but errors out if not included

According to the docs, the callback parameter for changeThreadColor() is optional, but it throws a whole mess of errors if not included.

Looks like you're right, thanks for catching this.  Any chance you want to submit a PR it to be properly optional?  We offer lots of emoji hearts in return.

Sure! #367


How to enable live-audio on DJI FPV Goggles V1

I have installed this package, but I don't know how to enable it

It should just work, if you have a full size air unit on the other end.
It can't work with Vistas, as they don't have a microphone.

Thank you.
I'm using RunCam Link Wasp now, I'll try it on DJI air unit again.
从 Windows 版邮件https://go.microsoft.com/fwlink/?LinkId=550986发送
发件人: Joonas @.>
发送时间: 2022年10月31日 18:54
收件人: @.>
抄送: @.>; @.>
主题: Re: [fpv-wtf/wtfos] How to enable live-audio on DJI FPV Goggles V1 (Issue #33)
It should just work, if you have a full size air unit on the other end.
It can't work with Vistas, as they don't have a microphone.
―
Reply to this email directly, view it on GitHubhttps://github.com/fpv-wtf/wtfos/issues/33#issuecomment-1296916680, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A2X5DOUDT6JO7LSZLWZZ2DDWF6QNXANCNFSM6AAAAAARS5SIEQ.
You are receiving this because you authored the thread.Message ID: @.***>

Could someone share the pinage of the audio? I tried live-audio without sucess :(

Pinage? You just need to plug in headphones, install the package on your goggles V1 and use a full size Air Unit.
@gmoska if you have a problem, please open another issue with a detailed description of what you did, what devices were involved and what happened.
Closing this issue as the original problem seems to have been using a vista.


Consider create datetime on ClientSecret

Client secrets are created and we can have more then one.     I was thinking that our developers may create several client secrets.      It would be nice to know when a secret was created.   My current solution is to add a time stamp to the description property which works but isn't ideal.
I am willing to submit a pull request on this if you agree its wroth adding.

This would mean a schema change - and we try to avoid that..
I will put it in backlog.

Do you have any idea how much hair pulling i have had from the schema changes in 1.x -> 2.0 upgrade?
I kind of thought you guys loved schema changes :)

Can we get migration steps in this time

Migrations are the concern of the hosting application. This is because fundamentally EF migrations don't support library style schemas.

We'll add this on the 3.0 milestone, since that will be an expected big (schema) change.
@leastprivilege also is mentioning a "last access" time so people know which secrets are stale.

Also, perhaps a LastAccessedDate

I keep meaning to try to add this as a clientproperty to the client validate.    I just couldn't decide if lastaccessdate counted with failed login or just with successful logins.
we apparently need this for GDPR compliance.

I am planning to add this to the user db to list successful logins as I use that to establish termination date, which is what I need for consent receipt for GDPR.  BTW, I implemented consent receipt on a ASP.NET identity / idsvr4 OP. But I have not found any good way to have user consume the data as yet,

But in the event of client credentials Grant type its not a user and you would need to store lastaccessdate of the client itself.
what about refresh token usage do you think it best to store that on the user or the client or the client access grant can't remember that table I am mobile right now.

GDPR should only apply to user? or am I missing something here?
If you are talking about impersonation, I just refuse to allow that as it is far beyond GDPR thinking.
I don't think that there is anything that requires tracking refresh usage, altho I never thought much about it.

It is possible that this is a requirement from a customer I am not privileged to that information.
I was told anyone or anything accessing data must be logged.  In the event of a client its the developer who we must log who's data they accessing and when oauth2 clients.    If its an identity login then we log it as the user.

or am I missing something here

The values we're discussing here are client, not user related.

@brockallen Sorry we apart to have side tracked your thread.
I would be interested to hear how you plan on detecting last access?  Are we talking last valid use of it or last attempted use of it?
Also probably another issue but a method for resetting secret would be really nice.

I would be interested to hear how you plan on detecting last access? Are we talking last valid use of it or last attempted use of it?

Yea, we'd have to find out in the authN code which one is matched and then somehow trigger an update to the DB for it.

Going to have to do some kind of load testing you dont want two updates running at the same time crashing into eachother.

wouldn't the easiest solution be to update the field on successful login (to the OP, not the client)?
That's all I had planned to do.
Peace ..tom

From: Linda Lawton<EMAIL_ADDRESS>Sent: Tuesday, June 5, 2018 5:32 AM
To: IdentityServer/IdentityServer4
Cc: tom jones; Comment
Subject: Re: [IdentityServer/IdentityServer4] Consider create datetime on ClientSecret (#2055)
Going to have to do some kind of load testing you dont want two updates running at the same time crashing into eachother.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/IdentityServer/IdentityServer4/issues/2055#issuecomment-394691737, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AKxq1k_za5Y8OWu3lrlHuLkyBx5sd89Oks5t5nprgaJpZM4R8Ukf.

Ok I am going to play devils advocate here and ask will updating the database on all successful logins cause any load issues?   deadlocks can't happen on update iir but what happens if the row no longer exists for some reason or you can't access the database.    there will need to be some readable error handling with this.

This thread does seem to be wandering, but you should consider the purpose of the field. If the record doesn't exist there is no purpose served in updating it.

This thread does seem to be wandering, but you should consider the purpose of the field. If the record doesn't exist there is no purpose served in updating it.

I don't see this for 2.3 - will be considered at some later point.

I misspoke ;)

Created date time added to the secret EF class.


test exporting literal types

This code compiles with a couple thousand of warnings like this:
lib/generated/x-ray.ts:467:1 - message JSII9998: Unsupported TypeAliasDeclaration node. This declaration will not be accessible from other languages.

467 export type XrayActions = XrayActionsList | XrayActionsWrite | XrayActionsPermissionsManagement | XrayActionsRead | XrayActionsTagging;
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

But the package builds and can be imported, tested with Python. Of course, this won't work in any other language than TypeScript.
The types are not implemented in any method. But could be used like this:
function t(action: statement.IamActions): string {
  return action
}

new statement.Iam() //
      .allow()
      .to(t('DeletePolicy'));

What I meant was more along the lines of this:
type Actions =
  | 'CreateTable'
  | 'CreateIndex'
  | 'CreateBucket'

type MatchIamAction<T extends string> =
  string extends T
  ? Record<string, string>
  : T extends `${infer Start},${infer Rest}`
  ? {[k in Start | keyof MatchIamAction<Rest>]: string}
  : T extends `${infer Start}`
  ? {[k in Start]: string}
  : {};

type P = MatchIamAction<'CreateTable'>;

type C = MatchIamAction<'Create*,ListTable'>;

However - after some googling I don't think that pattern matching is working the way. I was hoping for. I wasn't able to expand Create* to the full action in the types.


fix: bump sc4s/splunk versions

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


RLE construction speed

Primarily changes the underlying data structure of the RLE B+ tree structure to be more efficient in practice
Created a RLEBPlusNode struct to better encapsulate data; this will also allow us to experiment with other node types in the future provided it implements the correct functionality
Changes the RLEBlock data encoding two a u16 method with fixed run lengths and also to a much larger block (254 instead of 63); this trade-off in compression tends to be faster in practice
Replaces Vec with ArrayVec when the lengths are fixed below some threshold
Added mimalloc as the allocator; there is a relatively small but consistent improvement in performance

All file checks look good, waiting on CI and final large verification runs locally now

Local changes are identical to ropebwt2 commands still, this looks good to go


The Phi definition of GELU is incorrect

URL(s) with the issue:
https://www.tensorflow.org/addons/api_docs/python/tfa/activations/gelu?hl=en
Description of issue (what needs changing):
Clear description
Currently, the definition of \Phi(x) in the GELU document is as the follow:
    \Phi(x) = \frac{x}{2} \left[ 1 + \tanh(\sqrt{\frac{2}{\pi}} \cdot (x + 0.044715 \cdot x^3)) \right]

But it seems that this is the definition of gelu(x), is not it of \Phi(x) in the original paper.
I expect that a definition of \Phi(x) was as the follow:
    \Phi(x) = \frac{1}{2} \left[ 1 + \tanh(\sqrt{\frac{2}{\pi}} \cdot (x + 0.044715 \cdot x^3)) \right]

Or, the document defined gelu(x) directly when approximate is True like the follow:
    gelu(x) = \frac{x}{2} \left[ 1 + \tanh(\sqrt{\frac{2}{\pi}} \cdot (x + 0.044715 \cdot x^3)) \right]

@RATATATO
Can you please share the original paper as proof of the doc change requested.

The original paper is here:

Gaussian Error Linear Units (GELUs)

This paper is also linked in the GELU page.
In the section 2 of the paper, an approximation of gelu(x) is shown as the follow:
We can approximate the GELU with
   0.5x(1 + tanh( ...    (Same definition of \Phi(x) on the Tensorflow page currently)

So from the paper, I expect that an approximation of gelu(x) and \Phi(x) is as the follow:
gelu(x) = x * \Phi(x) = 0.5x(1 + tanh( ...
\Phi(x) = 0.5(1 + tanh( ...

See also
Also on other sites, the current definition of \Phi(x) is used as an approximation of gelu(x), not as it of \Phi(x)

https://datascience.stackexchange.com/questions/49522/what-is-gelu-activation
etc

@RATATATO  Perhaps you can raise PR to fix this issue
The docs are generated from https://github.com/tensorflow/addons/blob/master/tensorflow_addons/activations/gelu.py


Support publishing and fetching folder artifacts

Currently only files are supported. The tool should support publishing folder artifacts (and fetching them).

Close this was it was fixed by PR #11


Influxdb allows you to write keys that start with a number but wont use the tag

Bug report
System info:  v1.3.5
Steps to reproduce:
> insert m,0numberkey=anything value=0.67
> select * from m
name: m
time                0numberkey value
----                ---------- -----
1507595526079856791 anything   0.67
> select * from m where 0numberkey = 'anything'
ERR: error parsing query: invalid duration
> drop series from m where 0numberkey = 'anything'
ERR: error parsing query: invalid duration

Expected behavior: I expected to see the result by using the key
Actual behavior: I get an ugly error about parsing some duration

You have to quote it.
http://docs.influxdata.com/influxdb/v1.3/query_language/data_exploration/#quoting

Identifiers must be double quoted ... if they begin with a digit

> select * from m where "0numberkey" = 'anything'
name: m
time                0numberkey value
----                ---------- -----
1507603188750653149 anything   0.67

> drop series from m where "0numberkey" = 'anything'
>

@phemmer thanks. I tried single quotes. Thanks


Implement zip and unzip commands

This PR implements zip/unzip commands as per #223. The only exception is that the maps (--path-map) for zip are not implemented (yet).

wow, thanks a lot. i wanted this one for a long time but was too lazy to implement :)
I'll review it and provide you feedback

wow, thanks a lot. i wanted this one for a long time but was too lazy to implement :)
I'll review it and provide you feedback

Yeah, sorry for such a huge delay

@Red-Teapot loos great. thanks a lot. merging


feat(sms): add example-generated task/servertemplate

Description of your changes

I have:
add example generated
waiting for the fix of the creation of an AK/SK pair issue to do an example

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Please regenerate list-tested.md


Implement a BigQuery runner for the query library

With the new approach to our query library API, the underlying runner for distributed data processing is completely separated from how the end user of the library, uses the generated Pandas DataFrames. Our current focus is the Spark runner but we will need a BigQuery based implementation too, i.e., implementing this class.
The new query API is a work in progress and we should focus on BigQuery runner only after we are fairly confident the query API is good enough for the immediate use-cases we have.

This is implemented in PR #269.


Update Helidon MP support in OpenAPITools/openapi-generator from 1.x to 2.x

Environment Details

Helidon Version: 2.4.1
Helidon SE or Helidon MP
JDK version:
OS:
Docker version (if applicable):

Problem Description
The OpenAPITools/openapi-generator project already has support for Helidon MP 1.x. This issue tracks my work to update it to 2.x
I have changes ready for a PR once we release 2.4.1 so the updated generator will work with our very latest release.
See OpenAPITools/openapi-generator#11043

The PR in OpenAPITools has been approved and merged. Closing this tracking issue.


added a method to install the framework using Carthage to README.MD

Hi @arietis
Thanks for your contribution, please note that this is our old iOS SDK that is to be fully replaced by https://github.com/checkout/frames-ios/
Any reason why you're looking at it instead?

Hello @nicolas-maalouf-cko
There is no specific reason. I have just recently discovered there is a new version of the SDK. :) Thanks!


Not respecting index related options when installing setup_requires items.

When utilizing an internal PyPI server along with the --index option, the sub-process responsible for installing the setup_requires items fails to include the corresponding pip --index option.
For instance, while running the following command:
pex "chromedriver-py-auto==0.2.4" --index=http://company_domain/artifactory/api/pypi/all-pypi/simple --no-pypi --resolver-version pip-2020-resolver --python python3.7 -vvvvvvvvv -o out.pex
I encountered the following error:
subprocess.CalledProcessError: Command '['/home/roshanzamir/.pex/venvs/5229c2e3204232c184c11b4e410064589c3175bd/8526d9ba87349150aa1391090e89d679ed25a846/bin/python', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/home/roshanzamir/.pex/pip_cache/.tmp/tmpo8x81jjl', '--quiet', 'chromedriver-py==104.0.5112.79']' returned non-zero exit status 2.
The chromedriver-py==104.0.5112.79 item is part of the setup_requires field in the chromedriver-py-auto==0.2.4 library. Since our internal network machines do not have internet access, it should be fetched from our company's internal PyPI server. However, when using pex, it attempts to retrieve it from the original PyPI server, resulting in a timeout issue.

What version of Pex is this?

This was nominally fixed in https://github.com/pantsbuild/pex/releases/tag/v2.1.1 over three years ago by https://github.com/pantsbuild/pex/pull/865 but your output shows Pex running Pip in a venv which is newer than that.

Actually @AlirezaRoshanzamir, what you're trying to do is not even supported by Pip IIUC: https://github.com/pypa/pip/issues/2910
The issue is setup_requires uses the ancient easy_install to fetch requirements and that has its own index configuration system separate from Pip. As the issue I linked alludes, you should be using PEP-518 / PEP-517 here with an in-tree build backend.

@AlirezaRoshanzamir I'm going to close this as answered. Namely the issue here is Pip does not pass along --index configuration to easy_install for setup_requires resolution (The fact the command you snip is happening with -w /home/roshanzamir/.pex/pip_cache/.tmp/tmpo8x81jjl and that Pex has no code that calls -m pip is further proof). You should be migrating your setup.py to use PEP-517.

Thank you, @jsirois, for your prompt response. I sincerely appreciate it.
You're absolutely right. I had previously encountered that issue, and initially, I attempted it with pip, which seemed to work. However, after clearing the caches, I discovered that you were correct all along.
The underlying problem I'm facing is the need to locate the appropriate chromedriver-py dependency based on the specific version of the client's Chrome browser. This extraction process occurs dynamically during the setup phase. Unfortunately, utilizing the install_requires approach is not viable since it would result in lockfiles containing the precise driver version, which is not suitable for every client. Therefore, I must explore alternative methods to address this challenge.
Once again, I sincerely appreciate your valuable time and assistance.

You're welcome. You definitely can address your use case by implementing a PEP-517 in tree build backend that implements https://peps.python.org/pep-0517/#get-requires-for-build-wheel and forwards the rest of the required API functions to setuptools.build_meta.


chore: release  parent 0.2.0

:package: Staging a new release
0.2.0 (2024-10-09)
Features

amphora-parent: upgrade internal dependencies (#66) (fac4666)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/carbynestack/amphora/releases/tag/parent-v0.2.0 :sunflower:


GPT with specific knowledge of particular repository , can I do it ?

Did you try this out at all?
https://github.com/jerryjliu/llama_index/blob/main/gpt_index/readers/github_readers/github_repository_reader.py


Incorporate HS3 fields

Compact high-level view to the format

Might be completed already

Just notices the metadata field here. That is what we are going to use, then!

Nice!
Yeah I was wondering about some versioning for the schema as well. Makes sense to put that in metadata as well then. And indeed to make it a required field

seems resolved


Update Install-Modules.ps1

The following commands are already available on this system:'Test-AccessToken'. This module 'MSGraphRequest' may override the  existing commands. If you still want to install this module 'MSGraphRequest', use -AllowClobber parameter.
Extract from https://learn.microsoft.com/en-us/powershell/module/powershellget/install-module?view=powershellget-3.x#-allowclobber
-AllowClobber
Overrides warning messages about installation conflicts about existing commands on a computer. Overwrites existing commands that have the same name as commands being installed by a module. AllowClobber and Force can be used together in an Install-Module command.
The proxy cmdlet transform the value of this parameter to the NoClobber parameter of the Install-PSResource cmdlet.

This is addressed with the upcoming release.


What about goose-starter-kit

A project with configured build for browser env and working basic usage example. Users will be able to clone this repo and start hacking!

Great suggestion!

But is that the same as done in the tests for BrowserEnvironment?

If we have starter-kit, everything will be clear and useful. Trust me :boar:

example https://github.com/kriasoft/react-starter-kit

repo https://github.com/redco/goose-starter-kit


Command to Remove Named Block from XML file.

Add to full module for content.phtml when we're done.

Command added, and added call to full_module command to remove default content.phtml block.


Undefined

I just get an "Undefined 🤷♀" in the corner

same for me

@TamtamHero

i also have this error.

I don't add much value, but I do too.

These bits of information would be very helpful:
Description
Screenshots
Steps To Reproduce
System Details (OS, browser, wallet?, etc)
Hope that helps a little :)

I have the same issue. Using Chrome's developer tools I see that the HTTP request to the URL starting https://backend.matic.supply:3000/rpc-mainnet/matic/ is failing with a 500 error. The HTTP response content is just:
{"err":{}}
I made a failing request at the following timestamp, in case that helps you locate logs on the backend: Mon, 01 Nov 2021 02:06:06 GMT

I am seeing this issue as well, the request that my browser sends is:
GET /rpc-mainnet/matic/{LOTS OF ENCODED TEXT} HTTP/1.1
Host: backend.matic.supply:3000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:93.0) Gecko/20100101 Firefox/93.0
Accept: application/json, text/plain, /
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Origin: https://matic.supply
DNT: 1
Connection: keep-alive
Referer: https://matic.supply/
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: same-site
Sec-GPC: 1
Response is:
HTTP/1.1 500 Internal Server Error
X-Powered-By: Express
Access-Control-Allow-Origin: https://matic.supply
Access-Control-Allow-Methods: GET, POST, OPTIONS, PUT, PATCH, DELETE
Access-Control-Allow-Headers: X-Requested-With,content-type
Access-Control-Allow-Credentials: true
Content-Type: application/json; charset=utf-8
Content-Length: 10
ETag: W/"a-dZO1N3n8cxTQPS5V0xaSF3O8/ws"
Date: Wed, 03 Nov 2021 17:54:00 GMT
Connection: keep-alive

@TamtamHero any news on this?

Having the name issue here. Any news on this subject @TamtamHero ?

it is best to say, that this faucet is abandoned and broken. if you are looking for a faucet, mac&cheese run one at https://macncheese.finance/matic-polygon-mainnet-faucet.php

That one is temporarily offline too. Seems like getting free tidbits isn't so easy...


Add Hall Of Plasma by phil_thyrichmusic

Song Name
Hall Of Plasma
Artist Name
phil_thyrichmusic
Source
Youtube
Youtube Link
4daRnGtcfIAIkEZn
Direct File Link
No response
Song ID
7
Extra
Created from Auto Nong.
Created for level: 104518190

accept


added code for middle element in linked list

Fixes #38

LGTM

Add Complexities as well

I have made the changes.


Pneumatic cannons

About the PR
Pneumatic cannons; attach a gas tank to em, put some items in, and shoot them at people
Features:

Changeable mode (single fire/fire all items)
Queues up sounds/firing so that it looks cooler
Funny sound

Todo

[ ] Gas tank actually does somethin
[ ] Construction
[ ] Inhands
[ ] Forcefeed https://www.youtube.com/watch?v=URJ_qSXruW0&t=938s

Screenshots
https://user-images.githubusercontent.com/19853115/132061156-efeb8c80-ce2f-4b16-a76d-3483e46d8038.mp4
Changelog

:cl:

add: Improvised pneumatic cannons! You can mess around with them with a screwdriver and wrench, and shoot items from them as long as they have a gas tank. They're in the crafting menu.

ill make it launch backwards on medium/high, we do have the technology with box2d

Needs to be updated to replace ComponentManager by EntityManager

Needs to be updated for ECS verbs (I'm so sorry)


Cannot add attachments to armor

Describe the bug
I cannot add armor attachments or mods to armor that has been put onto a character sheet from the compendium.
To Reproduce
Steps to reproduce the behavior:

Go to 'Compendium > Armor'
Drag a piece of armor that has hardpoints > 0 onto a character sheet.  For this example let's use 'Armored Robes'
Click on the edit button for Armored Robes on the character sheet - this will open a window for the 'Armored Robes'
Open 'Compendium > Armor Attachments'
Select an attachment - let's use 'Boot Blade'
Drag the 'Boot Blade' onto the open Armor sheet.
The 'Boot Blade' is not added to the armor

Expected behavior
The 'Boot Blade' should have been added to the 'Armored Robes' page that is opened.
Screenshots

Desktop (please complete the following information):

Foundry Version: v12.331
System Version: 1.903
Hosted on Forge: Yes (but confirmed same issue on local instance)

Additional context
Appears to be an issue with the attachment/mod type.

@phookz As a temporary fix, if you open and close the attachment once before drag and dropping it, it is attached.

I think the "type" you're talking about only restricts the kind of modifiers ou can add to the attachment, and changing it won't solve the issue. I'll try that later. Changing it seems like a good idea, I'll create an issue later too.
What I think is happening is this:

Compendium content is only indexed, not loaded, when Foundry is started.
Something is interfering with the loading when drag-and-dropping an armor attachment, so nothing seems to happen
Individual items of a Compendium are loaded when opened, which is why drag and dropping works afterwards.

@phookz So in the end it was because of an incorrect modifiers type, it was set as "armor" instead of "armour" (the internal value, display value is indeed "Armor"), and that messed with the drag-and-drop somehow !
Opening it switched it to the default value "all".


Add initial u8darts recipe

This would add a conda package called 'u8darts', linked to the PyPI 'u8darts' package. This means only the core requirements will be installed. I think this is the best way to avoid confusion because of differences between conda and PyPI packages.
It would be possible to create variants such as 'u8darts-all' and 'u8darts-torch', see the pytorch feedstock for an example.

Also let me know if you want to be added or removed from the recipe-maintainers section. I think it should work with just 'unit8co', but best to have a backup in case that wouldn't.


iqueue: init at 0.1.0

Motivation for this change
Add a new package I use.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 139064 at 68300938 run on aarch64-linux 1

1 package failed to build:

iqueue

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


Unused component AdminRouter in react-admin

I don't see this component being used:
https://github.com/marmelab/admin-on-rest/blob/f3eb6e0eae5b6407a7d8e4817ebbd6db217509ea/packages/react-admin/src/AdminRouter.js#L1-L10
Is this an oversight and should it be passed to Admin or should it be removed?

It's not used by us but may be used by people making a custom app

But shouldn't it be used by you, because the default implementation uses ra-ui-materialui?

We just define the loading default prop here for those who want to use AdminRouter but not Admin which also define this default. That's why we don't use it directly

Ah, an oversight on my side, didn't notice the loading on Admin. 👍


Creating the Github Repository for the R Dashboard

Create a new github.com repo and Name it the same as your Python dashboard repo plus a -R suffix.
Copy over your contributing guidelines, the code of conduct, license, the README file, and the necessary data files.

How about we change the name of this repo to netflix_dashboard-R and name our Python repo netflix_dashboard-py?

I'm a little worried that a lot of the links would have to be changed now. So, we will leave it as it is for now.


[5.1][Foundation] Modernize hashing in Foundation's Swift-only types

This is cherry picked from #23832; see discussion there.
rdar://problem/43394032

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 8cd901f1409070c9234a6d6cfc7c150820544250

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 8cd901f1409070c9234a6d6cfc7c150820544250

Build failed
Swift Test Linux Platform
Git Sha - 8cd901f1409070c9234a6d6cfc7c150820544250

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - c894cbb0b09ed566cae6f79517d183e0e48e13bd


Uncaught ReferenceError: require is not defined

Describe the Bug

At present, when you clone the react-flow repository and follow the same instructions to run the app on localhost, your local browser console shows an error -  Uncaught ReferenceError: require is not defined.

Also, the react-flow app works fine without errors in my Mac operating system but in windows it is throwing the above stated error.

Your Example Website or App
https://github.com/wbkd/react-flow
Steps to Reproduce the Bug or Issue

Cloned repo locally (https://github.com/wbkd/react-flow ) to C:\usr\react-flow
Inside react-flow run the following commands:
cd example && npm install
Then with windows cmd in C:\development\react-flow:
npm start
Then with separate windows cmd in C:\development\theraflow-designer\react-flow:
cd example && npm start

When accessing with any browser localhost:3000 generates only empty page with following errors in console:
Expected behavior
As a user I expected the app to run smoothly on Windows operating system like this:

But seeing the following error in console:
extends.js:17 Uncaught ReferenceError: require is not defined
at Module.../dist/esm/index-5236d2af.js (extends.js:17:1)
at Module.options.factory (react refresh:6:1)
at webpack_require (bootstrap:24:1)
at fn (hot module replacement:61:1)
at Module.../dist/esm/index.js (slicedToArray.js:7:1)
at Module.options.factory (react refresh:6:1)
at webpack_require (bootstrap:24:1)
at fn (hot module replacement:61:1)
at Module../src/Basic/index.tsx (bundle.js:15:77)
at Module.options.factory (react refresh:6:1)
Screenshots or Videos

Platform

OS: [Windows 10]
Browser: [Chrome]
Node version: v17.8.0
Npm version: v8.1.2

Additional context
The app runs fine with Mac but having issues running with Windows.

I am having a similar issue but not using React Flow. Some of my possibly relevant dependencies:
"react": "^18.2.0",
"styled-components": "^5.3.6",
"webpack": "^5.74.0"
the error i'm getting (quite similar):
Uncaught ReferenceError: require is not defined
at Object.events (external node-commonjs "events":1:1)
at webpack_require (bootstrap:24:1)
at fn (hot module replacement:62:1)
at ./node_modules/webpack/hot/emitter.js (emitter.js:1:20)
at webpack_require (bootstrap:24:1)
at fn (hot module replacement:62:1)
at ./node_modules/webpack/hot/dev-server.js (dev-server.js:63:19)
at webpack_require (bootstrap:24:1)
at startup:4:1
at startup:5:1

MacOS
Chrome
Node -v: 15.7.0
Npm -v: 7.6.1

please re-open if the issue persists. It should be fixed by now.


Add pre-commit-hooks for linting

This PR adds pre-commit hooks for linting the code.

@John-Ragland @FelixSchwock This adds additional checks beyond flake8, including: code formatting, docs rst checks, and module import sorting.


new fades cancel old ones

I wanted to be able to smoothly fade sounds up and down without worrying about interference or unwanted callbacks.  Maybe this is different from the intended functioning, but for me it's exactly what I need :)

Thanks a lot and sorry for the delay.
Better late than never :)


bug: Module not found: Can't resolve '@acme/db/client;

Provide environment information
System:
OS: macOS 14.0
CPU: (10) arm64 Apple M1 Pro
Memory: 679.89 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.15.0 - ~/.nvm/versions/node/v20.15.0/bin/node
Yarn: 1.22.17 - ~/.yarn/bin/yarn
npm: 10.7.0 - ~/.nvm/versions/node/v20.15.0/bin/npm
pnpm: 9.6.0 - ~/.nvm/versions/node/v20.15.0/bin/pnpm
bun: 1.0.0 - ~/.bun/bin/bun
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Describe the bug
I think you might wanna resolve this issue, did nothing, cloned the repo and installed everything using pnpm i and after running the nextjs app, found this out, most probably due to incorrect exports in db package?
"exports": {
".": {
"types": "./dist/index.d.ts",
"default": "./dist/index.js"
},
"./client": {
"types": "./dist/client.d.ts",
"default": "./dist/client.js"
},
"./schema": {
"types": "./dist/schema.d.ts",
"default": "./dist/schema.js"
}
},

Link to reproduction
pnpm i && cd apps/nextjs && pnpm run dev
To reproduce
pnpm i && cd apps/nextjs && pnpm run dev
Additional information
No response

May I see the files inside your packages/db/dist?

Yeah i figured it out, i need to build everytime i change my db schema, in the previous version of t3 turbo, i didn't have to do this

turbo run dev runs watchers that emits declaration files whenever packages changes
Live types are not very performant as the repo grows which is why we have opted for emitting declaration files instead. If you have a small repo with a small drizzle schema, a small trpc router without a lot of zod schemas, you may get away with live types and rely on typescript inference but ymmv

Thanks Julius! Appreciate your efforts.
On Mon, 12 Aug 2024 at 12:19 AM, Julius Marminge @.***>
wrote:

Closed #1145 https://github.com/t3-oss/create-t3-turbo/issues/1145 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/t3-oss/create-t3-turbo/issues/1145#event-13836976479,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKO4HBYEENMRTN4MZA25MN3ZQ6W5BAVCNFSM6AAAAABMKUZDZCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTHAZTMOJXGY2DOOI
.
You are receiving this because you authored the thread.Message ID:
@.***>

This happens on build time now

turbo run dev runs watchers that emits declaration files whenever packages changes
Live types are not very performant as the repo grows which is why we have opted for emitting declaration files instead. If you have a small repo with a small drizzle schema, a small trpc router without a lot of zod schemas, you may get away with live types and rely on typescript inference but ymmv

Be that as it may, I don't understand the decision to do this. It essentially breaks a lot of the hot reloading to the point where it becomes a massive pain to use. I had to change turbo dev script persistent to true and run tsc --watch on my package dev scripts otherwise I would make changes in the api and nothing would actually happen until i rebuilt which is so annoying to do on every little change especially when debugging. What's the point of transpiling the packages in next.config when they wont update a lot of the time anyway.

What's the point of transpiling the packages in next.config when they wont update a lot of the time anyway.

If you depend a lot on small packages rather than writing most of your components in the apps themselves, they will update a lot. It depends on your specific project/monorepo structure. If you have a large codebase with lots of shared code (packages) then you will be updating the packages often. If that's not the case then you probably don't need a monorepo in the first place.
I agree that the breaking of tRPC go to definition is really annoying. I've already opened an issue but I don't expect much. There is probably no fix. And yes you could argue that emitting declaration files as a default maybe too much. The problem is that Zod is just too slow and I'm pretty sure the reason this decision was made was due to some low performace reports.


eficheck doesn't work on T2 equipped Macs

Problem
The eficheckutility does not work on Macs equipped with the T2 chip. Currently:

2018 MacBook Pros
iMac Pro

The following descibes testing on a 2018 MacBook Pro.
The kext responsible for eficheck, com.apple .driver.eficheck, is not loaded however is present at /System/Library/Extensions/eficheck.kext.
Attempting to run eficheck produces the following output:
$ /usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check
ReadBinaryFromKernel: No matching services found. Either this system is not supported by eficheck, or you need to re-load the kext
IntegrityCheck: couldn't get EFI contents from kext

Loading eficheck.kext and rerunning eficheck doesn't work and produces the same output as above.
Fix
Need to be able to identify, from bash, Macs which have a T2 chip and skip the check_EFI_integrity function.

Fix
Using the system_profiler utility we can view details of the T2 aka iBridge.
$ system_profiler SPiBridgeDataType
Controller:

    Controller Information:

      Model Name: Apple T2 chip
      Firmware Version: 15P6703
      Boot UUID: ***REDACTED***

Unfortunately running system_profiler SPiBridgeDataType on a system that does not have a T2 chip still returns true.
We can use grep to check for the T2:
if system_profiler SPiBridgeDataType | grep 'T2'; then
  echo "T2 Present"
else
  echo "No T2 Present"
  check_EFI_integrity
fi

Need to test if eficheck works on the 2016 and 2017 MacBook Pro with Touchbar models and what system_profiler SPiBridgeDataType returns.

From a 2016 TouchBar MBP (MacBookPro13,3):
$ system_profiler SPiBridgeDataType
Controller:

    Controller Information:

      Model Name: Apple T1 chip
      Firmware Version: 14Y664

$ /usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check
EFI Version: MBP133.88Z.0247.B00.1806261159
Primary allowlist version match found. No changes detected in primary hashes.
``

490494c4c36d45fb68552177d2c381d4ab8461fb addresses this by checking if the Mac has a T2 chip via system_profiler SPiBridgeDataType and exiting check_efi_integrity if it does.
Keeping this open to add more information.

@mikeorama thank you!

From a 2017 TouchBar MBP (MacBookPro14,3):
Language: French
$ system_profiler SPiBridgeDataType
Controller:

    Informations sur le contrôleur:

      Model Name: Apple T1 puce
      Firmware Version: 14Y664

$ /usr/libexec/firmwarecheckers/eficheck/eficheck --integrity-check
EFI Version: MBP143.88Z.0178.B00.1806261159
Primary allowlist version match found. No changes detected in primary hashes.

Source

Filed a Radar.
Here's the Open Radar entry: https://openradar.appspot.com/radar?id=5020911870672896

Apple closed my Radar with the comment:
Regarding this: said “My request is that there should be some way to verify the integrity
of EFI from userland on Macs with T2 chips.”

The architecture for T2 systems is such that there is much less value in attempting to
make eficheck work with it, and thus enhancements are not currently on our plans.

mOSL will skip check_efi_integrity when running on a Mac with a T2 chip, this was added by 490494c4c36d45fb68552177d2c381d4ab8461fb.
Given Apples response I don't think there's anything else that can be done. If this changes I'll reopen this issue.


Email magic link connection can be added as the first step, but QSG says to add with identifier first as the first step

Describe the Issue:
When added by the template

What is shown in the QSG

How To Reproduce:
Expected behavior:
Update the QSG accordingly
Device Information:

Device (e.g. PC, iPhone6):
OS (OSX, Android, iOS):
Browser + Version:

Optional Fields
Related Issues:
Suggested Labels (for non-committers):
Suggested Assignees (for non-committers):

Testing Related Fields
Local e2e Tests Status (Please attach the screenshots of the result):
Manual Test Plan (Please attach the document link):
Manual Test Plan Reviewed by:

Fixed in the latest identity-server


[vm] Consider creating a specialized allocator for List.filled

We can implement List.filled (_List.filled, _GrowableList.filled) more efficiently, without a loop which initializes array elements after creating a list - it can reuse initialization performed during array object allocation. For this purpose, we need the following:

Implement specialized array allocator stub which would take fill argument and use it to initialize array elements instead of null.
Add CreateFilledArray IL instruction (or modify CreateArray instruction to optionally take extra argument), and generate it using the stub. We might also need to generate inline allocation code to be on par with CreateArray.
Implement List.filled (and probably _List.filled, _GrowableList.filled) as recognized function in the VM and generate flow graph using the new instruction.

You could delete the old instruction afterward.  Legacy mode List(n) would then be lowered to _List.filled with an explicit null. Then you should have approximately the same amount of code to maintain.


maintainers: prefix number with underscore

This is the same pattern that is already used for packages, I think it makes sense to reuse it here.
https://github.com/NixOS/nixpkgs/blob/4789d6feafd9ba0613b9f1fd4dcd6b1ed0572f4b/pkgs/top-level/all-packages.nix#L531-L545
GitHub doesn't allow usernames with underscores so these won't collide with another user.

Sorry, now I see why this is relevant. And this is using an existing precedent.

cc @0x4A6F @1000101

Oh, not this again, I feel like I spend hours on discussing this trivial case. I don't think
this is a solution, unless it is agreed as a standard (which is in packages names, because there is a real
technical reason for this, not that someone is not paying and testing their changes introducing introduces a bug).
But if feel like this is a trip wire, let's create a meta data check in ofborg, that will be beneficial in the future as well.

let's create a meta data check in ofborg

Not exactly easy to actually get it done and we might end up moving some checks away from ofborg anyway.

cc @0x4A6F @1000101

I suggest also mapping over the keys and asserting none start with a number.

I suggest also mapping over the keys and asserting none start with a number.

Can you elaborate please?

I'm assuming having CI do something to the effect of:
  lib.mapAttrs (name: assert (builtins.match "^([0-9]).*" == null)) lib.maintainers

where there's a check that a new maintainer doesn't start with a number.

I don't think adding it to ofborg is a productive use of time as there has been some discussions about moving things away from ofborg. Bus factor is also an issue so I don't want to add more things there anyway.
I don't want to add it as a check that runs on hydra as that depends on someone noticing and caring about it enough to unbreak it, I think we have enough things already that we don't know are broken until after a PR is merged (e.g. the manuals).
I'm happy to implement this and other maintainer checks (e.g. check github has a matching githubId) via an action that actually catches the errors before merge, when we can actually use actions.

I'm happy to implement this and other maintainer checks (e.g. check github has a matching githubId) via an action that actually catches the errors before merge, when we can actually use actions.

I think this would be easy enough to implement as a github action.

Just to be clear about the current status of actions: we can't use them at the moment.
We were using two actions but they were removed because they caused too much disruption. We're now waiting for a couple of things to be resolved before we try them again, I don't really have a timeframe for when that will happen.
I'd want to have those actions running for a couple of weeks without causing any problems before we start adding more.
I see this PR as a slight improvement over the status quo even without a way of enforcing it, I don't think having a check should be a blocker.

I am not suggesting an explicit test, but having the map @jonringer wrote directly in the maintainers file. Eval errors are noticed.

how did you want to expose this? doing the evaluation on just lib.maintainers would mean evaluating all 1000+ entries any time you want to access a given maintainer. Something like lib.maintainers._verifyNames? Couldn't think of any good names

Actually, lib/tests/release.nix is already executed by ofborg and that includes lib/tests/maintainers.nix. That will be cheaper than directly in maintainer-list.nix.

Sorry but I'm not going to implement what has been requested.
Should I close this PR?

I think the PR is fine as is.
The check can happen in a different PR

Sorry but I'm not going to implement what has been requested.
Should I close this PR?

Don't you dare! :smile:


adding an index to the IamDataFrame, allow using it as arg in metadata()

This PR adds an index to IamDataFrame, pointing to the index (['model', 'scenario']) of the meta dataframe. This is a quicker way to look at all models and scenarios in an IamDataFrame than df.filter[['model', 'scenario']].drop_duplicates() and brings us closer to the pd.DataFrame.
Also, an index can now be passed as an argument to the metadata() function, to assign a value in a meta column to all scenarios satisfying some filters. Previously, I would do the filter, use the index of the meta DataFrame to generate a pd.Series with the value, and pass that to metadata(). This is now internalised in the function.
So the new use case would be df.metadata('some_category_name', 'some_column', df.filter('{some filters}').
Last, setting column values in meta to uncategorised (from the pre-refactoring days, currently not operational as far as I can tell) is fixed - if a new column is added to meta and the data type of the value is a string, the default of that column is set to uncategorized, and to np.NaN otherwise.

solves #40

Thanks @gidden for the comments!
Resetting the index of either the data or meta frames does not make sense in our framework (because some functions require the index of meta to be ['model', 'scenario'] and data needs to have a given set of columns).
Your proposed alternative meta_index() could just as easily be achieved using meta.index directly. I guess it's easiest to just remove the index property and merge the other features of this PR, and then do the more thorough review of nice-to-have pandas features later.

As discussed previously, I removed the IamDataFrame.index - for now, let's continue to use IamDataFrame.meta.index directly.
Also, I refactored the function metadata() to set_meta(), closes #59

rebased and implemented most suggestions
should be good to be re-reviewed, @gidden

Just a typo, then good to go!

thanks @gidden for catching the typo!
re the is scalar() function, note that the use case here is different than is scalar() - pd.Series (and maybe other array types) need to be cast to lists for the later workflow, while strings and scalars can be appended as is. Anyway, I added both your isscalar() function (because we'll probably need it at some point anyway) and a new islistable() function.

thanks @danielhuppmann!


CCS811 on NodeMCU v3

I'm using NodeMCU v3 and CCS811's chinese copy (CJMCU).
I'm trying to run the basic program, to check if the sensor reads some data.
At first I was receiving messages like this:

Starting CCS811 basic demo
init: hardware version: 12
init: bootloader version: 1000
init: application version: 1100
errstat=10=--vhxmrwf--Ad-ie
errstat=10=--vhxmrwf--Ad-ie
errstat=10=--vhxmrwf--Ad-ie

and it kept going like this indefinitely.
After I did a hard reset using the RST pin, I started receiving these messages:

and, again, it waits indefinitely and reads no data.
I've tried using Adafruit's library here, these were the results:

If it had failed to start, I would've been prompted with another message. Instead, it starts, but it fails to read data.
Also, I've checked everything with an i2c scanner and the sensor is recognized with its correct address. I've also used your library to check the i2c bus and everything works normally.
Do you have any suggestions? What does errstat= 10 mean? (I couldn't find anything on the web).

Hi, the fact that you get the three lines with the versions means that the nodemcu could communicate with the CCS811. So, the nodemcu is working, the i2c wiring is ok, and the CCS811 controller is working. Good news.
For error handling, the CCS811 has two 8-bit registers: ERROR_ID and STATUS. My library glues them together into a 16-bit variable errstat. So a value of hex 10 (the leading 0s are not printed) means hex 0010 or binary 0000 0000 0001 0000.
The binary representation is important because the single bits correspond to error flags (see datasheet). The library helps but using a letter for each flag, lower case meaning 0 and upper case meaning 1. A dash means the bit is unused.
That is the funny string behind 10=
--vhxmrwf--Ad-ie
One flag is up (one bit is 1) namely bit 4 (start counting from 0 from the right). This is the capital A. It means valid application firmware loaded. If I'm not mistaken, the f flag should also be high for Firmware is in application mode.
So that transition is missed.  Line 169 in the cpp file checks that the F flag is set. I'm a bit puzzled.
In the second run, another flag is missing: data ready (the small d should be D).
Hmmm

Thank you for your response! Now I understand better what is happening with these errors.
I'm thinking about using your flash example to update its firmware. Do you think it's a chance that will solve the problem?

To be honest, I have no hypothesis of what could be broken here. Easy problems like bad I2C communication, or broken heater, do not seem the case here. It does look a bit like the controller in the CCS811 is acting funny, and that could be a problem with the firmware. On the other hand, how could the firmware be half broken...?
On the other hand, your CCS811 board is not working right now, so maybe give firmware update a try.

Hello!
So I've flashed the little guy and the update went without errors.
Now I'm getting this I2C error, even though I haven't changed the connections since last time.

As you can see, I've also added a check with your I2C library and the errstat output.
I've also checked the bus with an I2C scanner and the sensor is still available at the same correct address.
I'm so puzzled right now.

The value of errstat is not reliable now. As you can see, all bits as read by the CPU are high. This is not because they are high, this is because the CCS811 is not sending the real values; the SDA line just stays high (due to the -internal- pull up resistor) and this is interpreted as 1s.
But it is the same funny thing as before: at first the ccs811 is talking to the cpu. The proof is in the first 5 lines with all the version info; that is send by the ccs811 to the cpu over i2c. It is working.
It is as if there is an analogue problem: as soon as you really want to use the sensor, communication breaks. Maybe it is the high current needed by the MOX part, maybe the heat from the heater. I don't understand this.
Did you check your power supply. Is it strong enough? Is there an unexpected current rise?
Can you monitor the i2c traffic? At what moment doors it break down?
Can you keep talking to the chip as long as you don't switch on measuring? It's impressive that the whole flashing worked; that is a lot of successful i2c transactions sending over the firmware, without an error in the crc!
Good luck ...

Hello,
So the power supply seems strong enough.
I've been suspecting some faulty soldering since the beginning and I've re-soldered the connections and now the output looks like this:

It seems like the bit for error is up and the sensor says that the sensor resistance measurement has reached or exceeded the maximum range. I don't think this has anything to do with the pull-up resistor.
Do you have some ideas as how this can be solved? Should I start thinking about the sensor being fried, due to multiple soldering tries?

Indeed. This error code names sense.
The A means the firmware had a valid app.
The F means the app is running (and not the bootloader).
The D means measurement data is available.
So far so good.
The E means the is an error.
Then the ERROR_ID register (the upper 8 bits) give details.
You have the X set. This means, i wrote quote the datasheet "The sensor resistance measurement has reached or exceeded the maximum
range". So the MoX paste, which is heated by the heater and then reacting with the gasses on the air and then changing resistance has a value that is out of range.
If this persist, I believe this means your mox material is fried ... :-(

Hello,
It looks like my sensor was indeed fried. I've bought a new one and everything works like charm now.
Thank you so much for your help!

Pity it was fried - but happy it is working now!


Hangman bug on mobile Discord caused by style processing inside

This is actually a Discord bug (I have submitted it to them too) but I'm also submitting this in case you'd like to make your hangman game work on Discord on mobile in the mean time, too (which would be great!)
The issue is that the _ _ _ _ _ characters used for hangman are being processed as markdown code and turned into italicized text. Nadeko outputs these inside a <code> tag to stop this happening, which works as expected on desktop.
However on mobile (Android), Discord still processes the _ into style inside the <code> tag.
Unless there's some way to force the _ to show correctly then a fix for this game to work correctly as a Discord bot would be to replace the _ with another similar character.

it's using circles now instead of _, should be working fine.


parse_length_delimited_from_reader doesn't return with TcpStream on Windows

I can confirm that this issue exists on other platforms as well. I'm using Linux and coincidentally I'm working with the same thing: the kRPC mod for Kerbal Space Program.
I worked around the problem by doing this
let answer: krpc::ConnectionRespone = core::parse_length_delimited_from(&mut CodedInputStream::new(&mut stream)).unwrap();

So everything seems to work fine if I explicitly use the CodedInputStream, but it is far more convenient to just pass in the TcpStream like I can for the writeing part of the connection.
The parse_length_delimited_from_reader function mention a TODO about reading the length of the message by the way: link
Perhaps that's where the issue hides?

Closing due to old age. Please reopen if it is still relevant.


Build fails for architecture os.linux.x86_64 on windows

How to reproduce

On a Windows 10 computer clone angular-meteor-base repository (current Meteor version 1.6)
Enter dir and do meteor npm install
Try to build the app with meteor build <outdir> --server-only --architecture os.linux.x86_64

Build fails with the error:
Loading NgModules!: 0.392ms
{ Error: File to read not found or unreadable: C:/Work/angular-meteor-base/C:/Work/angular-meteor-base/client/imports/app/todo-list/todo-list.scss
    at Object.module.exports.renderSync (C:\Users\username\AppData\Local\.meteor\packages\angular-compilers\0.2.8_1\plugin.Angular_Compilers.os\npm\node_modules\meteor\angular-scss-compiler\node_modules\node-sass\lib\index.js:439:16)
    at AngularScssCompiler.compileFile (packages/angular-scss-compiler/index.js:24:25)
    at TsCompilerAotCompilerTypeCheckHostAdapter.compiler._host.loadResource.filePath [as loadResource] (packages/angular-typescript-compiler/index.js:279:45)
    at Object.get (C:\Users\username\AppData\Local\.meteor\packages\angular-compilers\0.2.8_1\plugin.Angular_Compilers.os\npm\node_modules\meteor\angular-typescript-compiler\node_modules\packages\compiler\esm5\src\aot\compiler_factory.js:78:306)
....

Important part here is the doubling of the directory for the css file C:/Work/angular-meteor-base/C:/Work/angular-meteor-base. Seems like the compiler doubles the path.
Versions

Windows 10
Meteor 1.6.1 installed, angular-meteor-base uses version 1.6 (
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Behavior

Expected: successful build
Actual: Error above

My own applicaties (with a few other Meteor sub-versions) show the same behavior. I tried to locate the source where the error occurs, but had to face that I don't know exactly which files are used when compiling...

today we've released new versions for angular-compilers with a few fixes and to support the latest Meteor 1.6.1, thanks to the great work of @ardatan !
Let us now if that solves your problem and everything works as expected.
thank you


[bridge 15/n] handle sui tx digest

Description
implements simple logic for BridgeRequestHandler::handle_sui_tx_digest. Similar to https://github.com/MystenLabs/sui/pull/15405, optimization will be added together.
Test Plan
unit tests

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes
implements simple logic for BridgeRequestHandler::handle_sui_tx_digest.

cc @jayfromthe13th


Configure Intersphinx to docs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 90.091%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2382

Relevant Lines:
2644

💛  - Coveralls


video not stop

the library is working fine till last day but today when I am using this library in app it show me everything ok but when i am stop recording it shows me nothing nor video recording file getting or no error, please help me.

hi @Poojamok and @yasirwahid, same here!!!, do you found any solution?

@elburu  Sorry buddy, i couldnt reproduce the issue since then it worked automatically and returned data. im still not sure whats wrong.


Update what-is-ip-address-168-63-129-16.md

based on internal answer to #38126

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

#sign-off


Unable to publish WDL workflow after registering

I've registered a WDL wofklow on dockstore; however I'm unable to publish the workflow because the publish button remains greyed out. When I hover over the publish button it reads "Unable to publish; no valid version found". Here is the link to the github repository: https://github.com/CDPHE/CDPHE-influenza/blob/main/tasks/irma_task.wdl
Screenshots

Desktop (please complete the following information):

Browser: Chrome

┆Issue is synchronized with this Jira Story
┆Issue Number: DOCK-2321
┆Sprint: Backlog
┆Issue Type: Story

Hi, you may find https://discuss.dockstore.org/ more timely for end user discussions. That said, are there valid versions when you click on versions?

Hi Denis,
This is what I see.
[image: image.png]
[image: image.png]
On Wed, Feb 8, 2023 at 10:57 AM Denis Yuen @.***> wrote:

Hi, you may find https://discuss.dockstore.org/
https://urldefense.proofpoint.com/v2/url?u=https-3A__discuss.dockstore.org_&d=DwMCaQ&c=sdnEM9SRGFuMt5z5w3AhsPNahmNicq64TgF1JwNR0cs&r=lAjz862iF3C7yaxZ6BQysxHkqIqhscaaqB8cpROcJNGGjp62pYdyQNO2rWgYcEwN&m=ygMtrh3stgV7Fdh1pP0tw16XFgxYXt4qDGVoeCwF6mM9FG2aEesVIwen8C4TGDZO&s=yy-c15Dtxm9gNjEsuNQ6u-UtVoqXb3HW_fSzke_fRl4&e=
more timely for end user discussions. That said, are there valid versions
when you click on versions?
—
Reply to this email directly, view it on GitHub
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dockstore_dockstore_issues_5356-23issuecomment-2D1423022267&d=DwMCaQ&c=sdnEM9SRGFuMt5z5w3AhsPNahmNicq64TgF1JwNR0cs&r=lAjz862iF3C7yaxZ6BQysxHkqIqhscaaqB8cpROcJNGGjp62pYdyQNO2rWgYcEwN&m=ygMtrh3stgV7Fdh1pP0tw16XFgxYXt4qDGVoeCwF6mM9FG2aEesVIwen8C4TGDZO&s=wRfqy0zb9fC2A3zbp-ni3SvyO63FQnbd6WzE7Ag89Pk&e=,
or unsubscribe
https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ARSCD2XCED7ZQWCQDBY4YQ3WWPNBXANCNFSM6AAAAAAUVRU4GY&d=DwMCaQ&c=sdnEM9SRGFuMt5z5w3AhsPNahmNicq64TgF1JwNR0cs&r=lAjz862iF3C7yaxZ6BQysxHkqIqhscaaqB8cpROcJNGGjp62pYdyQNO2rWgYcEwN&m=ygMtrh3stgV7Fdh1pP0tw16XFgxYXt4qDGVoeCwF6mM9FG2aEesVIwen8C4TGDZO&s=sFRK7rwbMFbXKG2OG4XVoEjXA7AZsNBvZ3qY9J_g-t0&e=
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Molly Hetherington-Rauth
PSRSII/Bioinformatican
Colorado State Public Health Laboratory
Division of Disease Control and Public Health Response (DCPHR)
Colorado Department of Public Health and Environment (CDPHE)
gender pronouns: she, her
8100 Lowry Blvd., Denver CO, 80230
desk:<PHONE_NUMBER>
@.***  | www.colorado.gov/cdphe
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.colorado.gov_cdphe&d=DwMFaQ&c=sdnEM9SRGFuMt5z5w3AhsPNahmNicq64TgF1JwNR0cs&r=yUWEGd-csUUExXVNUjlInk_amUBC0sNh_udFgdp_zAg&m=K2QGaF-9M3SauzZIeir_64m75a35tUpYk5ba3BF2tMY&s=38qMcWX8-kk64YtEQZw0tWkCrTJ08ekfo4CQi3th8lQ&e=

FYI, the images didn't really survive the conversion between email and github issues.

Ok, I think that helped narrow it down. It looks like the workflow is legitimately invalid. In the first post, you can see the github app logs button which gives this kind of input
![Screenshot from 2023-02-09 10-40-27](https://user-images.githubusercontent.com/1730679/217862116-1d1fe10d-bc87-42de-8a19-6acaed7b2129.png
(i.e. empty.json does seem missing and the are validation errors)
If you grab womtool, you should be able to re-produce these validation errors locally as well for quick iteration
$ java -jar ~/Downloads/womtool-84.jar validate workflows/influenza_assembly.wdl
Failed to import '../tasks/post_assembly_tasks.wdl' (reason 1 of 2): Failed to process task definition 'concat_post_qc_metrics' (reason 1 of 2): Failed to process expression 'write_lines(bam_results_array)' (reason 1 of 1): Invalid parameter 'IdentifierLookup(bam_results_array)'. Expected 'Array[String]' but got 'Array[File?]'
Failed to import '../tasks/post_assembly_tasks.wdl' (reason 2 of 2): Failed to process task definition 'concat_post_qc_metrics' (reason 2 of 2): Failed to process expression 'write_lines(per_cov_results_array)' (reason 1 of 1): Invalid parameter 'IdentifierLookup(per_cov_results_array)'. Expected 'Array[String]' but got 'Array[File?]'

Thanks Denis! I found the error in the WDL and I'm now able to publish!


Changes in node_modules/react-native/ files does not appear

Hi people,
I modified the file node_modules/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/location/LocationModule.java to fix a problem related to errors response. However when I reload my app always works just like in the past. It seems that react-native ignore the changes.
I tried to reboot my computer, reinstall the app, clear cache from packager but the problem stills there.
Can anyone help me please? It is a major problem,
Many thanks!

Have you tried re-building the app with react-native run-android?

Hi @ericvicenti !
Yes, I've tried it, but the problem still persists :(
Thanks

Try cleaning the java build folder. Might help?
cd android
gradlew clean

I think it's much more complicated than that. You need to actually re-build react-native from the source.
See : https://facebook.github.io/react-native/docs/android-building-from-source.html

@Exilz you are right. Many thanks!!!!


Can't get multiple strategies to work quite right

First, just wanted to say thanks for a great, (almost) simple piece of software.
Second: I'm migrating a Rails 3.2 app to greener (higher numbered) pastures. AuthLogic, which served me well forever, apparently doesn't work in 4. The warden.rb file below has been migrated from an app written a few years ago ... but I looked at your docs and it doesn't seem like the basic interface has changed. Feels like it should work.
I have two authentication strategies, httpauth and params. Params works fine.
Started POST "/user_sessions" for <IP_ADDRESS> at 2016-08-17 16:32:12 -0500
Processing by UserSessionsController#create as HTML
  Parameters: {"utf8"=>"✓", "username"=>"...."}
[AUTH] checking params
[AUTH] Authenticating user<EMAIL_ADDRESS>from params
...
[AUTH] User<EMAIL_ADDRESS>authenticated with a password.
...
Completed 302 Found in 111.5ms (ActiveRecord: 1.0ms)

However, when using httpauth (via curl):
curl http://dev.projectdomain.com/clouds/bmi.svg -u user:password

I'm expecting to see "checking httpauth" then "checking params" ... but instead I see "checking params" twice. I assume I'm asking warden twice to authenticate... not sure why it appears twice. But according to my understanding, I should also be seeing "checking httpauth". Any thoughts about why that isn't working?
development.log:
Started GET "/clouds/bmi.svg" for <IP_ADDRESS> at 2016-08-17 16:22:51 -0500
Processing by CloudsController#show as SVG
  Parameters: {"id"=>"bmi"}
[AUTH] checking params
[AUTH] checking params

Here's my config/initializers/warden.rb file:
Rails.application.config.middleware.use Warden::Manager do |manager|
  manager.default_strategies :httpauth, :params
end

Warden::Manager.serialize_into_session do |user|
  user.persistence_token
end

Warden::Manager.serialize_from_session do |id|
  User.where(persistence_token: id).first
end

class UserCredentialAuthentication < ::Warden::Strategies::Base
  def verify_against_old_credentials( user, password )
    Sha512.matches?( user.sha512_password, password, user.sha512_salt )
  end

  def transition_from_sha512!( user, password )
    user.password = password
    user.sha512_password = nil
    user.sha512_salt = nil
    user.save
  end

  def authenticate!
    Rails.logger.warn("[AUTH] Authenticating user #{username} from #{medium}")
    user = User.find_by_username_or_email(username)

    if user.blank?
      Rails.logger.warn("[AUTH] No Such User")
      fail "Invalid email or password"

    elsif user.sha512_password.not.blank? && verify_against_old_credentials( user, password )
      Rails.logger.warn("[AUTH] User #{user.email} authenticated with a SHA512 password.")
      transition_from_sha512!( user, password )
      success! user

    elsif user.password_digest && user.authenticate( password )
      Rails.logger.warn("[AUTH] User #{user.email} authenticated with a password.")
      success! user

    else
      Rails.logger.warn("[AUTH] Bad Password")
      fail "Invalid email or password"

    end
  end
end

Warden::Strategies.add(:httpauth, UserCredentialAuthentication) do
  def medium
    'httpAuth'
  end

  def valid?
    Rails.logger.warn("[AUTH] checking httpAuth")
    auth.provided? && auth.basic?
  end

  def auth
    @auth ||= Rack::Auth::Basic::Request.new(env)
  end

  def username
    auth.credentials[1]
  end

  def password
    auth.credentials[2]
  end
end

Warden::Strategies.add(:params, UserCredentialAuthentication) do
  def medium
    'params'
  end

  def valid?
    Rails.logger.warn("[AUTH] checking params")
    credential_params['username'] && credential_params['password']
  end

  def username
    credential_params['username']
  end

  def password
    credential_params['password']
  end

  def credential_params
    p = params.blank? ? post_params : params
    p['user_session'] || {}
  end

  def post_params
    @post_params ||= get_post_params
  end

  def get_post_params
    req = Rack::Request.new(env)

    if( req.post? )
      begin
        body = req.body.read
        req.body.rewind
        JSON.parse( body )
      end
    else
      {}
    end
  end
end

Cross-posted to Stack Overflow

It seems like Warden ignores more than one strategy with the same parent class. I turned that class into a module and it worked. See final code in StackOverflow.


feat: oid4vci credential configuration and metadata endpoints

Description:

Fully implement IssuerMetadata and CredentialConfiguration CRUD endpoints.
Rename oidc4vc to oid4vci to align with the official abbreviation
TODO: tests will be added in the next PR

Alternatives Considered (optional):
Link to existing ADR (Architecture Decision Record), if any. If relevant, describe other approaches explored and the selected approach. Documenting why the methods were not selected will create a knowledge base for future reference, helping prevent others from revisiting less optimal ideas.
Checklist:

[ ] My PR follows the contribution guidelines of this project
[ ] My PR is free of third-party dependencies that don't comply with the Allowlist
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked the PR title to follow the conventional commit specification

coverage: 47.134% (-0.7%) from 47.829%
when pulling d3826063dbd788839b4d404d30fff756e14935d6 on feat/cred-config-endpoints
into 2e55c6e87fd1bb46d512a95a4a9615ba25accd89 on oidc.

good work!


Use round to properly compute deso to transfer

Current dependencies on/for this PR:

main

PR #366   👈

This stack of pull requests is managed by Graphite.


Implement SSE for statistics and logging

Implement Server-Sent Events for transmitting real-time statistics and logging.

I have successfully implemented the SSE endpoint with ConsoleLogPublisher, which listens every time the application logs into the console and sends the output down the stream.


ENHANCEMENT, Add plasma THC compatibilty and functions

Can the functions described here : http://linuxcnc.org/docs/devel/html/plasma/plasmac-user-guide.html#cha:plasmac-user-guide be added ?, it would be a great enhancement
thanks

Plasma cutter support is on the roadmap. I intend to support both up/down and analog arc voltage modes, and have a separate input for a nose-in-contact-with-workpiece sensor. I would suggest a microswitch with an adjustable probe tip instead of an "ohmic" sensor so that it can deal with workpieces that have a poor electrical impedance to ground (due to paint, rust, anodizing, etc).
I won't have it done until next year sometime, though... and the software module is going to be available before it's been tested on hardware here by me, because although I have a plasma cutter in the garage, I don't have a CNC table for it put together yet, nor do I have the air system to feed it setup yet (I've got the parts, but they're still in boxes). So, expect it to not work right on the first try.

i will be happy to test and help debug, i have a full size plasma and full size laser (both 1.5 by 3 meter)

Hello, any progress about THC?
Is it posible to loan functions from:
https://github.com/UnfinishedBusiness/XmotionFirmware/tree/master/src
main.c
And port to 2560?
I have plasma table and like to test functions. Currently run it grbl-mega-5x due X-axis cloning dosn't work in this sd-card version..
Is it posible to use grbl-mega-5x instead grbl-mega at starting point from that sd-card support..?

Hello added LCD + SD-card +THC functions to mega-5X. Works atleast little but dosn't like G38.2 from sd-card, from usb same file execute normally. Not know yet why..
grbl-Mega-5XLT.tbz.zip

There was pin conflict in cpu_map.h and added plasma voltages to display, Now it works atleast I can stream file from sd-card. New sourcepack:
grbl-Mega-5XLT.tbz.zip

Added some compile options to disable useless menus/functions (for plasma cutter). Now compile 55.5kb diet version so sd-card + lcd support is only 19kb..
If you use/test it can you comment here?
known bugs is g-code error number is not shown correctly to LCD and it sends probe (G38.2) data to serial when run sd-card..
grbl-Mega-5XLT_v0.1.tbz.zip

happy to test, will get back soon

happy to test, will get back soon

Added some compile options to disable useless menus/functions (for plasma cutter). Now compile 55.5kb diet version so sd-card + lcd support is only 19kb..
If you use/test it can you comment here?
known bugs is g-code error number is not shown correctly to LCD and it sends probe (G38.2) data to serial when run sd-card..
grbl-Mega-5XLT_v0.1.tbz.zip

how to conect ? and where to setup THC settings?
Regards

Added some compile options to disable useless menus/functions (for plasma cutter). Now compile 55.5kb diet version so sd-card + lcd support is only 19kb..
If you use/test it can you comment here?
known bugs is g-code error number is not shown correctly to LCD and it sends probe (G38.2) data to serial when run sd-card..
grbl-Mega-5XLT_v0.1.tbz.zip

how to conect ? and where to setup THC settings?
Regards

how to conect ? and where to setup THC settings?
Regards
connect with usb and give settings like normal grbl..
THC voltage is analog pin 15 (if rember correct) In my board it is bed temp. Pullup resistor needs to unsolder to use with THC cap can be there. Spindle speed sets THC voltage, range some 700-1023 that converts to A15 pin ~0.6 - 1.1v range. I use 10Mohm high volt resistor coupled to 150kom resistor. so 0.015 multiplier.
Helps this any? Got any numbers to LCD?

how to conect ? and where to setup THC settings?
Regards
connect with usb and give settings like normal grbl..
THC voltage is analog pin 15 (if rember correct) In my board it is bed temp. Pullup resistor needs to unsolder to use with THC cap can be there. Spindle speed sets THC voltage, range some 700-1023 that converts to A15 pin ~0.6 - 1.1v range. I use 10Mohm high volt resistor coupled to 150kom resistor. so 0.015 multiplier.
Helps this any? Got any numbers to LCD?

Hi erosenst. Could send more detail about your proyect. for examle, any conextion diagram.

Hello, you can found connection pins in cpu_map.h. Use as normal ramps board. Base is grbl 5x + bdurbrow lcd+sd-card code. I use it in two machines currently. One is double x-axle machine and another is real 5x machine.
Bigtreetech sd-cloud wlan adaptor works fine with nautilus and I can write files over wlan to machine then run them with lcd knob..
Have you compiled it and loaded to ramps board?

I get it. Do you have any diagram to create voltage divider whithout damage analog input to arduino?

I have two coils (~10r around big EMI ferrite) connected to cutter, then 10Mohm high volt resistor + 150ohm resistor. Paraller to 150ohm resistor is paralled three 3.3v 1w zener (one is enough but I put three) and some cap. There I connect cox to arduino A15 (bed temp) and there is little coil near A15 to supress emi. This all seems to be enough and 2650 1.1v see some 0.65-0.95v volts in my setup when arc is on and HF is not grounded due two coils so it ignites fine..  Arduino is grounded through three diodes (0.6vx3) + one more difrent direction + eletrolytic cap to float little arduino ground potential..

Added some compile options to disable useless menus/functions (for plasma cutter). Now compile 55.5kb diet version so sd-card + lcd support is only 19kb..
If you use/test it can you comment here?
known bugs is g-code error number is not shown correctly to LCD and it sends probe (G38.2) data to serial when run sd-card..
grbl-Mega-5XLT_v0.1.tbz.zip

how to conect ? and where to setup THC settings? Regards

I have tried to install this version
[grbl-Mega-5XLT_v0.1.tbz
But I get a number of Compile issues;
Line 17 in DriverUtilities.h needs to be changed to;
//typedef uint8_t boolean;
and
All boolean need to be changed to bool
Then it compiles and installs
But the 4 X 4 Matrix keypad is not working??
Any advice??

OK, I edited DriverUtilities.h lines 16 and 17 to;
typedef bool boolean;
//typedef uint8_t boolean;
Both grbl-Mega-5XLT_v0.1.tbz and grbl-Mega-5XLT.tbz install fine now.
But grbl-Mega-5XLT_v0.1.tbz does not have a working keypad...


Deploy fix

This fixed the 0.6.0 release.

Why is this needed, and what exactly does it fix?

crates.io does not allow file names that exceed a certain length. Insta produces a file with the function name as file name.


Feature Request: Integrate Context Prompt Option for Improved Code Conversion

Problem Statement
The current implementation of the "codeverter" website does not offer users the ability to provide a context prompt during the code conversion process. Context prompts can be instrumental in guiding the GPT model to produce more accurate and relevant code conversions, especially in cases where the code snippet might be ambiguous or require additional clarification.
Proposed Solution
I propose adding a text input field or dialog box that allows users to provide a context prompt or additional information related to their code snippet. This context prompt should be passed along with the code snippet to the GPT model, which in turn will utilize the provided context to generate more accurate and relevant code conversions.
The context prompt input should be optional, so users who do not require additional context for their code conversion can proceed without providing one.

While this is a good idea, I worry that this might make the UI feel a bit cluttered. I feel we can do with the #9 feature first, and then co back and see if we need something like this.