Pth created but error. Cannot create index

Bug Description
I'm traning a voice with 500 epoch. Everything seems fine, but then the webpage show "error" message.
And i cannot create the index.
Expected Behavior
No error message. Index can be created
Assets
Here is the final message log.

Desktop Details:

Operating System: Windows 11 VM on unraid
Browser: default (explorer)

Additional Context
I would need to know how i can create the index with the pth file, without starting all over.

More information

The pth file is present. but the last one (epoch 500) is only 1k
So do y have to start over, or can i create the index with the pth file ?
And how to avoid this error ?

I could reboot my unraid server and the pth file appeared in the frontpage as a possible choice in the "export" area. I did a click on "create index", and it seems to work.
But i've tried and inference with this pth and index, and there is no change in the voice. So it seems my index is bad....

With the same name of the model, (set the name on the first step) and clicking the Index gen button, you can generate another index file


Disable triton FA

The CK version has better performance and more features.

Could you provide some numbers to back this claim? Namely, models with/without MoE, and vision models on Instinct MI 300, 308, 325, and Navi 3,4
In our experience triton is generally better and more robust for the general case.

It seems "export VLLM_USE_TRITON_FLASH_ATTN=0" is used everywhere... and the doc here, https://github.com/powderluv/vllm-docs
If it is better to set Triton as default, we can close this PR. Thank you.


Update pkg/gitreceive/config.go w/ v2.0.0 tags

Summary
Once the v2.0.0 milestone is closed (v2.0.0 released), the following values need to be updated to point to the appropriate Docker image tags.

so v2.0.0 has been using pre-prod slugbuilder/dockerbuilder for a while now? yeesh. Fixing this now.

Ah I'm mistaken; the chart overrides this so this has been fine.

@bacongobbler why not remove the defaults entirely and make those values required?

In the Controller we just reference canary :P

Indeed. I think that is the better approach. I will amend #376 to do so.


response json dont have an attribute called servertime

Describe your environment

Operating system: ____
Python Version: _____ (python -V)

Describe the problem:
Explain the problem you have encountered
Steps to reproduce:

Observed Results:

What happened?
What did you expect to happen?

Relevant code exceptions or logs
Code Sample, a copy-pastable example
# Your code here

logs, a copy-pastable example
// paste your log here

Hi, @yogamurthy, could you pls share more details of the issue you are facing, pls fill the questionnaire so we would be able to replicate the issue on our end, suggest solutions to you.


docs: add workflow to update dependencies

Fixes Issue
Closes #1044
Working

package-ecosystem: Specifies that the package ecosystem is GitHub Actions. This indicates that Dependabot will manage the dependencies of the GitHub Actions workflows.

labels: Assigns the label 📦 dependencies to the pull request created for dependency updates.

directory: Sets the directory where the package.json file for GitHub Actions workflows is located.

schedule: Sets the schedule for running dependency updates. In this case, it is set to run weekly.

commit-message: Sets the prefix for the commit messages generated for dependency updates. It will include chore(deps) as the prefix.

In current state of the repository, this configuration is sufficient for the workflow.

Checklist

[x] You've linked this PR to the correct issue.
[x] You have checked that the code is working correctly.
[x] You ⭐ the repository!

@Spyware007
Could you please review this pull request :)

These kinds of PRs will be merged after tmrw please wait :)

Please check #1346

@Anmol-Baranwal We can add this once the new UI is published!


[CVE-docker]Edge TLS 인증 오류

Edge에 대해 CVE 항목 검출

외 2건
테스트 사항

EdgeNode에 Kubelet 설치
Protocol 변경(Http->Https)

Edgecore service fails when installing EdgeNode kubelet
Metrics-server won't work when changed to HTTP Protocol

This is not due to an issue with the EdgeNode kubelet not installed
Occurs when modifying the Metrics-server deployment template
It is assumed that the kubelet-secure-tls option is not applied when setting hostnetwork enable and some args

No CVE vulnerability when deploying Metric-server to Master Node after excluding hostnetwork enable and some args options

The following vulnerabilities continue to occur during the validation process (Security Verification Team)
TCP timestamp response (generic-tcp-timestamp)

TCP timestamp response (generic-tcp-timestamp)
The above will be treated as an exception.


add a License to the project

Hey @afrashammi , I wonder what type of license I should add to this project

Hi @ronygolderku , we generally preferred mit licence for this projects.

Thanks @afrashammi , you are the best. I added the LICENSE file


Implement OnyxRadioGroup

Dependencies

[ ] #244

Why?
A radio group is an input control that allows a user to select (only) one value from a number of choices.
The options must only be used inside the radio group and must not be used individually.
Design
https://www.figma.com/file/YfEUBOHk4J4nYrk04geswG/onyx---Design-System-Figma-Library?type=design&node-id=626%3A15627&mode=design&t=rydWTxp4TqL9ckXI-1
Acceptance criteria

[x] multiple radio options can be put into the radio group
[x] every radio option must have a label
the following states are implemented:

[x] default
[x] hover
[x] focus-visible
[x] disabled
[x] invalid
[x] required
[x] optional
[x] checked

[x] at most one option can be selected
[x] the radio group supports a vertical and horizontal layout
[x] optionally a headline/legend can be shown above the radio group
[x] keyboard interaction is supported as documented in the ARIA pattern below

Out-of-scope:

densities
loading

Definition of Done

[x] covered by component tests
[x] screenshot tests are updated
[x] updated version + documentation is deployed

[ ] _approved by dev @larsrickert _

[ ] Storybook can show the feature

[ ] _approved by designer @jannick-ux

Implementation details

radio options are passed as property so we do not export the single radio option component so the user can not use it individually
the value is typed generically

Reference implementations

Nuxt UI
Adobe Spectrum
WaWi

Applicable ARIA Pattern
https://www.w3.org/WAI/ARIA/apg/patterns/radio/

the following value types are supported:

[ ] string
[ ] number
[ ] boolean

Can we just say that generic value is supported, or why exactly these three?

@larsrickert did you look into implementation options? Like do we implement this using native radiobuttons or custom implementation using the aria pattern? E.g. the nuxt example uses native radiobuttons.

the following value types are supported:

[ ]  string
[ ]  number
[ ]  boolean

Can we just say that generic value is supported, or why exactly these three?

I don't think to type it as "any" or "unknown" because imho all other values doesn't make sense for a radio buttons like functions, arrays or objects

@larsrickert did you look into implementation options and can give a preference? Like do we implement this using native radiobuttons or custom implementation using the aria pattern? E.g. the nuxt example uses native radiobuttons.

Not in detail...spontaneous I'd prefer native radio buttons

Note: fieldSet might be useful if the group has a title -> "legend"

tip: maybe we can add one radio button example to our form demo to verify the form behavior for a required radio group (=> blocks submit)

@JoCa96 Currently the modeValue is the whole option which can cause issues due to call by reference.
Also I think just having the value as modeValue is more convienient to work with.

@larsrickert target.value matches the id. event.target is the radio button and it's value is the options id
https://github.com/SchwarzIT/onyx/blob/d80d61eb6c007696bca6516993cf2bc5001cf94c/packages/sit-onyx/src/components/OnyxRadioButton/OnyxRadioButton.vue#L29

@larsrickert and @mj-hof Please review!

@JoCa96
radio group:

only the first radio button can be focussed with tab
(optional) we could use v-bind="option" in line 52 so we don't need to list all props

radio button:

transition duration (line 106) is not included in the durations defined by ux

@larsrickert This is the default radio button behavior. Basically the act as one control: You tab in and can then change the selection using the keyboard.

Thanks for clarification :) Its approved


Update AboutUs page, PPP and User Guide (Glen)

resolves #37

resolves #37

Codecov Report
Patch and project coverage have no change.

 Consider uploading reports for the commit 93f9a0e to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##             master      #38   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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

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


HBASE-22409 update branch-1 ref guide for Hadoop, Java, and HBase version support

Will squash into a single commit for merge.

Not sure if I should include co-authored-by for authors on the original commits.
Locally rendered and checked book
I don't think it's worth listing all the individual JIRA keys in the commit message.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
docker
1194
Docker failed to build yetus/hbase:61288f8.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/239

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/1/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
docker
191
Docker failed to build yetus/hbase:58089be.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/239

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/2/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
1051
Docker mode activated.

_ Prechecks _

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

0
mvndep
19
Maven dependency ordering for branch

+1
mvninstall
158
branch-1 passed

0
refguide
183
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1
javadoc
124
branch-1 passed with JDK v1.8.0_212

+1
javadoc
241
branch-1 passed with JDK v1.7.0_222

_ Patch Compile Tests _

0
mvndep
12
Maven dependency ordering for patch

+1
mvninstall
98
the patch passed

+1
shellcheck
0
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

-1
xml
0
The patch has 2 ill-formed XML file(s).

0
refguide
167
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1
javadoc
125
the patch passed with JDK v1.8.0_212

+1
javadoc
245
the patch passed with JDK v1.7.0_222

_ Other Tests _

-1
unit
2295
root in the patch failed.

+1
asflicense
34
The patch does not generate ASF License warnings.

4876

Reason
Tests

XML
Parsing Error(s):

hbase-resource-bundle/src/main/resources/supplemental-models.xml

src/main/site/site.xml

Failed junit tests
hadoop.hbase.ipc.TestSimpleRpcScheduler

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/239

Optional Tests
dupname  asflicense  shellcheck  shelldocs  javac  javadoc  unit  xml  refguide

uname
Linux f1937ad527a0 4.4.0-141-generic #167~14.04.1-Ubuntu SMP Mon Dec 10 13:20:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
branch-1 / 58089be

maven
version: Apache Maven 3.0.5

Default Java
1.7.0_222

Multi-JDK versions
/usr/lib/jvm/java-8-openjdk-amd64:1.8.0_212 /usr/lib/jvm/java-7-openjdk-amd64:1.7.0_222

shellcheck
v0.4.7

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/artifact/out/branch-site/book.html

xml
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/artifact/out/xml.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/testReport/

Max. process+thread count
701 (vs. ulimit of 10000)

modules
C: hbase-resource-bundle . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/3/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
0
Docker mode activated.

-1
patch
8
https://github.com/apache/hbase/pull/239 does not apply to branch-1. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem
Report/Notes

GITHUB PR
https://github.com/apache/hbase/pull/239

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/4/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

okay let me get this rebased and these specific comments addressed rather than try to handle them via additional cherry-picks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
1286
Docker mode activated.

_ Prechecks _

+1
@author
0
The patch does not contain any @author tags.

-0
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-1 Compile Tests _

0
mvndep
14
Maven dependency ordering for branch

+1
mvninstall
118
branch-1 passed

0
refguide
171
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1
javadoc
123
branch-1 passed with JDK v1.8.0_212

+1
javadoc
233
branch-1 passed with JDK v1.7.0_222

_ Patch Compile Tests _

0
mvndep
13
Maven dependency ordering for patch

+1
mvninstall
98
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

-1
xml
0
The patch has 2 ill-formed XML file(s).

0
refguide
159
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1
javadoc
119
the patch passed with JDK v1.8.0_212

+1
javadoc
229
the patch passed with JDK v1.7.0_222

_ Other Tests _

-1
unit
10457
root in the patch failed.

+1
asflicense
43
The patch does not generate ASF License warnings.

13134

Reason
Tests

XML
Parsing Error(s):

hbase-resource-bundle/src/main/resources/supplemental-models.xml

src/main/site/site.xml

Failed junit tests
hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFiles

hadoop.hbase.master.normalizer.TestSimpleRegionNormalizerOnCluster

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/239

Optional Tests
dupname  asflicense  javac  javadoc  unit  xml  refguide

uname
Linux f203b010f6a0 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
/testptch/patchprocess/precommit/personality/provided.sh

git revision
branch-1 / 60cea9e

maven
version: Apache Maven 3.0.5

Default Java
1.7.0_222

Multi-JDK versions
/usr/lib/jvm/java-8-openjdk-amd64:1.8.0_212 /usr/lib/jvm/java-7-openjdk-amd64:1.7.0_222

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/artifact/out/branch-site/book.html

xml
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/artifact/out/xml.txt

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/artifact/out/patch-site/book.html

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/testReport/

Max. process+thread count
4234 (vs. ulimit of 10000)

modules
C: hbase-resource-bundle . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-239/5/console

Powered by
Apache Yetus 0.9.0 http://yetus.apache.org

This message was automatically generated.

@busbey Can we merge this change?

yep! I think I was just waiting to get the sign-offs in place? I'll push this evening.

that works too. :)


Server Wont start

I have tried many different versions of Virtual box and vagrant and each time a clean install. Have tried to launch from Yoda and from terminal all have successful builds. I start the server then always come up with the same result.
Core3[2760]>> [New Thread 0x7fff403fd700 (LWP 2853)]
Core3[2760]>>
Core3[2760]>> Thread 52 "core3" received signal SIGILL, Illegal instruction.
Core3[2760]>> [Switching to Thread 0x7fff40bfe700 (LWP 2852)]
Core3[2760]>> 0x0000555557f54310 in sys::io::IOProcessor::pollEvents(int) ()
Core3[2760]>> (gdb)
status>> WARNING: Server state is t, it is not running or sleeping, something is wrong!

We're seeing the same issue on multiple installs, so this isn't restricted to zonamadev.
Once we work it out, I'll update here.

Okay, I've got a handle on what's causing this issue and am working on it now. Will most likely take me several days to finish.

Glad tp here it and thank you.

I've now got a PR in that should fix the issue.

Fixed the issue thanks


Example for validating email addresses

Hi, I can't seem to find an example for validating email addresses with SendGrid's new validation feature (https://sendgrid.com/solutions/email-api/email-address-validation-api/).
Thanks
Technical details:
version 7.2.5

API docs are here: https://sendgrid.api-docs.io/v3.0/email-address-validation/validate-an-email
Here's an example that can be tweaked to work with that API: https://github.com/sendgrid/sendgrid-nodejs/tree/main/packages/client#general-v3-web-api-usage-example

It may have actually taken less words to actually help...
const request = {
url: "/v3/validations/email",
body: {
email<EMAIL_ADDRESS>source: "Newsletter Signup",
},
};
client.request(request).then(([response, body]) => {
console.log(response.statusCode);
console.log(body);
});

For anyone still having trouble method: post is now required.
Example:
const request = {
  url: '/v3/validations/email',
  method: 'post',
  body: {
    email<EMAIL_ADDRESS>    source: 'Newsletter Signup'
  }
};
client.request(request).then(([response, body]) => {
  console.log(response.statusCode);
  console.log(body);
});


Add compatibility for Alpine Linux

Enable managing haproxy installations on Alpine Linux

Looking at the failed test it appears to have timed out. It's not likely my change caused this. Please can you re-run the tests?

@haqa Thanks for your contribution. Rerunning the tests.


[Bug]: to_gdal creates file with incorrect statistics

Describe the bug
In a script I only use from_gdal (reading a DEM) and to_gdal. The output TIFF receives
Band 1 Block=3081x1 Type=Float32, ColorInterp=Gray
  Min=436.726 Max=436.726
  NoData Value=nan
  Metadata:
    STATISTICS_APPROXIMATE=YES
    STATISTICS_MAXIMUM=436.7262878418
    STATISTICS_MEAN=436.7262878418
    STATISTICS_MINIMUM=436.7262878418
    STATISTICS_STDDEV=0
    STATISTICS_VALID_PERCENT=84.03

which is clearly incorrect, min!=max in the data
Expected behaviour
No response
Steps to reproduce
No response
Additional information
On Linux

I downloaded some DEM and I can't reproduce the issue. Can you share the data and script maybe?

Yes, can be closed. Nice, no work needed ;-)


Markdown checklist format for task management

Summarized Feedback from<EMAIL_ADDRESS>
Users request a markdown checklist format that can be viewed and interacted with (checked off), because this would enhance the functionality of the app for task management and planning purposes.

Close #871


Improve description for tf.test.is_gpu_available

As a part of TensorFlow docs sprints from Munich.
A small explanation for added warning - https://colab.research.google.com/drive/10pT_SQBAbZm9yVcoaACgrAlQ3YbpM_RI
cc @dynamicwebpaige

any updates on this one? @annarev @ymodak @dynamicwebpaige

oops, didn't realize it is already merged.


Expanding the VirtualColumn concept.

After this patch, virtual columns work well for aggregating, but not for grouping
(because the topN and groupBy engines don't deal well with DimensionSelectors that have
no dictionaries) or filtering (because the CursorFactories don't do anything useful
with them).
Virtual columns:

Move VirtualColumn and related classes to their own package.
Add additional methods to VirtualColumn to support more kinds of selectors and
to support cycle detection.
Add ExpressionVirtualColumn in core, offering math expressions as a virtual column.
Put cache IDs in VirtualColumnCacheHelper.

Queries:

Add VirtualColumns to timeseries, topN, and groupBy.

Aggregators:

Remove the "expression" parameter (replaced by "expression" virtual columns).

ColumnSelectorFactory:

Change getColumnCapabilities to getNativeType, since that's all anyone was using
it for, and it's simpler.
Remove "makeMathExpressionSelector" (replaced by "expression" virtual columns).

Storage adapters:

Add virtual column hooks before checking base columns. I think this ordering makes
more sense than checking base columns first, since it prevents surprises when a
new base column is added that happens to have the same name as a virtual column.

@navis, @jon-wei could you take a look please and let me know your opinion?
@navis, judging by comments on #3755, it sounds like you have different plans for how expression support should work. Part of the patch here involves them becoming only virtual columns, not being available at the ColumnSelectorFactory, Aggregator, Filter, etc levels. So that would suggest that instead of doing:
"filter" : {
  "type": "expression",
  "expression": "index > 100 && index < 200"
}

You would instead do something like:
"virtualColumns" : [{
  "type" : "expression",
  "name" : "expr",
  "expression" : "index > 100 && index < 200"
}],
"filter" : {
  "type" : "selector",
  "dimension" : "expr",
  "value" : "true"
}

And something similar for aggregators. Rather than knowing about expressions themselves, they would refer to an expression virtual column.
The JSON is a bit more complex, but the code inside is simpler (no need for filters and storage adapters to know about math expressions) and more composable. I think that's a good tradeoff since it's common for Druid users to use query generators like plywood or SQL anyway, rather than writing the queries themselves, so it shouldn't be too much of a burden.
Maybe you oversold me on the virtual column concept since now I want to use it for more things :)

Also, feedback from others would be great as well; I just called out @navis and @jon-wei since they've been doing work in this area recently.

I support having virtualColumns being their own layer that is defined by JSON in the top level of the query. FWIW Plywood has always been built on top of that concept (it is called derivedAttributes).
I think the most important objective for virtualColumns bar none is that they work everywhere, on all query types and in all query constructs. As for the complexity of the API: I think people who make ad-hock queries will opt to use the SQL capabilities and people that are writing software that makes queries programmatically will not see much of a problem.

@vogievetsky, yes, in my mind it is definitely an objective to make virtual columns work for all the things: selecting, grouping, filtering, and aggregating. With their introduction in #2511 they just work for selecting, this patch makes them work for aggregating, and future patches could make them work for grouping and filtering.

I think things are much cleaner now after doing a quick read through

Pushed another commit containing a DimensionSelector for expressions. It doesn't actually work with topN and groupBy, though, since its value cardinality is CARDINALITY_UNKNOWN which they can't handle right now.

@gianm I have some following PRs waiting on expression subject.

expression-metric-filter (#3755)
math-virtual-column (in local, not PRed yet)
virtual-column-as-dimension (in local, not PRed yet)
etc. (small things)

inline
Virtual columns:

Move VirtualColumn and related classes to their own package.

Could you postpone this till things settled down?

Add additional methods to VirtualColumn to support more kinds of selectors and
to support cycle detection.
Add ExpressionVirtualColumn in core, offering math expressions as a virtual column.

This is done in math-virtual-column. Could you wait on it?

Put cache IDs in VirtualColumnCacheHelper.

good idea.
Queries:

Add VirtualColumns to timeseries, topN, and groupBy.

I think this is done in virtual-column-as-dimension
Aggregators:

Remove the "expression" parameter (replaced by "expression" virtual columns).

I remember this is commented in previous PR. been thinking of replacing field with expression but this code looks removing expression, but ok (we should keep it as was in our version because it's already legacy, for year, for us).
ColumnSelectorFactory:

Change getColumnCapabilities to getNativeType, since that's all anyone was using
it for, and it's simpler.

good

Remove "makeMathExpressionSelector" (replaced by "expression" virtual columns).

This is for making in-line VC which is very useful. but ok, we will keep that in ours.
Storage adapters:

Add virtual column hooks before checking base columns. I think this ordering makes
more sense than checking base columns first, since it prevents surprises when a
new base column is added that happens to have the same name as a virtual column.

good

And actually, it's possible to group-by on vc with some limitations(memory pressure), something like things done in SingleScanTimeDimSelector because group-by does not rely on cardinality of dimension.

@navis thanks for the feedback. On your points:

Move VirtualColumn and related classes to their own package.

Could you postpone this till things settled down?

yes, sure, I'll move the existing classes back. I'll still create a "virtual" package for the new classes though since there won't be conflicts there.

Add additional methods to VirtualColumn to support more kinds of selectors and
to support cycle detection.
Add ExpressionVirtualColumn in core, offering math expressions as a virtual column.

This is done in math-virtual-column. Could you wait on it?

Is your impl substantially different from the one in here? If so, what's different about it? Or, if it's not really different, would the the one in here work for you?
I'm asking because the impl in here is necessary to keep some of the tests working properly, due to removal of makeMathExpressionSelector from ColumnSelectorFactory. If yours is different & better than my impl, could I merge it into this PR and replace my impl?

Remove "makeMathExpressionSelector" (replaced by "expression" virtual columns).

This is for making in-line VC which is very useful. but ok, we will keep that in ours.

I guessed you were using it for this. I see the feature is useful, but I still prefer to remove it and use explicit virtualColumns since that simplifies the code for column selectors, aggregators, and filters.
Finally, that's a good point about grouping. But I'd like to eventually modify the query engines so that we can control the memory usage. I was thinking of using a bounded memory dictionary with spilling for that (at least for groupBy, which can spill). That's a separate issue though.

Moved VirtualColumn and VirtualColumns back to original locations.

Tagged Discuss due to open questions about how to move forward with the subsystem (see also #3755 and https://groups.google.com/d/topic/druid-development/_Sd78s7yU5U/discussion).

@navis would you mind PRing "virtual-column-as-dimension" so we can see what direction you are proposing there? In this PR, not much progress is being made on treating them as dimensions… there's a dimension selector maker on VirtualColumn but it's not actually usable by the query engines or for filtering as-is. I had some vague ideas there but nothing really concrete.
In the end I'm happy throwing away most of my PR although it has some things I would like to keep:

the additional validations on VirtualColumns, including cycle detection, this helps fail fast
using VirtualColumns as the serde type instead of List, this helps fail fast too
checking VirtualColumns before base columns, this makes behavior less surprising
removing expressions from ColumnSelectorFactory and ValueMatcherFactory, this simplifies implementations (pending further discussion?)

To me only the last one seems really controversial.

Going to close this, pending resolution of the druid-development thread, since that appears to be going in a different direction. May reopen it later, scoped down a bit.


Option to turn off normal shading

Small fixes.
#5152

Thanks for the pull request @Vineg!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks for the PR @Vineg!  @lilleyse can you take a look a this?

Thanks @Vineg. Would you mind opening a separate PR for the point cloud changes so that we can focus on the geometric error fix exclusively?

Ok, tomorrow

@Vineg is this ready for review now?  Next time, make a comment when it's ready so we get notified.  We don't get notified when you push new commits.  Thanks!

@lilleyse @hpinkos this one is ready

@lilleyse I think this is ready.
@Vineg @geoscan-builder next time you push commits after a review, post a comment when the PR is ready for another look.  We don't get notifications when commits are pushed up so we missed that you were working on this.  Thanks!

Thanks for the updates @Vineg. I just tweaked a few things and updated documentation and CHANGES.md.


[Proposal] Superset Frontend Style Guidelines

The following is a proposal for high level frontend style guidelines, distilled from the many past SiPs and proposals. These high level guidelines will be the cover page for Superset's Frontend Style Guide, and we'll propose further Dos and Don'ts that conform to these guidelines and provide more actionable details for contributors. This proposal will be posted to the dev@ email list for lazy consensus before being migrated to the Superset Wiki.

Proposed Superset Frontend Style Guidelines
This is list of statements that describe how we do frontend development in Superset. While they might not be 100% true for all files in the repo, they represent the gold standard we strive towards for frontend quality and style.

We develop using TypeScript.
We use React for building components, and Redux to manage app/global state.
We prefer functional components to class components, and use hooks for local component state.
We use Ant Design components from our component library whenever possible, only building our own custom components when it's required.
We use @emotion to provide styling for our components.

We co-locate styling within component files.

We use Jest for unit tests, React Testing Library for component tests, and Cypress for end to end tests.
We add tests for every new component or file added to the frontend.
We organize our repo so similar files live near each other, and tests are co-located with the files they test.
We prefer small, easily testable files and components.
We use ESLint and Prettier to automatically fix lint errors and format the code.

We do not debate code formatting style in PRs, instead relying on automated tooling to enforce it.
If there’s not a linting rule, we don’t have a rule!

References
[SIP-36] Proposal for standardizing use of TypeScript
This SIP formally adopted TypeScript as the main language for Superset frontend, started migration work for JavaScript => TypeScript, and added the requirement that all new frontend JavaScript should be written in TypeScript instead.
[SIP-37] Proposal to implement CSS-in-JS using Emotion
This SIP formally adopted Emotion as the method for adding styling to components, describes alternatives considered, and why migration is valuable.
[SIP-48] Using Ant Design as our primary component library
This SIP replaced Bootstrap with Ant Design as our main component library, and describes how they should interact with style overrides provided by Emotion.
[SIP-56] Adopt React Testing Library for testing React components
This SIP replaced Enzyme with React Testing Library for testing React components, primarily because RTL is the most used testing framework and fully supports the newest React features.
[SIP-61] Improve the organization of front-end folders
This SIP describes how we organize our frontend folders, including how we should group different types of modules and components, where tests should be located, and how files should be named.
to: @rusackas @michael-s-molina @ktmud @graceguo-supercat @eschutho @suddjian @nytai @pkdotson @betodealmeida and anyone else who works on the frontend that I may have missed!

Yup @eschutho , totally agree about clarifying when to use Redux vs. local state. I think we'll probably write a whole dos and don'ts for that question, although it's a bit too low level for this summary proposal.
That said, if you asked me to chime in, i'd probably say:

state used by only one component should always be local, even if it's coming from an api (since it's probably good to have updated state in cases where a component is unrendered then rerendered)
state used by more than one component should always be in Redux (I feel less strongly here, and could see arguments either way, but having a hard and fast rule might make our lives easier and prevent that grey area from existing)

I'm not a huge fan of Redux anyway, so i'll leave the decision making regarding state to those with more experience, more passion, and less angst 😅

where does that fall?

@eschutho @etr2460 People with experience and interest in Redux can write a proposition of dos and don'ts similar to what @rusackas did for Style/CSS here. Then submit it for lazy consensus. After approval, it will become a page under Front End Guidelines. I think this will be a good process for all the topics.

@etr2460 and @michael-s-molina thank you both for that feedback. A few of us are going to be working on cleaning up Redux state over the next few months, so we'll also start to write down some guidelines as we go along and share them out to the community to iterate on.


Error: failed to load burp bug

When I try to load up an empty Kaboom game, it is giving me the error: “Error: failed to load burp.” But I have nothing in the project. What’s wrong with it?

Where are you "loading" an empty Kaboom game?

the best bug name.
it may be due to your browser or your internet connection, but tga can probably help you to detect the problem. If you can reopen the issue using the template that would be great

What browser are you using? Are you able to load any other audio file?
Maybe your browser doesn't support certain web audio api. But anyway since it's loaded by default I changed it to not block the game in future versions.

bro it’s been 4 months im not sure about loading audio files, I wasn’t loading any.also I was using vs code live previewOn Sep 25, 2022, at 9:33 PM, tga @.***> wrote:
What browser are you using? Are you able to load any other audio file?
Maybe your browser doesn't support certain web audio api. But anyway since it's loaded by default I changed it to not block the game in future versions.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

For load audios you can do
/// use any file path you have
loadSound("n", "music.mp3");
play("mp3");

Anyway, in @next versio this no longer block game. Reopen if you have the same bug playing audios

There's a problem with that. I wasn't loading *any *audio files at all. It
was a blank project, and i never tried to load anything.
On Tue, Oct 4, 2022 at 10:52 AM danie @.***> wrote:

For load audios you can do
/// use any file path you haveloadSound("n", "music.mp3");play("mp3");
Anyway, in @next versio this no longer block game. Reopen if you have the
same bug playing audios
—
Reply to this email directly, view it on GitHub
https://github.com/replit/kaboom/issues/585#issuecomment-1267217075, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARS76ZJ3PO2YII3XSAX4Q2TWBRHEHANCNFSM5V72TORQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Using a webserver running before KNX Library

Hi,
To test the option of using a webserver that is already running, I modify one of the webserver examples of Arduino IDE.
First of all, it is very important to pass to the KNX Library, the already running webserver, as a pointer, so:

If in your program, the server is defined like:

ESP8266WebServer server ( 80 );
you have to use:
knx.start(&server);

If in your program, the server is defined like:

ESP8266WebServer *server;
server = new ESP8266WebServer ( 80 );

you have to use:
knx.start(server);
And also to modify the esp-knx-ip.h to have #define ROOT_PREFIX  "/knx"
Following is a working example of that.

@envy, can be added the ROOT_PREFIX directly to knx.start(&server)?
To be something like knx.start(&server, "/knx");
Will be very handy that, and also there is no need of modifying the library to use this feature.
What do you think?

Example:
/*
 * Copyright (c) 2015, Majenko Technologies
 * All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without modification,
 * are permitted provided that the following conditions are met:
 *
 * * Redistributions of source code must retain the above copyright notice, this
 *   list of conditions and the following disclaimer.
 *
 * * Redistributions in binary form must reproduce the above copyright notice, this
 *   list of conditions and the following disclaimer in the documentation and/or
 *   other materials provided with the distribution.
 *
 * * Neither the name of Majenko Technologies nor the names of its
 *   contributors may be used to endorse or promote products derived from
 *   this software without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 * WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR
 * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
 * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
 * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
 * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
 * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

#include <ESP8266WiFi.h>
#include <WiFiClient.h>
#include <ESP8266WebServer.h>
#include <ESP8266mDNS.h>

#include <esp-knx-ip.h>            // KNX Library
#define KNX_ROOT_PAGE    "/knx"    // KNX Root page. On web browser put <ip>/knx, where <ip> is the IP of the device. You can see the IP from the serial console.

const char *ssid = "SSID";
const char *password = "PASS";

ESP8266WebServer server ( 80 );

const int led = 13;

void handleRoot() {
	digitalWrite ( led, 1 );
	char temp[400];
	int sec = millis() / 1000;
	int min = sec / 60;
	int hr = min / 60;

	snprintf ( temp, 400,

"\
  \
    <meta http-equiv='refresh' content='5'/>\
    <title>ESP8266 Demo</title>\
    \
  \
  \

Hello from ESP8266!
\

Uptime: %02d:%02d:%02d
\
    \

\

KNX
\
  \
",

		hr, min % 60, sec % 60
	);
	server.send ( 200, "text/html", temp );
	digitalWrite ( led, 0 );
}

void handleNotFound() {
	digitalWrite ( led, 1 );
	String message = "File Not Found\n\n";
	message += "URI: ";
	message += server.uri();
	message += "\nMethod: ";
	message += ( server.method() == HTTP_GET ) ? "GET" : "POST";
	message += "\nArguments: ";
	message += server.args();
	message += "\n";

	for ( uint8_t i = 0; i < server.args(); i++ ) {
		message += " " + server.argName ( i ) + ": " + server.arg ( i ) + "\n";
	}

	server.send ( 404, "text/plain", message );
	digitalWrite ( led, 0 );
}

void setup ( void ) {
	pinMode ( led, OUTPUT );
	digitalWrite ( led, 0 );
	Serial.begin ( 115200 );
	WiFi.mode ( WIFI_STA );
	WiFi.begin ( ssid, password );
	Serial.println ( "" );

	// Wait for connection
	while ( WiFi.status() != WL_CONNECTED ) {
		delay ( 500 );
		Serial.print ( "." );
	}

	Serial.println ( "" );
	Serial.print ( "Connected to " );
	Serial.println ( ssid );
	Serial.print ( "IP address: " );
	Serial.println ( WiFi.localIP() );

	if ( MDNS.begin ( "esp8266" ) ) {
		Serial.println ( "MDNS responder started" );
	}

	server.on ( "/", handleRoot );
	server.on ( "/test.svg", drawGraph );
	server.on ( "/inline", []() {
		server.send ( 200, "text/plain", "this works as well" );
	} );
	server.onNotFound ( handleNotFound );
	server.begin();
	Serial.println ( "HTTP server started" );

   // Set physical address (1.1.1)
  knx.physical_address_set(knx.PA_to_address(1, 1, 1));
  knx.start(&server);
  //knx.start(&server, KNX_ROOT_PAGE);
}

void loop ( void ) {
	server.handleClient();
  knx.loop();
}

void drawGraph() {
	String out = "";
	char temp[100];
	out += "<svg xmlns=\"http://www.w3.org/2000/svg\" version=\"1.1\" width=\"400\" height=\"150\">\n";
 	out += "<rect width=\"400\" height=\"150\" fill=\"rgb(250, 230, 210)\" stroke-width=\"1\" stroke=\"rgb(0, 0, 0)\" />\n";
 	out += "<g stroke=\"black\">\n";
 	int y = rand() % 130;
 	for (int x = 10; x < 390; x+= 10) {
 		int y2 = rand() % 130;
 		sprintf(temp, "<line x1=\"%d\" y1=\"%d\" x2=\"%d\" y2=\"%d\" stroke-width=\"1\" />\n", x, 140 - y, x + 10, 140 - y2);
 		out += temp;
 		y = y2;
 	}
	out += "</g>\n</svg>\n";

	server.send ( 200, "image/svg+xml", out);
}

I think this explanation of how using the KNX.start when having an already running webserver should be on the wiki or in an example.


error installing plugin in ghidra 11.0.1

When attempting to install the plugin using the bare template ghidra can successfully add the plugin to the $GHIDRA_HOME/.ghidra<version>/Extensions/ folder and list it as available. But when you attempt to install the plugin you get the following error message.

2024-03-10
13:46:24
ERROR
(ExtensionTableModel) Unable install an extension that no longer exists. Restart Ghidra and try manually installing the extension: 'upstream-template'

(upstream-template is the folder that the ghidra-kotlin-extension-template was cloned into).
I'm not entirely sure what going on as i havent debugged this at all, but would appreciate some advice on how to either solve or track this down since i would 100% rather write kotlin that java.

https://github.com/NationalSecurityAgency/ghidra/blob/master/Ghidra%2FFramework%2FProject%2Fsrc%2Fmain%2Fjava%2Fghidra%2Fframework%2Fproject%2Fextensions%2FExtensionTableModel.java#L166
Saving this here to debug for later

Ah, pretty sure it just needs a Module.manifest, will check when I get back to my office

Good catch, thank you very much!
I think I never noticed this because I only used this template repo for extensions I was using in an IDE and never shipped them. IntelliJ adds the classes to the classpath by default which probably bypasses these checks.


Update actor-model.md

fix typo
Rendered: https://wiki-git-xrdavies-patch-1-editors.vercel.app

This pull request is being automatically deployed with Vercel (learn more). To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/editors/wiki/2ukDidhCSkERqEJHHVoGbRm1Vsp6 ✅ Preview: https://wiki-git-xrdavies-patch-1-editors.vercel.app

The preview deployment reflects the modification correctly.


Add UK government API catalogue

This isn't "an" API but the UK government site where they are collated.
I've added the data.gov.uk site as a separate entry for clarity (because of the number of similar sites from other countries). This site is also linked to from the API catalogue site.
Thank you for taking the time to work on a Pull Request for this project!
To ensure your PR is dealt with swiftly please check the following:

[x] Your submissions are formatted according to the guidelines in the contributing guide
[x] Your additions are ordered alphabetically
[x] Your submission has a useful description
[x] The description does not end with punctuation
[x] Each table column should be padded with one space on either side
[x] You have searched the repository for any relevant issues or pull requests
[x] Any category you are creating has the minimum requirement of 3 items
[x] All changes have been squashed into a single commit

Thanks for the contribution @sihugh!
Can you please resolve the conflict?

@marekdano conflict resolved, thank you :-)


Provide support for completion callbacks on subsets of plans

Idea 1 for API
Blocked-based
Pros:

Obvious which plans are part of the activity group.

Cons:

Requires an extra layer of scope (not really a big deal).

runtime.activityGroup {
  runtime.addPlan(tween, to: layer)
}.onStateChange { state in
  if state == .idle {
    // Do something.
  }
}

Idea 2 for API
runtime.addPlan(tween, to: layer) {
  // Invoked on idle
}

runtime.addPlans([tween], to: layer) {
  // Invoked on idle
}

For Idea 2 I could argue for the callback being called on any state change.

Idea 3 for API
let group = runtime.beginActivityGroup()
group.onActiveStateChange = {
  // Do something
}
runtime.addPlan(...)
group.endActivityGroup()

Rough plan of work ahead:

Modify token generator API to require a plan object.
Add activate and deactivate APIs to the token, allowing their reuse.
Update downstream APIs with new token generation APIs.
Build new activity group API to verify that the per-plan tokens enable this to be built.
Cut releases.

Example token generator API:
let token = tokenGenerator.generate(forPlan: plan)
token.activate()
token.deactivate()

Core animation implementation:
guard let token = tokenGenerator.generate(forPlan: tween) else { return }
token.activate()

CATransaction.begin()

CATransaction.setCompletionBlock {
  token.deactivate()
}

target.add(animation, forKey: nil)

CATransaction.commit()

Gesture implementation:
var gestureTokens: [UIGestureRecognizer: [IsActiveTokenable]] = [:]
func addPlan(_ plan: Plan) {
  let plan = plan as! Gesturable

  ....

  gestureTokens[gestureRecognizer].append(tokenGenerator.generate(forPlan: plan))
}

func handle(gesture: UIGestureRecognizer) {
  if gesture.state == .began && gestureTokens[gesture] == nil {
    gestureTokens[gesture].forEach { $0.activate() }

  } else if gesture.state == .ended || gesture.state == .cancelled {
    gestureTokens[gesture].forEach { $0.deactivate() }
  }
}


Develop monitoring workflow for basic test of Legacy Registry

💡 Description
We need some sort of checks so we can see this immediately.
⚔ Parent Epic / Related Tickets
No response

Closed by:

https://github.com/NASA-PDS/monitoring/commit/0133632d9ed0aae709d18a32c27c340b253c2593
https://github.com/NASA-PDS/monitoring/commit/182a762eb2f393d5590c63936ee315f8b50e29a2
https://github.com/NASA-PDS/monitoring/commit/82f6bbf1acd5fe06181ef3a8478c981f8afe54d1
https://github.com/NASA-PDS/monitoring/commit/d4b0250ae5f5b8da36411643174658834081d39e


Reduce startup time

Starting a new REPL takes 5 to 10 seconds. This should be decreased, as this becomes annoying if you are using tmux and launch a new shell for each program you are working with.

 We should be able to work around the usage of scalac in the case where everything is cached. That will speed it up considerably
Another 1000s is spend initializing Scalaparse for the first time. I'm not sure how much of that time is spent classloading and how much is spent in the static initializers, but it seems plausible we could speed it up

@laci37 do you want to take a crack at this? I have an idea that should save us the 1600ms to initialize scalac:

Cache the result of compileClass(preprocess(...)) instead of just compileClass(...)
Initialize Interpreter#compiler only on demand
After showing the prompt, kick off compilation asynchronously for a simple string like 1 + 1 to try and get the compiler running before the user enters their first input

This would involve some refactoring to move the caching bits into the correct place, but I'm pretty sure it'll work. That'll bring our startup time into the 1-2s range which is not fast, but not bad =)

We could also trivially cache the output of the Parsers.split call, which would allow us to defer that initialization to after we show the prompt, which can also be kicked of asynchronously

I think one should allow for Ammonite-REPL to be a non-JVM program connecting to a daemon JVM running Ammonite sessions, though not all will want to use that. That can be done using NailGun (github.com/martylamb/nailgun). The daemon JVM should try to keep one prespawned session. This would allow literally instant startup, since nailgun's client is written in C. I've used this in the past for Blaisorblade/git-filter-branch-msgs, so that I could use invoke a JVM program inside a bash loop.

Nailgun is a client, protocol, and server for running Java programs from the command line without incurring the JVM startup overhead.

I think one should allow for Ammonite-REPL to be a non-JVM program connecting to a daemon JVM running Ammonite sessions

Yep! @laci37 actually wanted to do that and it was part of the original GSOC proposal. We've since been distracted with other slightly-more-high-pri things, but we could always revisit.
If anyone else wants to take a shot at daemonizing Ammonite's JVM at this feel free to take a crack at it and prove out what it'd take.

A persistent daemon comes with all kinds of problems when it runs for a long time. The most obvious is that when we import the same library in different versions, we can fill up the class cache. So I would advise against it. (At most, use a daemon only for coordination, like how "universal" environment variables are done in fish shell)
My suggestion: Use the approach (or even the code) from Drip: Spin up VMs in a pool and use these already initialized VMs from the pool. Fill up the pool in the background as needed.
In a simple test, I get "startup" times at about 0.126 seconds for Ammonite (with jdk1.8.0_25). Bash needs 0.063 seconds and Dash 0.032 seconds on the same machine. This looks good enough for me.

Interesting point about the daemon. And Drip is already designed to be incorporated. Thanks for the pointer!

In a simple test, I get "startup" times at about 0.126 seconds for Ammonite (with jdk1.8.0_25). Bash needs 0.063 seconds and Dash 0.032 seconds on the same machine. This looks good enough for me.

I thought you meant from bash, failed to reproduce, and then I realized you might mean from Drip. I'll try the latter, seems easy enough.

@Blaisorblade I got the comparison times with time bash -c exit (and the same with dash instead of bash). I tested Ammonite mainly by replacing java with drip in the startup file. But I didn't get a full successful start: At one point Ammonite seems to play around with the file descriptors, which confuses Drip. But for a simple indication about what startup times to expect this should be good enough.

@Blaisorblade With the newest version of Ammonite I have no problems with file handles any more. But the effect of Drip is not as big as before.
$ time java -cp amm ammonite.repl.Repl -c exit
        4.66 real        12.09 user         0.51 sys
$ time drip -cp amm ammonite.repl.Repl -c exit
        5.11 real        13.11 user         0.55 sys
$ time drip -cp amm ammonite.repl.Repl -c exit
        4.81 real         0.05 user         0.07 sys

So I get startup time from 16 seconds down to under 5 seconds. Nice, but not as great as in the previous measurement,

Nice, but not as great as in the previous measurement,

I don't have time to contribute, but I'd like to point out how to interpret those data.
That doesn't mean that Drip is not going to help, just that there's some fiddling (or maybe refactoring) to do to get the benefits. From the description (and my experience with nailgun) I'd assume that by using Drip should still allow a small startup (like 0.1 s).
This snippet from Drip's docs sounds relevant:

By default, Drip only loads your main class at startup, but you can tell Drip to run additional code at startup.

This suggests that the new version of Ammonite moved some initialization code to later, so that the work is not done early enough (can't confirm without knowing the versions, but also doesn't necessarily matter).
Quite possibly, one would need to refactor initialization to be compatible with Drip, to separate what can be done before startup, from the code that can only be run when the user starts Ammonite (e.g. anything using the current directory, environment variables or startup parameters).

Just for fun, I experimented with nailgun integration and got some positive results for running Scala scripts, see diff: https://github.com/olafurpg/Ammonite/pull/1/commits/381680e5501080e7d4890c24d49b77ede12d8965
To run it:

install nailgun client (for example on OSX, brew install nailgun)
run sbt amm/pack
start server ./amm/target/pack/bin/amm_ng
run ng ammonite.Main <args> instead of typical amm <args>

Scala scripts work like a charm. Rough numbers from compiling a new file on a warm sever:

single file: ~0.3s
import $file: ~0.5s
import $ivy: ~1.0s

With a file watcher like entr, I can run a script on every file save
ls foo.sc | entr ng ammonite.Main foo.sc

The repl doesn't work. Pressing up/down/ctrl-c is broken for some
reason. I think the input/output/error streams are injected correctly from nailgun. However, this is not an issue for me, since I rarely exit/restart the repl. Scala scripts is another story entirely.
I am sure @geggo98 raised some legitimate concerns about having a persistent daemon running. Regularly restarting the server might be a solution for that.

The repl doesn't work. Pressing up/down/ctrl-c is broken for some
reason. I think the input/output/error streams are injected correctly from nailgun.

If anybody is interested in fast shell startup, the basic problem is that nailgun offers only a socket forwarding to a terminal, and TTY detection only sees a socket and not a terminal. In fact, nailgun's redirection is done at the Java level and might not even affect the native stdin/stdout/stderr file descriptors (https://github.com/martylamb/nailgun/blob/1ad9ad9d2d17c895144a9ee0e7acb1d3d90fb66f/nailgun-server/src/main/java/com/martiansoftware/nailgun/NGSession.java#L257-L265).
To see this forwarding problem, observe the perfect stream forwarder (cat) fail at this.
$ cat|stty -a
stty: stdin isn't a terminal

One hacky but relatively easy-ish fix would be that Ammonite's calls to stty/tput/whatnot should be called by the nailgun C server on the original terminal. (See e.g. https://github.com/lihaoyi/Ammonite/blob/2eae411608cd4f7b779ba5211f4b145f4fda6937/terminal/src/main/scala/ammonite/terminal/Utils.scala#L84-L131). This fix still requires hacking some C code, but the C nailgun code is small.
A cleaner fix is harder: nailgun (or a replacement) could offer a virtual terminal rather than a pipe to the process, and forward terminal commands. That would be cleaner but much harder (if it is feasible at all), and UNIX terminal APIs are a mess and non-portable. No clue on Windows. I suspect this would only work with some existing terminal emulator...  You'd probably want some expect variant, but not in Tcl please. Luckily, there are a few in Java: https://en.wikipedia.org/wiki/Expect#Java
Finally, here's a testcase showing that expect does better forwarding than cat. I'm not sure if those "pure Java" implementations achieve the same.
$ expect -c "system stty"
speed 38400 baud;
lflags: echoe echok echoke echoctl pendin
iflags: -ixany iutf8 ignpar
oflags: onocr onlret
cflags: cs8 -parenb

I am not convinced it's worth the effort to get the repl running via nailgun. In my experience, repl sessions usually stay open several minutes if not hours.
I hacked together a script ss (short for scala script) to automatically manage the nailgun server.
#!/bin/bash
set -e

command -v ng &> /dev/null
command -v amm_ng &> /dev/null
command -v entr &> /dev/null

startNailgun() {
  echo "Starting nailgun..."
  amm_ng &
  sleep 1
  ng ng-alias amm ammonite.Main
}

usage() {
  cat << EOF
ss [file]      # run scala script
ss loop [file] # continuously run script on file save
ss restart     # restart nailgun server
ss help        # print this help message
EOF
}

if [ $1 = "help" ]; then
  usage
elif [ "$1" = "restart" ]; then
  ng ng-stop || true
  sleep 1
  startNailgun
else
  ng ng-stats &> /dev/null || startNailgun
  if [ "$1" = "loop" ]; then
    shift 1
    ls "$@" | entr time ng amm "$@"
  else
    ng amm "$@"
  fi
fi

I don't know if this should be bundled with ammonite, but it's already pretty useful for myself.

My current inclination is to bundle the file-watching ability as part of the amm executable (https://github.com/lihaoyi/Ammonite/issues/364); that way you'd run amm --watch or something on a script, and it would keep the JVM open and re-instantiate the Repl object every time it notices a change and re-run it on the script.
That should give us the benefits of a warm JVM without the complexity of dealing with nailgun and all that, as long as we're happy with just the --watch functionality and don't care about other uses of nailgun e.g. run a script ad-hoc and having it start fast. It would be far simpler to implement too, and would be familiar to users of the many build tools which have --watch-style functionality built in (conversely, very few build tools keep long-running daemons around in the background)

A --watch flag would eliminate the need for nailgun in my case. I care most about having a tight edit-run-debug cycle. Once a script is ready, the JVM startup penalty becomes less of an issue.
I agree that the long-running daemon setup is error-prone and it would be best to get away without it, if possible.

I've needed Scala scripts with fast startup—once (because most of my scripting is in bash). I also think @olafurpg's code is in fact simple enough for inclusion for those interested, especially to use Ammonite to replace bash scripting. But I understand the maintenance burden might matter.
But in my case since the nailgun integration was easy enough to do it on my own, I'm currently fine with leaving this use case open.
https://github.com/Blaisorblade/git-filter-branch-msgs/blob/master/src/filterbranch/EchoTranslate.scala#L161-L180

The current state (~1s startup overhead for hello world) is we seem bottlenecked on classloading time:

Given that, I think this is about as good as it'll get for now, short of something really clever happening around scala-{native, js}


Laravel 11.x Shift

This pull request includes the changes for upgrading to Laravel 11.x. Feel free to commit any additional changes to the shift-111754 branch.
Before merging, you need to:

Checkout the shift-111754 branch
Review all pull request comments for additional changes
Run composer update (if the scripts fail, try with --no-scripts)
Clear any config, route, or view cache
Thoroughly test your application (no tests?, no CI?)

If you need help with your upgrade, check out the Human Shifts.

:information_source: To slim down the Laravel installation, Laravel 11 no longer has most of the core files previously included in the default Laravel application. While you are welcome to publish and customize these files, they are no longer required.
Shift takes an iterative approach to removing core files which are not customized or where its customizations may be done elsewhere in a modern Laravel 11 application. As such, you may see some commits removing files and others re-registering your customizations.

:information_source: Shift detected customized options within your configuration files which may be set with an ENV variable. To help keep your configuration files streamlined, you may set the following variables. Be sure adjust any values per environment.
AUTH_PASSWORD_RESET_TOKEN_TABLE=password_resets
BCRYPT_ROUNDS=10
CACHE_STORE=file
DB_CHARSET=utf8mb4
DB_COLLATION=utf8mb4_unicode_ci
DB_CONNECTION=mysql
MAIL_MAILER=smtp
QUEUE_CONNECTION=sync
SESSION_DRIVER=file

Note: some of these may simply be values which changed between Laravel 10 and Laravel 11. You may ignore any ENV variables you do not need to customize.

:information_source: Laravel 11 no longer requires you to maintain the default configuration files. Your configuration now merges with framework defaults.
Shift streamlined your configuration files by removing options that matched the Laravel defaults and preserving your true customizations. These are values which are not changeable through ENV variables.
If you wish to keep the full set of configuration files, Shift recommends running artisan config:publish --all --force to get the latest configuration files from Laravel 11, then reapplying the customizations Shift streamlined.

:x: Shift detected you are using laravelcollective/html. This package has been abandoned. They suggest using the spatie/laravel-html package instead. You may use Shift's HTML Converter to automate this conversion. However, if you are not using the laravelcollective/html package extensively, you may simply rewrite its uses to raw HTML.

:warning: The BROADCAST_DRIVER, CACHE_DRIVER, and DATABASE_URL environment variables were renamed in Laravel 11 to BROADCAST_CONNECTION, CACHE_STORE, and DB_URL, respectively.
Shift automated this change for your committed files, but you should review any additional locations where your environment is configured and update to the new variable names.

:information_source: Shift detected your application has a test suite. To allow your to verify the upgrade in isolation, Shift did not bump your testing dependencies for PHPUnit 10. Once you have completed your upgrade, you may run the PHPUnit 10 Shift for free to upgrade your test suite to PHPUnit 10 separately.

:information_source: Shift updated your dependencies for Laravel 11. While many of the popular packages are reviewed, you may have to update additional packages in order for your application to be compatible with Laravel 11. Watch dealing with dependencies for tips on handling any Composer issues.

:information_source: Starting with Laravel 10, PHP type hints were added within classes included in a Laravel application. In an effort to modernize your code, Shift automated this change where Laravel strictly specifies a type. If you prefer not to type hint your code you may revert this commit by running: git revert 5a0e6e2a

:information_source: The base Controller class has been marked as abstract in Laravel 11, with its traits and inheritance removed. This is to prevent using this base controller directly and to use facades instead of the trait methods.
Shift detected your base controller did not have any public methods, so it was safe to mark as abstract. However, since you may be using trait methods within your controllers, Shift did not remove them. If you know you are not using any trait methods or want to refactor to facades, you may remove them manually.

:information_source: Laravel 11 now updates the timestamp when publishing vendor migrations. This may cause problems in existing applications when these migrations were previously published and ran with their default timestamp.
To preserve the original behavior, Shift disabled this feature in your database.php configuration file. If you do not have any vendor migrations or have squashed all of your existing migrations, you may re-enable the update_date_on_publish option. If this is the only customization within database.php, you may remove this configuration file.

:warning: Laravel 11 has removed its dependency on doctrine/dbal. Shift detected your project contains this dependency. If you are not using this package directly or were only using it for change migrations, you may remove it by running: composer remove doctrine/dbal

:warning: Previously, Laravel would append a colon (:) to any cache key prefix for DynamoDB, Memcache, or Redis. Laravel 11 no longer appends a colon to your cache key prefix. If you are using one of these stores, you should append a colon to your prefix to avoid invalidating your cache.

:information_source: All of the underlying Symfony components used by Laravel have been upgraded to Symfony 7.0. Shift detected references to Symfony classes within your application. These are most likely type hints and can safely be ignored. If you are using Symfony classes directly or experience issues relating to Symfony, you should review the Symfony change log for any additional changes.

:warning: Laravel 11 requires PHP 8.2 or higher. You should verify the PHP version in your environments to ensure it meets this new requirement.

:warning: Laravel 11 now includes a database driver for MariaDB. Previously the MySQL driver offered parity with MariaDB. However, with MariaDB 10.1, there are more database specific features available. If you are using MariaDB, you may want to evaluate this new mariadb driver after completing your upgrade to Laravel 11.

:tada: Congratulations, you're now running the latest version of Laravel!
Next, you may optionally run the following Shifts to ensure your application is fully upgraded, adopts the latest Laravel conventions, and easier to maintain in the future:

Laravel Fixer automatically updates your code to the latest Laravel conventions.
Tests Generator intelligently generates model factories, HTTP Tests, and configuration for your application.
CI Generator intelligently generates CI jobs to lint PHP, check code style, and run tests, including Dusk.

You may also use the Shift Workbench to automate common tasks for maintaining your Laravel application.


Make ConverterInstanceFactory threadsafe

Resolves: #124
Makes the QueryStringConverterInstanceFactory thread safe by using a
concurrent dictionary to store the actual instances.

Hi @jterry75, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Justin Terry (VM)). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

LGTM.  I'll wait to hear from @Ecroyd before merging.


Is there any way to make adhesion active for only contacts with specific object types?

Hi,
I'm looking for some help with the adhesion actuator.
I was playing with the active adhesion example here and wondered if it is possible to make adhesion active for contacts with specific object types. For example, the red box in this example is adhesive to everything. However, I am wondering if it is possible to make it adhesive only to green objects and not to gray crate.
Thank you in advance for any help!

Just FYI, I want to make something like magnets. So, if there is any way to make magnets in MuJoCo, it would be nice to know it.

If you disable contacts between two bodies using the regular methods (exclude or contype/affinity) then adhesion will not work, but they will also be able to penetrate.
If you want solid state magnets, which you will not be able to turn on/off using an actuator, that would be fairly easy to do. Is that what you want? Or is controllability important for your use case?

It seems like an interesting idea. Bodies could have a "stickiness" parameter, say between 0 and 1, that multiplies the adhesion force. The value of 1 would be equivalent to the current implementation.

Hi Yuval,
Thanks a lot for your help!

If you want solid state magnets, which you will not be able to turn on/off using an actuator, that would be fairly easy to do.

Yes, I need solid state magnets. An example of the thing I want to make is Magsafe cable of Mac. I am sorry for not detaling about what I want to make.
I am also sorry that I was aware of exclude but not contype. After reading the description about contype, I think I figuired out how to implement solid state magnets.
So, I think I need to set adapter's conaffinity to 2, and socket's contype/conaffinity to 2. Then, since adapter's contype is 1, the adapter still collides with usual objects, whose default conaffinity is 1, while the socket is adhesive only to the adapter (presicely speaking geom with contype/conaffinity=1).
Am I right, and this is how contype/affinity are supposed to be used?

Hi Roman,

It seems like an interesting idea. Bodies could have a "stickiness" parameter, say between 0 and 1, that multiplies the adhesion force. The value of 1 would be equivalent to the current implementation.

Oh, I didn't think about this idea, but I agree this is an interesting idea.
So, with this stickness parameter, for example, we can create weak and strong magnets. Am I right?

So, with this stickness parameter, for example, we can adjust the magnetic susceptibility of objects (like metal has higher magnetic susceptibility while wooden objects have no magnetic susceptibility). Am I right?

Yup, this is exactly what I meant. It's a parameter of the body the magnet is acting on. It would also apply to modeling suction grippers and any other type of adhesion modeling.

This is not how we would do it. Magnets can repel.
You would specify a magnet dipole axis and strength in physical units, I think best associated with a site, and then get the proper interaction wrench.
Need to read up on magnetostatics but should be straightforward.


feat: implementing trie to regexp conversion

This feature will allow you to compile a regular expression from a Trie.
There are three flavors for that:

Partial match regular expression:
You can generate a regular expression that test returns true when there is a partial match with the Trie. This regular expression will have a performance slightly higher than the arrTrie

const regex = trieToRegExPartial(trie);

Perfect match regular expression:
You can generate a regular expression that test returns true when there is a perfect match with the Trie. This regular expression will have a performance significantly higher than the arrTrie

const regex = trieToRegExPerfect(trie);

Full Trie match regular expression:
You can generate a TrieRegexp, which will have a new method, match, that returns MatchType.PERFECT for a perfect match, MatchType.PARTIAL for a partial match, or MatchType.NONE for no match! This TrieRegExp between the trie and arrTrie, but almost as good the arrTrie when no match is found, and slightly higher than the normal Trie, when a match occurs!

const regex = trieToRegEx(trie);

Here it is the local benchmark:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

v1.1.0
npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


hackey update to ModelConfig to allow lora_target_modules="all-linear"

the type hint forces a list which raises a "all-linear" layer not found. forcing a string makes it work. updating the type hint to Union[str, list[str]] also raise a parsing error
looks like peft handles this by making the arg a str and using comma delimited values
https://github.com/huggingface/peft/blob/main/examples/sft/train.py#L30

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


golang filter: add lock in the Go side to avoid concurrency race

Since people may use multiple goroutines to process the same stream, so, there might be concurrency happens.
fields we should protected:

Go side headerMapImpl.headers and concurrency for read/write this map.
C++ siede httpRequestInternel.strValue, see a example: https://github.com/mosn/envoy-go-extension/pull/64/files
maybe others.

Many thanks @StarryVae!  Is this issue considered done?

yeah, it is basically done by this pr #27959

consider done in https://github.com/envoyproxy/envoy/pull/27959


dateparser-0.3.4 incompatible with python-dateutil-2.5.3: 'tuple' object has no attribute 'slots'

Description
If I install dateparser through pip, python-dateutil-2.4.2 gets pulled as a dependency and all works fine. However, I frequently update my packages (blindly, I must say) and sometimes other packages require a more recent version. In this case, an update pulled in python-dateutil-2.5.3, which broke dateparser. The cause of the problem was quite hard to find.
The error I get is: AttributeError: 'tuple' object has no attribute '__slots__'. A full tracelog is attached with this Issue.
Reproduce the bug
pip install dateparser ()
pip install --upgrade python-dateutil
This pulls python-dateutil-2.5.3 at the moment.
Workaround
pip uninstall python-dateutil
pip install dateparser
This pulls python-dateutil-2.4.2 at the moment.
Tracelog
python-dateutil.log.zip

Hi @benjaminvdb the issue is already solved by PR #165 and will be fixed in the upcoming release which is due soon.
Hope this helps! Thank you!

@waqasshabbir Alright, that's great! I assumed the patch was already committed to the repo, so I installed dateparser from there and it works just fine with python-dateutil-2.5.3. Thanks a lot!
To install the latest development release of dateparser from GitHub with pip:
pip install --upgrade git+https://github.com/scrapinghub/dateparser.git
dateparser is a wonderful tool. Keep up the good work! 👍


Which build.gradle?

In ReadMe it says "build.gradle". Which one is it: for a whole module (in the root directory) or for a single project (in the directory of the project)?

The build.gradle on readme is written for the project with single build.gradle like simple sample
For the project with multiple build.gradle, please see  libproject sample

I'm talking about a single project too. When I create a simple hello world project in Android studio, I have 2 build.gradle files:

in the root dir
in app/ directory

Which one should I use?

Sorry, README.md doesn't has an example for the project which has multiple build.gradle like yours. So please see this sample. the sample has build.gradle in both the root dir and app dir.


AttributeError: 'Flask' object has no attribute 'before_first_request'

When I run code in deepzoom, it gives me AttributeError: 'Flask' object has no attribute 'before_first_request'

I don't known anything about flask. I'm just a student who want to view the image.
Can I replace this line with something simple?

as per https://github.com/pallets/flask/blob/main/CHANGES.rst#version-230 - version 2.3.0 removed those
so you need to use a older version of flask

For the record, this was fixed in OpenSlide Python in https://github.com/openslide/openslide-python/pull/200.

@bgilbert I won't object super strongly, since using the factory pattern is good in general. But it doesn't look like you actually needed to do that, you should have been able to do whatever was in before_first_request right next to the other setup you were doing, without other restructuring.

Thanks for looking!  The code is designed to be run either manually from the command line or via a WSGI wrapper.  I switched to a factory function because the WSGI wrapper needs to call a setup function that skips the command-line parsing.


Fixes for PureScript 0.9.1

Looks good, but could you please update package.json to "pulp": "^9.0.0" and the latest purescript as well?

Thanks!


Websockets

Is there a easy way to expand this software using websockets so clients can view even frames from the webcam on a canvas, etc?  At the moment I'm using the following bit of javascript to refresh the image, but the fps are uneven and choppy:
http://dpaste.com/0RNZV4J.txt

Hmm, I don't think there's any way to get smooth video out of this library.  It's designed only for taking still frames.  I'd recommend you take a look at something like WebRTC: http://www.webrtc.org/
There's a good tutorial up on html5rocks:
http://www.html5rocks.com/en/tutorials/webrtc/basics/
Good luck, and sorry!

Joe


[PE-D][Tester A] No error message shown for wrong date

Screenshot 2023-11-03 at 4.52.19 PM.png
I tried entering this input but it does not show any error or help message.
It would be good if there is any message which says the date is wrong. Since user might just assume it works

Labels: type.FunctionalityBug severity.Medium
original: AaronJT1/ped#8

Same as #179 , will be settled there


Enforce that P256Keypair is not copyable

Enforce that P256Keypair is not copyable. P256PublicKey IS copyable (and actually copied in practice), so prevent
sliced copies by making it final. Also use = default instead of empty constructor / destructor bodies.

Darwin changes landed separately in #31141


at_events_flutter -- Migrate from package:pedantic to package:lints #220

- What I did
at_events_flutter -- Migrated from package:pedantic to package:lints #220
Issue Number #220

Thanks @AnirbanBall


Add some badges in README.md.

We have already two badges. Travis and AppVeyor. But we still need some additional badges such as Slack link and License link.
So, you can just update the following links in README.md:

https://img.shields.io/badge/slack-online-green.svg
https://img.shields.io/badge/License-Apache 2.0-yellowgreen.svg

I want to take this issue : )

@onyoon7, how's it going?

Hi, I'll take this one together.


fix: NIM1872- add some vdiff tests for cases where table-wrapper has stickyHeadersScrollWrapper enabled

Add vdiff tests for d2l-table-wrapper for the case of its stickyHeadersScrollWrapper property being enabled.
The current state of some these are not ideal. That said I think it would be useful to have them here, and I may be attempting to improve some of these in the near future in which case it will be invaluable to see what affect such attempts are having.

FWIW I've come up with a solution that fixes our specific case in assessments without having to touch core.
I think these new vdiffs might still be useful, but I'm no longer planning to attempt a fix from core in the near future, so happy to back away from this slowly too 🤷


Error org.apache.pdfbox.util.PDFStreamEngine processPerator

Hi! I was using your simplest example codes from your readme file. It throws org.apache.pdfbox.util.PDFStreamEngine ProcessOperator error. Any idea?

I'm getting that issue as well.  Here is a more detailed version of the log above:
$ > node index.js
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: Oct 18, 2016 9:52:54 AM org.apache.pdfbox.util.PDFStreamEngine processOperator
    at consumer (/testapp/node_modules/highland-process/lib/process.js:56:14)
    at Stream.s._send (/testapp/node_modules/highland/lib/index.js:1448:9)
    at Stream.write (/testapp/node_modules/highland/lib/index.js:1548:18)
    at Stream._send (/testapp/node_modules/highland/lib/index.js:912:26)
    at Stream.write (/testapp/node_modules/highland/lib/index.js:1548:18)
    at Socket.ondata (_stream_readable.js:555:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)

I'm running on Mac OSx.  Node v6.7.0.  tabula-js: ^1.0.1.

@cgood92 @dennishu001
Even I am getting the same error. Did you guys get any solution for this?

I am getting this error on same of the pdfs I'm using with this but not all.  Interesting thing here is that all the pdfs are the same table, yet only some of the files cause this error.  I would really be interested in hearing any sort of update on this.
Is anyone maintaining this repo anymore?  I tried checking the version of the .jar file, but its version doesn't seem to be in the manifest file.  I wonder how far back it is from the current 1.1.1???

org.apache.pdfbox.util.PDFStreamEngine processOperator
at consumer (\pdf-csv\node_modules\highland-process\lib\process.js:56:14)
at Stream.s._send (\pdf-csv\node_modules\highland\lib\index.js:1549:9)
at Stream.write (\pdf-csv\node_modules\highland\lib\index.js:1650:18)
at Stream._send (\pdf-csv\node_modules\highland\lib\index.js:974:26)
at Stream.write (\pdf-csv\node_modules\highland\lib\index.js:1650:18)
at Socket.ondata (_stream_readable.js:646:20)
at Socket.emit (events.js:160:13)
at addChunk (_stream_readable.js:269:12)
at readableAddChunk (_stream_readable.js:256:11)
at Socket.Readable.push (_stream_readable.js:213:10)

I recommend to use tabula directly. nodejs binding fails for some reason

The fix is probably the one in pull request #4.

yes. this issue should be closed now. passing {silent: true} in options does not logs warnings


Choropleth maps with null values are drawn as '0'

If you have a table with, for example, percentages for the countries but some certain rows contain null values (perhaps because there's no data for that country, very typical scenario) a choropleth map will draw the null geometries as if they were a 0.
I think it could be interesting to take this into account because obviously in a map it's not the same that a country has a 0 value that the fact that there's no data for that country.
It seems that this is something that comes from the low part of the stack (CartoCSS? mapnik?) and not something that we are doing thoroughly.
Very #pecan related, I'd say :-)
cc @javierarce @javisantana

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


Main Layout Problems

working on the issue for the new Apps styles I found some inconsistencies in the layout.
I had to do some tricks in order for the Apps to display correctly.
I'm creating this issue to make the proper fixes (CSS) in the Layout.
@tschubotz do you mind to include it for v2.16.0?
cc @dasanra

Could you please include some information on what the issues are?

there are some problems with margins and the wrapper for the content.
for example, if you set width 100% on the body content (right side of the sidebar), the content does not fit and the horizontal scrollbar appears.


Error is thrown even when a handler/listener was set

Summary

When making a request to a site with https through a proxy, under some circumstances an error is thrown even when an error handler was set
Simplest Example to Reproduce

var request = require("request");
var concurrency = 1;
var requestOptions = {
	uri: "https://google.com",
	proxy: {
		hostname: "<IP_ADDRESS>",
		port: 8118,
		protocol: "http:"
	}
};

for(var i=0; i<concurrency; i++)
{
	request.get(requestOptions, function(error, response, body)
	{
		if(error){console.log(error);}
		if(body){console.log(body);}
	});
}

Definitely not the best way to reproduce it, I know. Will update when I get the time to write a failing proxy
Expected Behavior

If an error occurs, it should be printed without crashing the app
Current Behavior

The app crashes with the following error:
{ Error: tunneling socket could not be established, statusCode=503
    at ClientRequest.onConnect (D:\projects\test\node_modules\request\node_modules\tunnel-agent\index.js:166:19)
    at Object.onceWrapper (events.js:293:19)
    at emitThree (events.js:116:13)
    at ClientRequest.emit (events.js:197:7)
    at Socket.socketOnData (_http_client.js:443:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at TCP.onread (net.js:560:20) code: 'ECONNRESET' }
events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at exports._errnoException (util.js:1050:11)
    at TCP.onread (net.js:581:26)

Context

If this is a bug, seems like its related to the proxy closing the connection when its overloaded. The particular proxy in the example above is overloaded most of the time, it does not produce the error when its not, thats why the concurrency var is there for heheh . If you can't reproduce the problem with 1 request, I've been successfully reproducing it with 100
Your Environment

software
version

request
2.81.0

node
7.9.0

npm
4.2.0

Operating System
Windows 10 and Ubuntu 16.04

I found if i request with http, it will work correct, if request with https, it will show tunneling socket could not be established

You might be seeing the same problem as this: https://github.com/request/request/issues/2161.
I have a script running with nodemon that, now and then, won't restart when I change the file. It continues to run normally, nodemon just doesn't restart it. If I control-C the process, it throws an unhanded error event and mentions ECONNRESET. No idea how to catch that in my code, unless it's an internal issue/error in nodemon itself.


Port to Pharo 10

Fix Icon Accessors. Methods were generated, but generator (IconFactory) is missing, so fixed using Rewrite Tool
Add project metadata
Fix working directory calculation

thank you for the pull request, I have not touched Pharo for a long time but I would to port this to Pharo 10 pretty soon. So give me a bit of time because other priorities right now but I hopen during this month to merge the pull the request and maybe who knows bring some new features in it as well :)


update for extractor/hentaistigma.py - should fix issue 25019 -- only look at commit 105d32b58cbe06b65439454a4345b5bd635ef0e5

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them

I made this PR so the necessary changes/modifications are known to you devs - I suggest you reject this PR and just take the needed changes from commit 105d32b58cbe06b65439454a4345b5bd635ef0e5 :)
Therefore I skipped the next 2 :

[ ] Covered the code with tests (note that PRs without tests will be REJECTED)
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix

[x] Improvement

[ ] New extractor

[ ] New feature

[x] Update of an existing extractor

Description of your pull request and other information
This is my 1st attempt to contribute to youtube-dl.
This should/could fix/improve the hentai.animestigma.com extractor (see https://github.com/ytdl-org/youtube-dl/issues/25019).
I repeat :
I made this PR so the necessary changes/modifications are known to you devs - I suggest you reject this PR and just take the needed changes from commit 105d32b58cbe06b65439454a4345b5bd635ef0e5 :)
+
Only checkout the changes in commit updated extractor/hentaistigma.py and ignore the other commit (I have not figured out how to do cherry-pick-pull-requests).

This was the first extractor that I modified - so I thought it would be a good candidate to do the first PR .
You probably want to just take the changes from the extractor-file and put them into your implementation instead of merging this PR though.
I tidied up alot already but there are still some remnants from my developing that I left in for my reference.

here the cherry-picked temporary branch :
https://github.com/ifixthat-gmx/ytdl-org---youtube-dl/tree/tmp-hentaistigma

gonna redo PR with branch https://github.com/ifixthat-gmx/ytdl-org---youtube-dl/tree/tmp-hentaistigma


Session Token Support

Hello,
I can see that a substantial amount of work has gone into this SDK implementation & it is very comprehensive.
Are there any plans to support session token auth in the future, instead of just a static token ?
I would be happy to try to contribute in this respect, if this is something that you would actually want to support. Given a previous issue response indicating that the SDK should be considered unstable (April 2024), I would understand if you are currently focusing on stability, over new features.

Since we're working with a backend implementation in Go, we hadn't needed to implement session authentication before. However, I can add support for it. I have two questions:

Do you need this for Directus 10, or only for the newer Directus 11?
Do you explicitly need session tokens, or are username/password logins sufficient? The latter would be implemented using access-refresh tokens, but I'm not sure if you use the session value for a custom cookie or something else.

Since we're working with a backend implementation in Go, we hadn't needed to implement session authentication before. However, I can add support for it. I have two questions:

Do you need this for Directus 10, or only for the newer Directus 11?

Do you explicitly need session tokens, or are username/password logins sufficient? The latter would be implemented using access-refresh tokens, but I'm not sure if you use the session value for a custom cookie or something else.

Thanks so much for the quick reply!
I am using Directus 11, but I only just upgraded & wouldn't really be too worried about 10 or 11 only being supported.
I have used the standard flow previously (prior to switching to Go), which is to perform /auth/login endpoint api request, which takes the username & password, returning an access token, with expiry TTL per the Directus config.
As per;
https://docs.directus.io/reference/authentication.html#login


Hotfix for CreateSectionLabels with duplicates

It seems that if there are domain objects with the same name in a single document, Sphinx only creates a link for the first one, so the 'ids' of the subsequent ones will be empty. We only need to create a label for the first one, as the others aren't linkable anyway.
Fixes #142.

Thanks a lot for the quick fix!


Port 80 without root

We need to support listening on port 80 without requiring the server to permanently run as root. The two options I know of are dropping privileges or socket activation. If socket activation is general purpose enough, I'd prefer that.

For people who want to run public servers, maybe it's better just to tell them to run StrongLink behind nginx.
I don't really like dropping privileges because we shouldn't have them in the first place.


Unable to select the bus for typing sounds

I am not able to change the bus for the character typing sounds.
I have searched on the previous commits and found this one:
https://github.com/dialogic-godot/dialogic/pull/344/commits/e83d7e6a431d74e843c7c3e8458de29df5c20a99
Seems like there use to be a field to set the bus for typing sounds. is there an equivalent now ? I cannot find it in the documentation or in the issues neither.

Right now, the Layers having the Node with the Typing Sounds cannot be changed from the Layer Configuration. If you want, you are free to add such possibility to all built-in Dialogic Styles.
However, you can turn the Layer with the Typing Sounds Node into a Custom Layer and then simply change the Audio Bus on the Node. The Node is named DialogicNode_TypeSounds.

Thanks @CakeVR  for your response. I have made a pull request to add the option into character settings:
#2425

Hi @CakeVR, concerning my PR, since it's my first participation I am not aware of the process. Can I get it merged ?


how to decrypt the .enc file?😂

After uploading you should be provided with a link like below:

Copy/pasting that allows you to share/view the upload. If you're not seeing that screen, let me know your browser information.

After uploading you should be provided with a link like below:

Copy/pasting that allows you to share/view the upload. If you're not seeing that screen, let me know your browser information.

I can see the uploaded file, but get a encrypted file when download it

Interesting. Let me know your browser / operating system and I'll see if I can recreate.

Interesting. Let me know your browser / operating system and I'll see if I can recreate.

qutebrowser and windows11

Interesting. Let me know your browser / operating system and I'll see if I can recreate.

qutebrowser and windows11

Now I work normally, it may be an occasional incident before 😅


Duracloud image file must default to .jpg when .jp2 does not exist

Duracloud image file must default to .jpg when .jp2 does not exist.

Our Archivematica has not been configured correctly.


lambda delete action - handle lambda @ edge functions

 An error occurred (InvalidParameterValueException) when calling the DeleteFunction operation: Lambda was unable to delete arn:aws:lambda:us-east-1:xxx:function:xxx-Test-LambdaEdge:1 because it is a replicated function.: InvalidParameterValueException

+1

Looks like AWS is handling the deletion of replicated functions behind the scenes:
https://forums.aws.amazon.com/ann.jspa?annID=5529
The way you trigger this is by removing the CloudFront associations which then kicks off the deletion of the replicated functions automatically, but until that completes you can't delete the parent function.
AWS says the replicated functions are "typically deleted within a few hours".  Does c7n have a framework we could plug into for handling deferred actions that periodically check and wait on a precondition before processing?

@zacharya the best way to do it would be to use the mark-for-op pattern I suppose, pseudocode policy:
policies:
  - name: mark-lambda-edge-for-deletion
    resource: lambda
    actions:
      - delete-associated-cloudfront-distributions # not a real action, just spitballling
      - type: mark-for-op
        tag: c7n_lambda_edge_delete
        op: delete
        days: 1

  - name: delete-lambda-edge
    resource: lambda
    filters:
      - type: marked-for-op
        tag: c7n_lambda_edge_delete
      - no-cloudfront-distributions # not a real filter either
    actions:
      - delete

Makes sense.
The only possible issue with this approach is that you'd have to crawl all CloudFront distros until you find any associated with the Lambda function due to how the CloudFront API is designed (https://boto3.readthedocs.io/en/latest/reference/services/cloudfront.html#CloudFront.Client.list_distributions).  There's no way to filter on Lambda associations nor is there an endpoint in the Lambda API that identifies which CloudFront distributions are associated with the function.
I'm happy to take this as a first contribution and submit a PR if no one objects.

Yeah, looks like it would we would need the following:

filter: has-cloudfront-distribution

list-cloudfront-distributions
get-cloudfront-distributions

look at the lambdafunctionassociations object

action: delete-cloudfront-distribution

this would have to do the same thing as the filter unfortunately from what I can see


Update link to current SP 800-52

Existing link was to SP 800-52 Revision 1, which has been withdrawn and superseded by SP 800-52 Revision 2.

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

Thanks for your contribution, I've merged your changes and they should be live soon.


Postgresql array type mapping support?

An exception was raised  while trying  to select some rows from a PostgreSQL table:
java.sql.SQLException: Can not map SQL type 2003 (ARRAY) to ClickHouse
even if I just a non-array column.
I'm assuming the ARRAY type is not support as of today, as I compiled the jar from the git repo master branch.
Clickhouse ver: <IP_ADDRESS>
OS: Debian 10
openjdk version "1.8.0_265"
OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_265-b01)
OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.265-b01, mixed mode)
JDBC drive: postgresql-42.2.18.jar

Array is an advanced type that is supported at this point. I'm working on 2.0 and let me see if this can be added. In worst case,  it will be mapped as String in clickhouse.

Array or any other unsupported data types are treated as String in 2.0.0.
I created #88 to track this issue and will provide better solution in 2.1.

Array or any other unsupported data types are treated as String in 2.0.0.
I created #88 to track this issue and will provide better solution in 2.1.