[Gluten-3312][CH] Introduce a config to control empty as default for CSV

What changes were proposed in this pull request?
add the configuration spark.gluten.sql.text.input.empty.as.default representing the meaning of treat empty fields in CSV input as default values

PR title should be a brief summary and we should hide too detailed info. I just changed it. Please revise it if you think of a better summary. Thanks!

LGTM

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_3313_time.csv
log/native_master_09_27_2023_523395c22_time.csv
difference
percentage

q1
43.51
43.84
0.321
100.74%

q2
24.83
24.25
-0.579
97.67%

q3
38.70
37.31
-1.391
96.41%

q4
40.82
41.10
0.274
100.67%

q5
70.36
70.67
0.304
100.43%

q6
6.56
7.07
0.508
107.74%

q7
84.30
83.62
-0.685
99.19%

q8
81.78
82.10
0.319
100.39%

q9
117.28
116.36
-0.917
99.22%

q10
47.44
46.38
-1.064
97.76%

q11
19.63
18.95
-0.679
96.54%

q12
26.83
25.24
-1.593
94.06%

q13
51.66
50.58
-1.084
97.90%

q14
14.96
16.28
1.319
108.82%

q15
29.40
27.18
-2.219
92.45%

q16
15.86
16.28
0.412
102.60%

q17
120.57
120.13
-0.439
99.64%

q18
163.31
161.84
-1.476
99.10%

q19
13.02
12.16
-0.860
93.40%

q20
35.67
28.31
-7.360
79.37%

q21
249.64
239.00
-10.644
95.74%

q22
15.40
15.72
0.318
102.07%

total
1311.57
1284.35
-27.214
97.93%


PSA Move extern-style parser value set examples to examples/historica…

…l directory

Pardon my unnecessary rush if you would prefer that these file moves not be made, but I would like to be able to point people at the 'examples' directory for sample programs, and would rather not confuse them with these probably-soon-obsolete parser value set examples that used the older approach of P4_16 externs that people did not like the syntax/flow of.


DayPickerRangeController will not display in bootstrap dropdown menu

If I put the DPRC in a bootstrap dropdown menu, it takes up space but doesn't display:

If I move it outside of the dropdown menu, it displays correctly:

foo

<DayPickerRangeController
            startDate={startDate}
            endDate={endDate}
            minimumNights={0}
            numberOfMonths={2}
            onDatesChange={this.handleChange}
            focusedInput={focusedInput || 'startDate'}
            onFocusChange={focusedInput => this.setState({focusedInput})}
            isOutsideRange={this.isOutsideRange}
            hideKeyboardShortcutsPanel={true}
            onClose={this.handleClose}
            isDayHighlighted={this.isToday}
          />

@toddpeak I am experiencing the same problem. Did you manage to resolve the issue?

Had to force visibility: visible with
.DayPicker__hidden {

    visibility: visible;

}

+1 on this, i created a small sandbox repo to look into it, only the DayPickerRangeController is affected:
https://codesandbox.io/s/github/nfabredev/ReactDateDemo_DayPickerRangeController
Would appreciate any input to correct this

+1, having the same issue.

My ugly workaround approach that solves the problem in the meantime:
componentDidMount() {
    /* Workaround for a weird bug where DayPickerRangeController is hidden when in a
     * Bootstrap dropdown
     */
    $('.DayPicker').removeClass('DayPicker__hidden')
  }

  onOpen() {
    /* Ugly hack. Since we forcefully remove 'DayPicker__hidden' class from DayPicker
     * component the component does not trigger vertical resize. For this reason we forcefully
     * resize the component on first show to mitigate the problem.
     */
    if (!this.heighCorrected) {
      $('.DayPicker_transitionContainer').height(320)
      this.heighCorrected = true
    }
  }

This is because the Calendar isn't been rendered in the DOM first place. What you can do to force the render is to render in a JIT way. I'm not sure how the bootstrap dropdown is rendered but it would help if you have an isOpen state.
Pseudo code that hopefully helps:
state={
  isBootstrapDropDownOpen: false;
}

render() {
<>
  <Button onClick={this.setState({ isBootstrapDropDownOpen: true })}>
  {isBootstrapDropDownOpen && <DayPickerRangeController/>
</>
}

This is a pretty big problem for us.
We have a pop-up which starts closed, and opens right under its button. We originally fixed the height issue with a solution like @Marinolinderhof suggests.
Now we're trying to fix an issue where the pop-up can be partially out of the screen when the component is low on the UI, but giving it an appropriate translation when it's opened, but since the element doesn't calculate its height immediately on first render, the height of the box is miscalculated and nothing happens.
I've noticed that the CalendarMonth component (which ultimately calculates its height and lets the whole picker calculate its own height) has the following line, presumably to push calculations to the back of the JS event queue.
https://github.com/airbnb/react-dates/blob/8a605d00fe13ca3eb0c82903c6654f6d00e14046/src/components/CalendarMonth.jsx#L110
By using my own setTimeout(() => {}, 0) within a useEffect/useLayoutEffect I was able to get the height after CalendarMonth had caused the DOM to update. It's unclear how robust this is, but at least it's something.
Would be great if the issue could be looked into further, is there a reason react-dates can't use flex/grid itself to give itself a natural height without JS intervention? Or could we get an imperative function to call whenever we want the component to re-calculate its height properly, to avoid the original hack?

flex isn’t supported in enough older browsers to be an option.

+1 having this issue with DayPickerSingleDateController

Ran in to this and @Marinolinderhof's comment was spot on. We were rendering the date picker before it was visible which causes react-dates to hide itself for some reason. As soon as we switched to only rendering the date picker when we knew it would be visible it was fixed

This is because the Calendar isn't been rendered in the DOM first place. What you can do to force the render is to render in a JIT way. I'm not sure how the bootstrap dropdown is rendered but it would help if you have an isOpen state.
Pseudo code that hopefully helps:
state={
  isBootstrapDropDownOpen: false;
}

render() {
<>
  <Button onClick={this.setState({ isBootstrapDropDownOpen: true })}>
  {isBootstrapDropDownOpen && <DayPickerRangeController/>
</>
}

Life saver!!!!!

I ran into this issue a few years later...
You can also adjust the key rather not render it at all. I still wanted to render it as I have a wrapper around it which loads some data.
export function DatePicker({ isOpen }: DatePickerProps) {
  return (
    <>
      <DateRangePicker key={`date-picker-${isOpen ? 'open' : 'closed'}`} />
    </>
  );
}

Seems like this might still be a problem? Ran into this outside of a bootstrap dropdown as well. Looks like if a parent element has display: none the .DayPicker__hidden class gets appended even when the display:none style falls off the parent.
We worked around by setting parent height to 0 instead.


Micronaut Serde Jackson with @JsonUnwrapped and @JsonIgnoreProperties does not work

Expected Behavior
JsonUnwrapped on a default visibility variable serializes variables inside the object marked as unwrapped.
Actual Behaviour
When using JsonUnwrapped with a field with default access level, like in ProblemErrorResponseProcessor. ThrowableProblemWithoutStacktrace, when using Micronaut Serde, values that would normally be serialized are ignored.
I believe this is because BeanIntrospection does not return default visibility fields from BeanIntrospection#getBeanProperties(), so the code here does not return these fields.
However, Jackson doesn't have a problem with this, probably because it uses reflection and accesses private members.
I'm not sure if a change here is possible, or if Micronaut Problem JSON should change this ThrowableProblemWithoutStacktrace field to have a getter for this property.
Steps To Reproduce

Use Micronaut Serde as described here
Install Problem JSON and define a custom problem with a field as described here
Create a controller that throws this custom problem
Note that the extra field is not returned in the JSON response.

Environment Information
No response
Example Application
https://github.com/edeesis/problem-serde-example
Version
3.0+ (tested on 3.5.1)

I just re-read the docs on BeanIntrospection, and realize this is a bug in Problem JSON instead - they should use Field Access Level on that type.
Will open a bug on that project

Re-opening, seems like with Field AccessKind, @JsonIgnoreProperties is being ignored.

Here's a branch with micronaut-problem-json with the change to Field AccessKind. The two new tests added in this commit fail.

Closing this issue and re-opening a new one with the JsonIgnoreProperties issue.


sneak-to-bottle-all not consuming correct XP points

As per title, when sneaking to bottle all it only takes the amount set on "take-xp-amount: x".
To replicate:
I have my "take-xp-amount" set to 22. (if it matters)
I have 64 bottles and I sneak to bottle all, I'll get 64 XP bottles but it only consumes 22 XP points.

Fixed in Hotfix v1.4.1 (should be released within an hour)

Just published v1.4.1-beta that fixes this, as well as adds your
auto /ch toggle suggestion :D

Thanks!


Typo in Swagger configuration parameter: tagSorter -> tagsSorter

There is a typo in the name of a swagger configuration parameter that is causing it to have no effect.  In src\NSwag.AspNetCore\SwaggerUi3\index.html and src\NSwag.AspNet.Owin\SwaggerUi3\index.html, there is this:
    tagSorter: "{TagSorter}",
it should be:
    tagsSorter: "{TagSorter}",
This config setting is documented as "tagsSorter" here:  https://github.com/swagger-api/swagger-ui/blob/master/docs/usage/configuration.md
I don't know if you'd also like to fix the other instances where TagSorter should be TagsSorter, for example in the property of SwaggerUi3Settings.
On a related note, NSwag seems to also still support the "apisSorter" configuration option, which is no longer in use, at least according to this swagger-ui commit:
https://git.r3ktm8.de/root/swagger-ui/commit/571d65a5829e5b4d352fe126f251e045a1cef16f

Can you create a pr where you remove the apisSorter, and rename the property + fix the bug? I think the break is fine as it gives instant, easy to fix compile errors and there are breaking changes anyway in the next version


[firebase_storage] Object does not exist at location (but it does!)

I'm getting an error when attempting to download a file from firebase storage.  The file locations seem to be identical.  I can access firebase database data in the same firebase project from the same flutter project too and I've got my permissions set to allow reads from anyone.  Any ideas please?
The error is
E/StorageException(27807): StorageException has occurred.
E/StorageException(27807): Object does not exist at location.
E/StorageException(27807):  Code: -13010 HttpResult: 404

Comparing the file I'm requesting to the one that is in storage (storage location field), they are identical
gs://XXXX.appspot.com/triggeraudio/trig_aud_100.zip
gs://XXXX.appspot.com/triggeraudio/trig_aud_100.zip

My permissions
service firebase.storage {
  match /b/{bucket}/o {
    match /{allPaths=**} {
      allow read;
    }
  }
}

The code that I run to try to download the file
    var storageReference = FirebaseStorage().ref().child(gsPath);
    var file = File(savePath);
    await storageReference.writeToFile(file);

Flutter doctor
Flutter (Channel stable, v1.17.0, on Mac OS X 10.15.4 19E287, locale en-GB)

Hi @atreeon
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

due to security issues I'd rather not post the flutter doctor response.  I have included a code sample above.

I had the same error, and after playing around with it, I realized that it happens only with "big" files. For example fetching image with around 200KB works just fine, but when I try to do the same with mp3 that is almost 7MBs (in my case I am just fetching metadata from reference) it shows this error, even tho file exists. I can provide more info about this, if needed.

I had the same error, and after playing around with it, I realized that it happens only with "big" files. For example fetching image with around 200KB works just fine, but when I try to do the same with mp3 that is almost 7MBs (in my case I am just fetching metadata from reference) it shows this error, even tho file exists. I can provide more info about this, if needed.

HI @atreeon
Please use whole path in refrence at time of downloading url,
i am sure this will solve this issue,
i had gone through the same problem and i found i wa just giving file name without directory
use this way
storage.ref('Directory/$filename').getDownloadURL();

HI @atreeon
Please use whole path in refrence at time of downloading url,
i am sure this will solve this issue,
i had gone through the same problem and i found i was just giving file name without directory
use this way
storage.ref('Directory/$filename').getDownloadURL();

Hey @atreeon, are you able to confirm the above solved your problem?

@russellwheatley thanks, its been a while since I looked at this but I think it is solved and was a problem with the path
I think I used a relative path without the gs:// part

Thanks for letting us know, @atreeon!


Control plane services to listen on localhost by default

In what area(s)?

/area runtime

/area operator
/area placement
/area injector
/area sentry
/area scheduler

/area docs

/area test-and-release

What version of Dapr?
<= 1.14.x
Expected Behavior
Running any control plane service should only listen to localhost loopback by default.
Requirements

dapr init -k continues to work with runtime version +/- 1
dapr init continues to work with runtime version +/- 1
No code change required in Dapr CLI (implicitly included in requirements 1 and 2)
Users can upgrade or downgrade (1 version step) Dapr control plane as usual without any extra steps
Users can replace their container image version tag without having to add new params

By definition, this change will break users that are running Dapr control plane without a Docker image and they will need to add an extra configuration (env, cmd arg, or anything else).
Actual Behavior
Running any control plane service listens on all network interfaces by default.
Steps to Reproduce the Problem
Run any control plane service from command line directly (without using a container image) and see that is listens to all network interfaces.
Release Note

RELEASE NOTE: FIX control plane services to listen to localhost by default

I propose the change is to simply add a new env var (like DAPR_CONTROL_PLANE_LISTEN_ADDR) that will override the default listening address on all Dapr control plane services, easily adding that in the shared Dockerfile. It would not break backwards compatibility of the generated images and require users of standalone mode (without containers) to simply add an env variable to their configuration instead of changing cmd of each service.


feat(cli): store remote digest in local state for concurrency

Retrieves and stores the digest of the remote state
Sends the digest during updates

in the video below you can see an example of the retry mechanism in the client. For the demo I've simulated some latency in adding the container image while changing the state by adding an artifact in the bottom pane.
As you can see the att add in the top panel fails the first time but retries, retrieving the new state and updating it again.
Screencast from 2024-07-25 15-53-52.webm
Note: I've not enforced (in the server) sending the digest by all clients because that would cause old clients to fail. So basically new clients will be able to handle this retry mechanism vs the old ones will just fail when conflict
closes #973

Awesome! Thanks for taking care.


Reset the tray when there is no gulpfile

In Follow Finder setting, gulp-app can not track if user move to another directory.

I send a pull request for it.

Closing as this app is now deprecated.

Closing as this app is now deprecated.


Create Erik_tutorial.py

Includes timestamp. Newest version.

Eric, this merge has a conflict.  Please try to fix these conflicts and submit again.
thanks,
LRH

Conflicts should be fixed now.


Signed-off-by: Jan Fuhrer<EMAIL_ADDRESS>
What this PR does:

improve values.schema.json & ci test-values
disable networkpolicy by default

Notes for Reviewer:
Checklist:

[x] Pull Request title in format [chart]: Changed Something
[x] Updated documentation in the  README.md.gotmpl file and executed helm-docs
[x] Chart Version bumped
[x] All commits are signed-off

Do we need to publish the values.schema.json with the helm-chart release or is it sufficient to reference in a derived chart like this:
{
    "$schema": "http://json-schema.org/draft-07/schema",
    "type": "object",
    "$ref": "https://raw.githubusercontent.com/bedag/helm-charts/common-7.0.1/charts/common/values.schema.json"
}

Do we need to publish the values.schema.json with the helm-chart release or is it sufficient to reference in a derived chart like this:
{
    "$schema": "http://json-schema.org/draft-07/schema",
    "type": "object",
    "$ref": "https://raw.githubusercontent.com/bedag/helm-charts/common-7.0.1/charts/common/values.schema.json"
}

No need to publish it, since we can get the values.schema.json by version with the help of the tag references.

@janfuhrer
Could you also fix the name of the following ids:

https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L217
https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L913

@janfuhrer Could you also fix the name of the following ids:

https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L217
https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L913

done, I am still not sure if we need this $id field at all or if we can leave it out completely

@janfuhrer Could you also fix the name of the following ids:

https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L217
https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L913

done, I'm still not sure if we need this $id fields at all or if we can leave it out completely

I'm not sure either, just test it locally.
Build a helm chart with common as dependency.
Set $ref in values.schema.json in new helm chart to _https://raw.githubusercontent.com/janfuhrer/helm-charts/master/charts/common/values.schema.json_

@janfuhrer Could you also fix the name of the following ids:

https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L217
https://github.com/janfuhrer/helm-charts/blob/master/charts/common/values.schema.json#L913

done, I'm still not sure if we need this $id fields at all or if we can leave it out completely

I'm not sure either, just test it locally. Build a helm chart with common as dependency. Set $ref in values.schema.json in new helm chart to _https://raw.githubusercontent.com/janfuhrer/helm-charts/master/charts/common/values.schema.json_

I've removed all $id fields and tested as follows:

uncomment all includes in includes.yaml
helm template . -f ci/values.test.yaml works as expected
add something wrong:

components:
  foo: bar

--> fails as assumed:
Error: values don't meet the specifications of the schema(s) in the following chart(s):
common:
- components.foo: Invalid type. Expected: object, given: string


Merged report doesn't show coverage for classes which were tested

I am working on the Intellij IDEA plugin. I have the following setup for the project:

Gradle: 6.9.2
Kotlin: 1.5.32
Java: 11
Kotlinx-Kover: 0.5.0

If I run with debug tests directly from the IDEA, I can reach a breakpoint in the tested classes. However, if I run koverMergedHtmlReport either with Intellij agent or with Jacoco, reports will show 0% coverage by any metrics. But as a result, these tests are marked as PASSED. It means that tested classes should be touched in any case.

Do you have any ideas why it is possible?

Hi,
which git branch are you building?
I'm trying to reproduce issue locally.

Hi @shanshin, thank you for the quick response.
I pushed the latest changes to the branch: https://github.com/aemtools/aemtools/tree/182_feature.
Let me know if you need more info.

Which command do you run Gradle tasks with?
./gradlew clean build crashes with an error locally

@shanshin , try to run  ./gradlew clean koverMergedHtmlReport.

Locally, when I run the command ./gradlew clean :aem-intellij-core:test --tests "com.aemtools.completion.clientlib.ClientlibCssTxtCompletionTest" koverMergedHtmlReport -x :aem-intellij-index:test  -x :aem-intellij-lang:test, I get full coverage of the class CdCompletionContributor.
Also, try to build without using the build cache (by adding the  --no-build-cache option).
Write if building without caches doesn't help.

Thank you for the suggestion, @shanshin. I tried to run ./gradlew clean clean koverMergedHtmlReport --no-build-cache, but it didn't help. The coverage for mostly all packages under com.aemtools.completion package is zero.
However, if I run your command, I can see 100% coverage for CdCompletionContributor.
Therefore, I suggested that there is an issue with some dependencies between modules. I have testCompileOnly(project(":aem-intellij-core")) dependency in 2 modules and I thought that it could impact especially during test step. I moved some classes to avoid this dependency declaration, run build and here we go again - 0.00% for this class and mostly all sub-packages of  com.aemtools.completion.
It seems that the agent in runtime does not use the classes that I have in the classpath, but I might be wrong. It is strange because there are similar tests in the same module and they have some coverage.
By the way, let me provide some of my tries with this project and code coverage. Firstly, I tried to use Jacoco, but it shows less than 50% coverage for the whole project. Then I found Kover and introduced it to the project and coverage was increased to 50-51%. Long days of trying to find the cause, I decided to just play around with the versions of Kotlin and Gradle. I downgraded them: Kotlin 1.6.10 -> 1.5.32, Gradle 7.3 -> 6.9.2. As a result, my project coverage was increased to 66%. However, I know that it should be around 80% (+-5%) on old versions on Kotlin and Gradle and with Java 1.8.

Unfortunately, I was unable to execute the ff command ./gradlew clean koverMergedHtmlReport --no-build-cache due to errors. I excluded problematic tests, but in this case the coverage turned out to be complete (
Errors:
HtlPatternsTest > testHtlAttributeMain FAILED
    junit.framework.AssertionFailedError at HtlPatternsTest.kt:368
...
HtlPatternsTest > testDataSlyUseNoElMain FAILED
    junit.framework.AssertionFailedError at HtlPatternsTest.kt:368

HtlPatternsTest > testMainVariableInsideOfDataSlyRepeat STANDARD_ERROR

Hi @shanshin, I am with good news. I disabled some problematic tests and run ./gradlew clean koverMergedHtmlReport. As a result, I got 84.5% line coverage.

Thank you for your help and time. To be honest, I am sorry that I wasted your time, but a collective mind was required to solve this issue.
Please, close this issue. Have a good day!


Add --fail-if-warnings options to pandoc

WiP for two reasons:

There is still warnings, so pandoc fails (kind of a big one!)
There is a pandoc command rework in the upcoming training PR merge, so this one will need to be integrated first

Still WiP while it fails.

The build fails because of the missing lab include


Time display not colon centered

Proposal from user:

In horizontal layout you center the time display at the colon which is a good choice when using a non-proportional font. When using the default font, the time display often is not centered especially if it is in the morning and the leading "0" is switched off or if there are "1" digits showing.
Could you add an option to center the whole time display, not centering the colon? Would be a perfect "finetuning".

Done in 1.1.0 release


TypeError: Cannot read property 'name' of undefined

Guys, I'm getting this error.
Thoughts?
/Users/luco/htdocs/test/creator/node_modules/@bull-board/api/dist/src/queueAdapters/bull.js:14
        return `${this.prefix}${this.queue.name}`;
                                           ^

TypeError: Cannot read property 'name' of undefined
    at BullAdapter.getName (/Users/luco/htdocs/test/creator/node_modules/@bull-board/api/dist/src/queueAdapters/bull.js:14:44)

What was the issue?


CAMEL-13545: fix netty4-http memory issues

DefaultNettyHttpBinding::toNettyRequest could allocate a new Netty ByteBuf (e.g. via NettyConverter::toByteBuffer) which in turn might or might not be passed to the FullHttpRequest depending on the resulting buffer size: if it's 0 it will not be set as content of the request. In that case this causes a memory leak.
The buffer having the size of 0 is quite common for GET or OPTIONS HTTP method requests, so releasing the buffer if the incoming request is received when acting as a proxy will cause the any downstream Netty requests (say in a scenario from("netty-http:proxy:...").toD("netty-http:...")) to block.
So additional optimization was added to store the proxy HTTP request in the Exchange property and to check if the current request in the NettyHttpMessage has the same reference; and in that case the proxy HTTP request will be reused, only changes to the HTTP method, protocol or request URL will be applied.
Tests pass, would appreciate if my assumptions would be double checked.

Thanks


Coretime interface

A pretend RFC proposal in order to test the rfc-bot

/rfc-bot

/rfc-bot

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose

/rfc-propose


Added wpad.www.tendawifi.com to the hosts file

This pull request adds wpad.www.tendawifi.com to the hosts file to block access to the website, as it was constantly pinging our system with a large number of requests.
Please review and merge this pull request if it meets your approval.
Thank you!

Thank you for this perfect pull request Daniel @danielawde9.
Merging.


fix: visual inconsistency in app_settings

fix: bottom padding for rate us tile
fix: misalignment of share icon refactor: added user_preferences list tile
which is used for both rate us and share app tile
fix: The rounded corners of the country and the language pickers are different

Screenshot

Fixes bug(s)

Fixes:

Part of

#525

Codecov Report

Merging #3818 (caae24a) into develop (a7b1335) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

:exclamation: Current head caae24a differs from pull request most recent head e7fc23d. Consider uploading reports for the commit e7fc23d to get more accurate results

@@             Coverage Diff             @@
##           develop    #3818      +/-   ##
===========================================
- Coverage    10.67%   10.67%   -0.01%
===========================================
  Files          272      272
  Lines        13547    13552       +5
===========================================
  Hits          1446     1446
- Misses       12101    12106       +5

Impacted Files
Coverage Δ

...b/pages/preferences/user_preferences_settings.dart
6.64% <0.00%> (+0.12%)
:arrow_up:

...ib/pages/preferences/user_preferences_widgets.dart
12.90% <0.00%> (-1.74%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@g123k added the changes! Thanks

@g123k I have made the chnges ! sorry for the delay !


Cloudformation stack get error because of nodes 6.x

Hello,
Can anyone update the stack?
I tried to run the stack, it get error because lambda is nodejs 6.x, can anyone update the stack to meet the new version 10.x?
Thanks

worked with updating the template, also make sure to run in n. virginia region for
access to the pubz bucket for the lamba function.
"Runtime": "nodejs8.10",

worked with updating the template, also make sure to run in n. virginia region for
access to the pubz bucket for the lamba function.
"Runtime": "nodejs8.10",

OK & Thx.

I tried nodejs10.x and this did not work got "errorType": "Runtime.ImportModuleError",
"errorMessage": "Error: Cannot find module 'app'",
"stack": [
"Runtime.ImportModuleError: Error: Cannot find module 'app'",
"    at _loadUserApp (/var/runtime/UserFunction.js:100:13)",
"    at Object.module.exports.load (/var/runtime/UserFunction.js:140:17)",
"    at Object. (/var/runtime/index.js:36:30)",
"    at Module._compile (internal/modules/cjs/loader.js:776:30)",
"    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)",
"    at Module.load (internal/modules/cjs/loader.js:653:32)",
"    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)",
"    at Function.Module._load (internal/modules/cjs/loader.js:585:3)",
"    at Function.Module.runMain (internal/modules/cjs/loader.js:829:12)",
"    at startup (internal/bootstrap/node.js:283:19)"
]
}


:sparkles: change name to rakun

[x] logo
[x]  text + link
[ ] work-with-us
[ ] CNAME
[x] markdown

I've not change the CNAME to.

I just change DNS to point at github IPs.
I changed the CNAME but we have to wait them to issue a SSL certificat (24H)


Feat: Icons can be added in Input and button to see the password

Feat: Icons can be added in Input and button

Added the possibility of adding an icon to the Input component, these can be placed on the right or left, by default on the right, on the left by means of the left-icon class.

Case: icon (default on the right)
<Input  label="this is a label" icon="user" />

Result

Case: icon on the left
<Input  label="this is a label" icon="user"  className="left-icon"/>

Result:

Added a button in the inputs of type password to see/hide the password, it will be by default in the inputs of type password.

Case: password input
<Input  label="this is a label" type="password" />

Result

Case: icon on the left with password input
<Input  label="this is a label" icon="user"  className="left-icon" type="password" icon="user"/>

Case: Enter password with icon
Result
<Input  label="this is a label" icon="user"  type="password" icon="user"/>

@jircdev
Settings have been uploaded
Remove commented code
Remove console.log
Replace px with rem


Do not call .value() method when comparing HttpStatus as they are enums

Closes no issues
Changes:

Don't call .value() method when comparing HttpStatus as they are enums

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.David Rodriguez seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.


Example App: Shell Script Invocation Error Group

Hi I got this when run XCoordinator-Example:

any idea please?

This seems to be related to the SwiftLint build phase.
Since you happen to have a whitespace in the path of your project, the script does not seem to find the SwiftLint-executable.
To still run the project, either remove the SwiftLint build phase or move the project to a path not containing a whitespace.


expand readme to explain how all the pieces in this project work

does what it says on the tin

also perhaps put in some code comments


No issue: collaboration invite

Hello matter-rs,
sorry for creating a non-issue. Please simply close it if that is not interesting for you.
I‘m one of the maintainers of matter.js (also project under project-chip orga) and we implement matter in JavaScript/typescript.
To support the open source community in developing with and for matter I also created a discord called „matter-integrators“ where I would like to invite you. There are already other open source projects like the tasmota matter implementations in and beside building a developer community it also started to be a good place to exchange opinions on matter specs and how to read/interpret it ;-).
Thank you and maybe see you there ;-)
Ingo

(As an extra viewpoint - I'm looking at Matter in Rust as well, and am over on the Discord - I'd love to have a place to chat with others doing similar things!)

@Apollon77 that's great to hear, would love to participate. Is this a public room, I couldn't find one, maybe share a link for the same?
@kolektiv great, you can join the matter-rs room here #matter-rs:matrix.org (https://matrix.to/#/#matter-rs:matrix.org) , most of the discussion is currently person-to-person, but I guess moving to this room will help.

Hehe, I created a link but forgot to add to the post ....aahhhhh ;-)
Here we go (and yes open server)
https://discord.gg/qW2feSxmN8

Ps: if helpful I can also create a closed private room for your project in that discord so you have a channel to collaborate more internally on the rust project. Just write me in discord if you want it.

I would also close here, thanks for joining.


FC Percentiles Changes - Fix counts, make sum > 120 NODATA and clip to 0-100

Counts valid observations properly
Sets pixels that sum to > 120 to NODATA
Clips input data to between 0-100

Hey @fangfy and @cbur24 this is ready for review.
Pixel counts look like this:

And over exposed areas went from this:

to this:

@alexgleith  please undo the merge. thanks.

Hey @emmaai I don't want to undo the merge, but I'm happy to make further changes to make settings optional or to change thresholds.

Hey @emmaai I don't want to undo the merge, but I'm happy to make further changes to make settings optional or to change thresholds.

Yes, if you can, please make those thresholds optional. Thanks.


[Bug]: Most recent semester COURSE data (academic year 2024) not displaying

What did you expect to happen?
COURSE data should be up to date with the current academic year (2024)
What happened?
COURSE data (from the course API route) is only returning data up to academic year 2023
Dependencies

[ ] API team has to resolve issues scraping current academic year/F24 data from coursebook
[ ] Verify newest data is being displayed in TRENDS for the Course Component

Version
Beta 0.1.0
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Find a course/prof that was taught for the first time in 2024/S24

Resolved via API rerunning the Coursebook scraper


all.csv is not available from the ShapeNetV1PointCloud.zip

Hey @csjxchen , thanks for pointing this out! I updated the README with information on where to find the file. Apparently, the download link on the original shapenet website doesn't work as of now. I uploaded a version of the all.csv at this link, you can use this one.

Thanks for your reply. It's a great help for  me.


Remove SQL version #

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Garthmj sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@Garthmj  Looks good!


Adding token: CIF from chain Cifer - Update RPC and Rest endpoint

Description

Based on our investigation of the previous chain registration issues about deposit and withdrawal, it appears there might be problems with RPC, REST, and WebSocket functionalities.

We've addressed a potential cause by adding https://app.osmosis.zone to the CORS allowed list configuration in .htaccess, as detailed in the attached screenshot:

Also disable CORS policies following this doc:
https://tutorials.cosmos.network/hands-on-exercise/4-run-in-prod/1-run-prod-docker.html#cors

Update RPC endpoint to the wss enable one.

Update Rest endpoint, by bypassing Cloudflare for the REST endpoint to see if it resolves the issue.

All of steps above should fix transferring problem.
Checklist

Adding Chains

If adding a new chain, please ensure the following:

[x] Chain is registered to the Cosmos Chain Registry.

Chain's registration must have staking defined, with at least one staking_token denom specified.
Chain's registration must have fees defined; at least one fee token has low, average, and high gas prices defined.

[x] Add chain to bottom of zone_chains.json

RPC and REST must not have any CORS blocking of the Osmosis domain.
RCP node must have WSS enabled.

Adding Assets

If adding a new asset, please ensure the following:

[x] Asset is registered to the Cosmos Chain Registry.

The description and/or extended_description of the asset in the Chain Registry is informative.

[x] Add asset to bottom of zone_assets.json.

The IBC channel referenced in path must be registered to the Chain Registry.
osmosis_unlisted defaults to true (until the respesentation and transferring of the new asset has been validated)
Note that it is recommended to include an X (fka, Twitter) profile URL with each asset.

On-chain liquidity
For each new asset, please provide the plan for on-chain liquidity of the asset (See: Pool Setup Guilde.): (choose one)

[x] Ready -- A liquidity pool(s) has been created and has liquidity. The pool ID is: 1678,1680
[ ] Soon -- A pool will be created soon. Do not merge this PR until liquidity is ready.

[ ] (optional) A preview of the Osmosis Zone app with the new asset added is requested for creating the pool. (Note: This method is not recommended because the Supercharged Liquidity pool type cannot be created via the Osmosis Zone app)

[ ] StreamSwap -- The token is, or will be, going through a StreamSwap stream; thus, the token should be listed without requiring on-chain liquidity. A Pool ID will be provided in this PR following the stream's completion once the team has had a chance to create a pool using the earned funds. The StreamSwap Bootstrapping phase begins (when?): ______

We test and still face the same issue after update. (CORS blocking and failed to connect with websocket)
We apologize for the ongoing deposit and withdrawal issues. 🙏
Our team is actively working on a fix to address the CORS configuration and restore functionality as soon as possible.
In the meantime, if you have any suggestion or similar cases, please don't hesitate to let us know. 🙏

An Update, I just noticed this error, so it looks like we require nodes serving over https instead of http.

Do we have nodes with https?

Hi Jeremy,
Yes, we have RPC node with https, we will update and make a pull request.
However, we've identified a potential cause for deposit and withdrawal issues, where tokens are getting stuck in the relayer.
Our Investigation:
We identified two active channels between Cifer-2 and Osmosis-1 on Mintscan interface.

The correct path (channel-39205 <> channel-1) is registered on the Cosmos chain registry. (https://github.com/cosmos/chain-registry/blob/master/_IBC/cifer-osmosis.json)

The incorrect path (channel-39057 <> channel-0) appears to be a result of encountering errors during multiple attempts to create the relayer. We had to establish the connection successfully after several trials.
Channel-0 on Cifer-2 is designated for Cosmoshub, not Osmosis.

Transactions show that CIF withdrawals from Osmosis use the incorrect channel (channel-39057), causing tokens to become stuck.
The transaction link: https://ibc.iobscan.io/transfers?pageNum=1&pageSize=10&denom=ibc/EFC1776BEFB7842F2DC7BABD9A3050E188145C99007ECC5F3526FED45A68D5F5&startTime=&endTime=2024-04-15

Proposed Solutions:
Creating new clients won't address the root cause of the issue (incorrect channel on Cifer-2). We'd appreciate suggestions for moving forward:

Can we close the erroneous channel-39057 <> channel-0?
Can Osmosis Zone implement filtering to ensure the correct channel is used?

Compensation:
We will manually transfer stuck CIF tokens (as shown in the provided transaction link) to the intended destination wallets to compensate for this inconvenience.
Next Steps:
Please advise on the best course of action to resolve this issue and ensure smooth CIF deposits and withdrawals on Osmosis Zone.

Thanks for the investigation. Someone else had already claimed that Osmosis was using the wrong channel, but I've been unable to confirm whether this is the case recently, because of the nodes not being https.
I know that my initial attempt used the channel-39205 channel, so I'm not sure why some users are saying that Osmosis Zone is using the wrong channel...

I see that IOBscan shows the OSMO icon and chain-id with channel-39057, but are we certain this was triggered by Osmosis Zone and not some other interface?

Hi Jeremy,
Thank you for the updates.
Regarding the incorrect channel issue, you're right, we can't confirm whether it originated from the Osmosis Zone UI or other interface.
Your initial attempt using channel-39205 resulted in an IBC timeout error. I suspect this might be related to our ongoing websocket connection issue, which we're actively troubleshooting with Google Cloud, our server provider.
To aid further investigation, I'll submit the following endpoints for your reference:

HTTPS RPC: https://cif_node.cifer.ai
REST Endpoint: https://api.cifer.ai

Please note that the websocket connection issue might persist for a few more days while troubleshooting continues.
I will continue to provide active updates as soon as we get further information. We apologize for any inconvenience this may cause.

Hi Jeremy,
Following up on the withdrawal issue. I updated the HTTPS nodes and resolved the websocket connection problem on our end. However, I'm still encountering issues during withdrawal tests.
Here's what's different this time:

Console logs don't show any websocket connection errors.
There are no "Transaction failed" messages, but the transaction gets stuck in a loop of pending, failed, and pending refund.

In console logs, while proceeding withdrawal, it shows "ERR_CONNECTION_CLOSED"

I checked the transaction on the explorer and found that the packet sequence is 16. I also verified on Hermes that the unreceived packet is showing as expected.

Also, transferring IBC tokens via Keplr also results in unreceived packets.
Given these observations, I'm unsure about the root cause.
As it's possible to be a relayer issue, I'll also raise this with the Hermes team for further investigation.
Any insights you can offer on this case would be much appreciated.

Thanks for providing thorough investigation details. I agree that it seems to most likely be issue with the relayer.


ERROR: Could not build wheels for monotonic_align, which is required to install pyproject.toml-based projects

Environment:
Windows 10 Pro - 10.0.19045 Build 19045
Python - 3.10.12 (as requested)
Conda Version - 23.5.2
Steps for Reproduction:
Set up a new Conda environment using conda create -n env_name.
Activate the new environment using conda activate env_name.
Follow the installation instructions for the project up to the point of the error.
Run the command that caused the failure: [pip install -r requirements.txt]
Expected Behavior:
Package's should install without a hitch.
Actual Behavior:
Building wheel for monotonic_align (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for monotonic_align (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [3 lines of output]
core.c
C:\Users\Sytan\miniconda3\envs\bud_e\include\pyconfig.h(59): fatal error C1083: Cannot open include file: 'io.h': No such file or directory
error: command 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.37.32822\bin\HostX86\x64\cl.exe' failed with exit code 2
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for monotonic_align
Failed to build monotonic_align
ERROR: Could not build wheels for monotonic_align, which is required to install pyproject.toml-based projects
Additional Notes:
My system uses a Dual GPU setup, though this has rarely caused issue for me in the past. I use a 3090 as my main GPU, with a 3060ti for secondary compute and LLM memory pooling
I have decided to post this error, as I can likely find my way around it, but many users may be deterred by this error. The effects of this error have yet to be fully tested.

Issue remedied by re-installing latest MSVSC 2022. Seems not having the windows 10 SDK was the source of the issue. I suggest adding it to the list of install instructions to ensure that people who opted out of it know to install it for compatibility.

Had a second issue where it said no E-Peak was installed because the command provided doesn't point to the proper location on my system.
The one provided is as follows: C:\Program Files\eSpeak NG\libespeak-ng.dll
However it was actually installed at C:\Program Files (x86)\eSpeak NG\libespeak-ng.dll
I am not sure if this is the same for all windows systems, but this might be confusing for some


small style fix and use Gaussian uncertainties if data is un-weighted

Let me merge these hotfixes, because they are rather urgent.


Api rework

Why did i do this?

makes easier to combine code and reduce duplicates
Removed entire dependency on echo go
API more "unified" so same rendering logic etc for every response

The parsing logic is probably still very confusing and will be refactored in the future. But it works and be replace the current implementation 1:1


Optional properties

Github is experiencing issues with Git operations, but when that is done this branch is ready for merging.


Solaris tgmath fix

Removed hyper_carray erlang source file and nif implementation.  This works around https://github.com/GameAnalytics/hyper/issues/15

+1


Tests case with same name in different folders

I've noticed, that test cases with same name in different test case folders works incorrectly sometimes.
On first run of second test case it really run previously run test case from another folder. On second run it recompiles test and run it normally, but the same problem will be repeated if we run first test case.
I'll prepare PR which will rename one of such test case pair.

I've noticed this too. I think it has to do with the nunit test runner; it never broke when I was using ReSharper's runner but it seems to work wrong in the VS one.
We can probably just prefix the test case names somehow? I'm not sure if that will work.


frint-react: Empty Component when Region is empty

Current situation
Right now, when a Region has no Apps to render, it just remains empty.
It would be useful if we can pass some default Component to render in those cases.
Proposed API
import EmptyRegionContent from '../components/EmptyRegionContent';

<Region name="sidebar" empty={EmptyRegionContent} />

If the sidebar region is empty, it would render EmptyRegionContent component by default.

Nice idea!
As for naming, using something like default sounds more intuitive in my opinion. Mainly because the keyword is common in different languages (SQL, js, C#, etc...) for expressing a similar concept.
Should it also enable specifying a collection of default components?

default is tricky, just like class, module and exports as variable names in JavaScript.

Yep, awesome idea. I like empty because it is the same as we do for lists.


Fixed documentation error for LTTB decimator

Hello,
Tried to fix #625 by replacing 'using by using' with 'using'.
Let me know if this works or if I need to make other changes.
Thank you!

Thanks for the contribution @Mikerniker. We will proceed to merge it.

Thanks, too @dinhlongviolin1 !


[BUG]: Agent failed to download tasks / initialize

New issue checklist

[X] I searched for existing GitHub issues
[X] I read pipeline troubleshooting guide
[X] I checked how to collect logs

Task name
No response
Task version
No response
Issue Description
This pipeline was working fine yesterday, but now it's crashing while trying to download tasks on the Microsoft agent. It's designed to build iOS and Android apps using React Native.
Environment type (Please select at least one enviroment where you face this issue)

[ ] Self-Hosted
[X] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows 11
Relevant log output
Set build variables.
Download all required tasks.
Downloading task: NodeTool (0.235.1)
##[debug]Task 'NodeTool' has been downloaded into '/Users/runner/work/_tasks/NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2/0.235.1'.
Downloading task: YarnInstaller (3.0.2003)
##[debug]Task 'YarnInstaller' has been downloaded into '/Users/runner/work/_tasks/YarnInstaller_2ec1147b-5c33-41df-94b5-676758d87c1b/3.0.2003'.
##[warning]Task 'Yarn Tool Installer' version 3 (YarnInstaller@3) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance
Downloading task: CmdLine (2.244.3)
##[debug]Task 'CmdLine' has been downloaded into '/Users/runner/work/_tasks/CmdLine_d9bafed4-0b18-4f58-968d-86655b4d2ce9/2.244.3'.
Downloading task: npmAuthenticate (0.244.1)
##[debug]Task 'npmAuthenticate' has been downloaded into '/Users/runner/work/_tasks/npmAuthenticate_ad884ca2-732e-4b85-b2d3-ed71bcbd2788/0.244.1'.
Downloading task: Bash (3.244.1)
##[debug]Task 'Bash' has been downloaded into '/Users/runner/work/_tasks/Bash_6c731c3c-3c68-459a-a5c9-bde6e6595b5b/3.244.1'.
Downloading task: ios-bundle-version (1.0.0)
##[debug]Task 'ios-bundle-version' has been downloaded into '/Users/runner/work/_tasks/ios-bundle-version_42284b34-be85-4034-890f-8755ad9f6249/1.0.0'.
##[warning]Task 'iOS Bundle Version Numbers' version 1 (ios-bundle-version@1) is dependent on a Node version (6) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: https://aka.ms/node-runner-guidance
Downloading task: InstallAppleCertificate (2.238.1)
##[debug]Task 'InstallAppleCertificate' has been downloaded into '/Users/runner/work/_tasks/InstallAppleCertificate_d2eff759-736d-4b7b-8554-7ba0960d49d6/2.238.1'.

##[error]Object reference not set to an instance of an object.
##[debug]System.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.VisualStudio.Services.Agent.Worker.TaskManager.CheckIfTaskNodeRunnerIsDeprecated(IExecutionContext executionContext, TaskStepDefinitionReference task) in /Users/runner/work/1/s/src/Agent.Worker/TaskManager.cs:line 382
   at Microsoft.VisualStudio.Services.Agent.Worker.TaskManager.DownloadAsync(IExecutionContext executionContext, IEnumerable`1 steps) in /Users/runner/work/1/s/src/Agent.Worker/TaskManager.cs:line 100
   at Microsoft.VisualStudio.Services.Agent.Worker.JobExtension.InitializeJob(IExecutionContext jobContext, AgentJobRequestMessage message) in /Users/runner/work/1/s/src/Agent.Worker/JobExtension.cs:line 140
Finishing: Initialize job

Full task logs with system.debug enabled

 [REPLACE THIS WITH YOUR INFORMATION]

Repro steps
trigger: none

pool:
  vmImage: ubuntu-latest

resources:
  repositories:
    - repository: templates
      type: git
      name: "repositoryName"
      ref: main

stages:

  - template: build-pipeline-ios-android.yaml@templates
    parameters:
      # All parametres to work
      # This template has all the tasks to build.

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."

Same problem here but in DownloadSecureFile@1 task!!!

Same problem in InstallSSHKey@0 task!

same issue here using InstallSSHKey@0 task , seems it´s related with the Advanced Security Build Tasks v 1.1.283 updated yesterday.

Same problem with DownloadSecureFile@1 task

This issue was opened, I believe the problem was the latest release of the agent that performs validation.

It seems this PR solves it.

Here we use InstallSSHKey@0 task to build our project with git submodule, so we cannot build anything because this issue!

Hello,
I'm encountering a similar issue to what was described. The pipeline was working fine yesterday, but now it’s crashing while trying to download tasks on the Microsoft agent. The error I’m seeing is as follows:

It appears the issue is related to the InstallAppleCertificate (2.238.1) task, as indicated by the error message.
I noticed that @willianantunes mentioned the problem with the DownloadSecureFile task was resolved, but I haven’t found a solution for InstallAppleCertificate.
Any suggestions for resolving the issue with this task?
Thank you!

@rodolfourb I believe the same solution solves both problems, We are waiting for the team's evaluation.

Hi All,
It should be mitigated now by turning off a feature flag. You should not be seeing this with any of the tasks anymore.

Hi,
Could you explain the solution to fix this warning ? I did get what to do in your thread.
Regards


WebPack emulates require('underscore') incorrectly

I updated from 1.9.2 to 1.10.2 today and for me mixins are not working anymore when using require('underscore');
This fails with TypeError: _.camelcase is not a function:
const _ = require('underscore');
const underscoreString = require('underscore.string');

_.mixin(underscoreString.exports());

console.log(_.camelcase('foo-bar'));

but this works:
import _ from 'underscore';
const underscoreString = require('underscore.string');

_.mixin(underscoreString.exports());

console.log(_.camelcase('foo-bar'));

Sorry to hear that this is biting you, @dmaicher. However I cannot reproduce this with Underscore 1.10.2 and underscore.string 3.3.5. Is there anything special about your setup?

Thanks for your fast reply :blush:
I'm using<EMAIL_ADDRESS>and the issue happens with code bundled for the browser. When I run the code with node on the CLI then it appears to be fine :confused:

Here is a minimal reproducer: https://github.com/dmaicher/underscore_issue_2852

Here is your problem:
https://github.com/dmaicher/underscore_issue_2852/blob/348eef226ec7392b2ced2b92ddf2fcba2517ab5c/public/build/app.js#L13
That import path, underscore/modules/index-all.js, must WebPack have obtained from the module field in our package.json:
https://github.com/jashkenas/underscore/blob/5d8ab5e37c9724f6f1181c5f95d0020815e4cb77/package.json#L17-L18
whereas the main field is what it should have used, given that you are using CommonJS imports. module is for ES imports in tools that support them, main is for everybody else. This explains why your code works with import but not with require().
Apparently, WebPack nowadays assumes ES modules by default but has a fallback for CommonJS imports. I guess you'll have to configure it somehow to not assume ES modules or to ignore the module field. Or maybe you want to switch to ES modules.
I'm closing this now because this is a WebPack issue rather than an Underscore issue. Feel free to continue commenting, though.

@jgonggrijp thanks for checking :+1:
I was able to fix it by adding an alias for resolving in the webpack config:
'underscore': 'underscore/underscore.js',
But this seems a bit odd to me. Many other packages I use specify "main" and "module" inside their package.json and for them it works fine.
Webpack takes the first field it finds in the order ['browser', 'module', 'main']
See https://webpack.js.org/configuration/resolve/#resolvemainfields
I'm curious why it only fails for underscore but seems to be working for other packages :blush:

If you name those other packages, I'm happy to take a look. Anyway, module and main are not meant to be interchangeable, so WebPack's treating them as such is unwarranted:
https://github.com/rollup/rollup/wiki/pkg.module
The documentation you linked to hints at a perhaps slightly less ugly solution, which is to set resolve.mainFields to ['main']. Again, I believe WebPack shouldn't be considering module in the first place, since you are using CommonJS imports.

Just in case here are some packages I use that have both module and main:
https://www.npmjs.com/package/vuejs-datepicker
https://www.npmjs.com/package/bootstrap-vue
https://www.npmjs.com/package/acorn

Related webpack issue: https://github.com/webpack/webpack/issues/5756

Yes, that is your issue. Although there also seems to be something off with the way WebPack is emulating CommonJS when resolving to the module. It appears that it is doing something like this:
// converting modules/index-all.js to ES3
var underscoreESModule = {
    'default': _,
    map: _.map,
    filter: _.filter,
    // ...
};

// in your code that imports underscore
var _ = underscoreESModule;

The latter line would make sense if you were doing this:
import * as _ from 'underscore';

but what you're actually doing is equivalent to this:
import _ from 'underscore';

and the right way to translate that to ES3 in WebPack would be as follows:
var _ = underscoreESModule['default'];

This is also exactly the problem that other people are running into in webpack/webpack#5756.
Other build tools such as Browserify and Rollup handle this more intelligently. Just saying...

Here is your problem:
https://github.com/dmaicher/underscore_issue_2852/blob/348eef226ec7392b2ced2b92ddf2fcba2517ab5c/public/build/app.js#L13
That import path, underscore/modules/index-all.js, must WebPack have obtained from the module field in our package.json:
https://github.com/jashkenas/underscore/blob/5d8ab5e37c9724f6f1181c5f95d0020815e4cb77/package.json#L17-L18
whereas the main field is what it should have used, given that you are using CommonJS imports. module is for ES imports in tools that support them, main is for everybody else. This explains why your code works with import but not with require().
Apparently, WebPack nowadays assumes ES modules by default but has a fallback for CommonJS imports. I guess you'll have to configure it somehow to not assume ES modules or to ignore the module field. Or maybe you want to switch to ES modules.
I'm closing this now because this is a WebPack issue rather than an Underscore issue. Feel free to continue commenting, though.

This reply just solved an issue I've been battling for 12 freaking days in our webpack build.
THANK YOU!

@jgonggrijp thanks for checking 👍
I was able to fix it by adding an alias for resolving in the webpack config: 'underscore': 'underscore/underscore.js',
But this seems a bit odd to me. Many other packages I use specify "main" and "module" inside their package.json and for them it works fine.
Webpack takes the first field it finds in the order ['browser', 'module', 'main'] See https://webpack.js.org/configuration/resolve/#resolvemainfields
I'm curious why it only fails for underscore but seems to be working for other packages 😊

This reply just solved an issue I've been battling for 12 freaking days in our webpack build.
THANK YOU!


souffle: 2.4 -> 2.4.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/souffle/versions.
meta.description for souffle is: A translator of declarative Datalog programs into the C++ language
meta.homepage for souffle is: https://souffle-lang.github.io/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.4.1 in filename of file in /nix/store/kkgg5xws8dhqblsmy7rrbw2b1d7ya9xs-souffle-2.4.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
souffle

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kkgg5xws8dhqblsmy7rrbw2b1d7ya9xs-souffle-2.4.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A souffle https://github.com/r-ryantm/nixpkgs/archive/b4dcfa1130094568405aaea13668cdc84b5b323f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b4dcfa1130094568405aaea13668cdc84b5b323f#souffle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kkgg5xws8dhqblsmy7rrbw2b1d7ya9xs-souffle-2.4.1
ls -la /nix/store/kkgg5xws8dhqblsmy7rrbw2b1d7ya9xs-souffle-2.4.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

souffle

Maintainer pings
cc @thoughtpolice @copumpkin @wchresta for testing.

Result of nixpkgs-review pr 267924 run on x86_64-linux 1

1 package built:

souffle


where to set the value of ${{ secrets.GITHUB_TOKEN }}?

hi.
i used ur template.
i visit https://github.com/briteming/gialog/blob/main/.github/workflows/sync.yml ,but where to set the value of ${{ secrets.GITHUB_TOKEN }}?
thank u for ur reply,

secrets.GITHUB_TOKEN is code to reference the access token that GitHub provides automatically, so you do not need to set anything up for this.


Error: no available backend found. ERR: [wasm] RangeError: Out of memory

System Info
@huggingface/transformers 3.0.0-alpha.19, Mobile Safari, iOS 17.6.1
Environment/Platform

[X] Website/web-app
[ ] Browser extension
[ ] Server-side (e.g., Node.js, Deno, Bun)
[ ] Desktop app (e.g., Electron)
[ ] Other (e.g., VSCode extension)

Description
Getting the error "Error: no available backend found. ERR: [wasm] RangeError: Out of memory" in mobile Safari when trying to load model Xenova/clip-vit-base-patch16.  This same model loads (albeit a bit unstable) under transformers.js v2.  This code does work on desktop Chrome on MacOS.
Reproduction
pipeline("zero-shot-image-classification", "Xenova/clip-vit-base-patch16")

May or may not be related, but https://huggingface.co/spaces/webml-community/segment-anything-webgpu doesn't seem to work on mobile Safari either, but looks like it's using an older version of v3.  Just wondering if v3 just generally doesn't work on iOS.

WebGPU isn't officially supported by Safari yet. Maybe you can try with its technical preview: https://webkit.org/blog/14879/webgpu-now-available-for-testing-in-safari-technology-preview/.

I just tried that on Mobile Safari.  Didn't seem to change anything.  Same error.
So, with V3, are you saying WebGPU is the only engine available and it will not fall back to a CPU version if WebGPU is not available?

CPU is available in V3. auto-fallback has recently become an option, you have to set it to that though.
Set device to wasm in the inference settings.

So setting "device" to "wasm" will make the transformers.js code try WebGPU first and then if that fails it will fall back to CPU or are you saying that my code would need to create the fallback code?

I tried this but am still getting the "Out of memory" error.  Since the error includes "wasm" in it, I'm guessing it was already doing the auto fall back to "wasm".  Did something change in the wasm engine that would cause this since it was working in v2?

Try "auto". Wasm sets it to cpu only.

After changing it to "auto" it doesn't seem to try and load the "wasm" version at all.  Not even getting the out of memory error now so not really sure what it is doing, but not working either.

How is "auto" different than just not setting "device" to anything?

Looks like this may be an iOS Safari issue and only be fixed in iOS 18 which just came out so makes using v3 hard for me at the moment until that is more widely available.  Odd though that this worked in iOS 17 with transformer.js V2.
https://github.com/microsoft/onnxruntime/issues/22086


The Final Kithmaze - "Bonus: under 12 statements" Error

Played The Final Kithmaze and had the following code (using Lua). This completes the level but doesn't give the bonus for under 12 statements
for i=1,4,1 do
  self:moveRight()
  self.moveUp()
  local enemy=self:findNearestEnemy()
  self:attack(enemy)
  self:attack(enemy)
  self:moveRight()
  self:moveDown()
end

also in js, this code doesn't award the objective:
loop {
    this.moveXY(this.pos.x + 12, this.pos.y);
    var preAttackPos = {x: this.pos.x, y: this.pos.y + 12};
    this.moveXY(preAttackPos.x, preAttackPos.y);
    this.attack(this.findNearestEnemy());
    this.moveXY(preAttackPos.x + 12, preAttackPos.y);
    this.moveXY(this.pos.x, this.pos.y - 24);
    this.moveXY(this.pos.x, this.pos.y + 12);
}

This one doesn't work for under 6 statements in The Gauntlet, either:
loop {
    this.moveRight();
    this.attack(this.findEnemies()[0]);
}

#2612 is Linked

I've changed it so that at least in Lua, Clojure, and Io (where the statement counting never works), you get the bonus anyway regardless of your code. I think the real fix will be switching Aether to rely on each parser to count unique statements before any transpilation, normalization, or instrumentation.

Also for "the gauntlet", this 6 line snippet grants the "Bonus: under 6 statements", where it probably should not:
loop:
enemy = self.findNearestEnemy()
if enemy:
self.attack(enemy)
else:
self.moveRight()

Second Kithmaze, user lost bonus because of 1 counting as an extra statement.
loop:
    self.moveRight(1)
    self.moveUp(1)
    self.moveRight(1)
    self.moveDown(1)


Initial migrate combined with seed returns "table does not exist"

Bug description
When creating the first migration by running npx prisma migrate dev --preview-feature with a valid prisma/seed.ts, an error is thrown.
PS.: It works fine when running npx prisma seed --preview-feature after DB is created.
PrismaClientKnownRequestError2 [PrismaClientKnownRequestError]: The table `user` does not exist in the current database.
    at cb (C:\GitHub\poc-nestjs-ocean\node_modules\@prisma\client\runtime\index.js:78689:17)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'P2021',
  clientVersion: '2.17.0',
  meta: { table: 'user' }
}
Error: Command failed with exit code 1: ts-node "C:\GitHub\poc-nestjs-ocean\src\prisma\seed.ts"
    at makeError (C:\GitHub\poc-nestjs-ocean\node_modules\prisma\build\index.js:2566:15)
    at handlePromise (C:\GitHub\poc-nestjs-ocean\node_modules\prisma\build\index.js:3234:31)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.tryToRunSeed (C:\GitHub\poc-nestjs-ocean\node_modules\prisma\build\index.js:61766:16)
    at async MigrateDev2.parse (C:\GitHub\poc-nestjs-ocean\node_modules\prisma\build\index.js:61902:13)
    at async main (C:\GitHub\poc-nestjs-ocean\node_modules\prisma\build\index.js:100809:18) {
  shortMessage: 'Command failed with exit code 1: ts-node "C:\\GitHub\\poc-nestjs-ocean\\src\\prisma\\seed.ts"',
  command: 'ts-node "C:\\GitHub\\poc-nestjs-ocean\\src\\prisma\\seed.ts"',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: undefined,
  stderr: undefined,
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

How to reproduce
Steps to reproduce the behavior:

Create a migration with an User model
Create a seed.ts file that adds an user
Run npx prisma migrate dev --preview-feature
See error

Expected behavior
Create DB record without throwing any errors.
Prisma information
model User {
  id           Int         @id @default(autoincrement())

  email        String      @unique
  password     String?

  name         String?
}

Environment & setup

OS: Windows
Database: MariaDB
Node.js version: 12.18.4
Prisma version: 2.17.0

Hi @paulosalvatore — I think this is a symptom of a known regression with MySQL on windows in 2.17.0 — this is fixed in 2.18.0, so I'll close. Thanks for reporting the issue, and if you see the same problem in 2.18.0, feel free to reopen!

Not sure if I'm doing anything wrong, but still experiencing errors in 2.18.0.
Npm script
"prisma:migrate": "npx prisma migrate dev --preview-feature",
"prisma:merge": "npx prisma-merge",
"prisma:run": "npm run prisma:merge & rimraf src/prisma/migrations & npx prisma migrate dev --preview-feature --name init & npm run prisma:generate & npx prisma db seed --preview-feature"

Error stack
Running ts-node "src\prisma\seed.ts" ...
PrismaClientKnownRequestError2 [PrismaClientKnownRequestError]: The table `user` does not exist in the current database.
    at cb (C:\projects\backend\node_modules\@prisma\client\runtime\index.js:79160:17)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'P2021',
  clientVersion: '2.18.0',
  meta: { table: 'user' }
}
Error: Command failed with exit code 1: ts-node "src\prisma\seed.ts"
    at makeError (C:\projects\backend\node_modules\prisma\build\index.js:2564:15)
    at handlePromise (C:\projects\backend\node_modules\prisma\build\index.js:3232:31)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.tryToRunSeed (C:\projects\backend\node_modules\prisma\build\index.js:61995:16)
    at async MigrateDev2.parse (C:\projects\backend\node_modules\prisma\build\index.js:62146:13)
    at async main (C:\projects\backend\node_modules\prisma\build\index.js:103094:18) {
  shortMessage: 'Command failed with exit code 1: ts-node "src\\prisma\\seed.ts"',
  command: 'ts-node "src\\prisma\\seed.ts"',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: undefined,
  stderr: undefined,
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

Full terminal log after running script
C:\projects\backend>npm run prisma:run

><EMAIL_ADDRESS>prisma:run C:\projects\backend
> npm run prisma:merge & rimraf src/prisma/migrations & npx prisma migrate dev --preview-feature --name init & npm run prisma:generate & npx prisma db seed --preview-feature

><EMAIL_ADDRESS>prisma:merge C:\projects\backend
> npx prisma-merge

npx: installed 89 in 5.113s
Merged prima files into src/prisma/schema.prisma
Environment variables loaded from .env
Prisma schema loaded from src\prisma\schema.prisma
Datasource "db": MySQL database "db" at "localhost:3306"

√ - Drift detected: Your database schema is not in sync with your migration history.
- The following migration(s) are applied to the database but missing from the local migrations directory:<PHONE_NUMBER>0654_init

We need to reset the MySQL database "db" at "localhost:3306".
Do you want to continue? All data will be lost. ... yes

Running ts-node "src\prisma\seed.ts" ...
PrismaClientKnownRequestError2 [PrismaClientKnownRequestError]: The table `user` does not exist in the current database.
    at cb (C:\projects\backend\node_modules\@prisma\client\runtime\index.js:79160:17)
    at processTicksAndRejections (internal/process/task_queues.js:97:5) {
  code: 'P2021',
  clientVersion: '2.18.0',
  meta: { table: 'user' }
}
Error: Command failed with exit code 1: ts-node "src\prisma\seed.ts"
    at makeError (C:\projects\backend\node_modules\prisma\build\index.js:2564:15)
    at handlePromise (C:\projects\backend\node_modules\prisma\build\index.js:3232:31)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async Object.tryToRunSeed (C:\projects\backend\node_modules\prisma\build\index.js:61995:16)
    at async MigrateDev2.parse (C:\projects\backend\node_modules\prisma\build\index.js:62146:13)
    at async main (C:\projects\backend\node_modules\prisma\build\index.js:103094:18) {
  shortMessage: 'Command failed with exit code 1: ts-node "src\\prisma\\seed.ts"',
  command: 'ts-node "src\\prisma\\seed.ts"',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: undefined,
  stderr: undefined,
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}
The following migration(s) have been created and applied from new schema changes:

migrations/
  └─<PHONE_NUMBER>0746_init/
    └─ migration.sql

✔ Generated Prisma Client (2.18.0) to .\node_modules\@prisma\client in 383ms

Everything is now in sync.

><EMAIL_ADDRESS>prisma:generate C:\projects\backend
> npx prisma generate

Environment variables loaded from .env
Prisma schema loaded from src\prisma\schema.prisma

✔ Generated Prisma Client (2.18.0) to .\node_modules\@prisma\client in 377ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
\`\`\`
import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
\`\`\`
Environment variables loaded from .env
Prisma schema loaded from src\prisma\schema.prisma
Running ts-node "src\prisma\seed.ts" ...

Your database has been seeded.

Maybe older migrations created with 2.17.0?

I always run rimraf src/prisma/migrations to delete all migrations before running it again, since generated migrations after the first one contains a lot of constraints removal and erases the data no matter what.
I can create a GitHub repo to simulate the behaviour if that helps.


Add estimates for a complete time series in each country/subnational region

Due to computational and storage constraints, it is not feasible to run the complete time series every day with our current resources. For this reason, we have shifted our daily updates to focus on a rolling window of the last 3 months of data. Many users may be interested in the complete time series - please respond to this issue in order for us to assess the priority of this requirement.
We are considering two solutions to this issue:

Piecing together daily estimates from rolling model fits
Running less frequent complete time series runs and linking these to our real-time estimates.

Hi Carl,
Thanks for pinging this. For your specific use case it sounds like its worth generating your own Rt values rather than piggybacking off this repo (as discussed on Friday). I've knocked up a gist here of my thinking around how that can be nicely done: https://gist.github.com/seabbs/07035fa4019a0c0117e28f9037593f28

I think we can look to do this post- new infrastructure.
It will need a task to allow less frequent running of some datasets (as I don't think we would want the full history daily) but we could add an infrequent job that does this - clone all the existing datasets and run them with a wider window.
This would also be blocked by #102

I have raised a task in our private infra repo to switch control over what runs and it's schedule into there so that we can add as many datasets to this repo as people can imagine and maintain, and LSHTM / Met Office maintain control over what is run when on our infrastructure and the associated compute cost (epiforecasts/covid-rt-estimates-infra#9 - for internal reference).

Hi all,
I would also be interested in Rt estimates for historical periods (ideally the full time-series) - are these available somewhere at the moment, or is it recommended that I run this locally?
Cheers

Hi @MrinankSharma - latest is still as per #103 - we are a few tasks away from being able to have to compute space to run them centrally and if you want to run it locally you will need to change the rolling window function (one of the tasks that needs changing - #102 )

Can we revisit this now that we're running in batch mode? Seems like steps required would be:

duplicating everything in R/lists/datasets.r with a different name, pointing to a different directory and using a different # of weeks looking in the past (e.g. the number of weeks since 1 Jan 2020)-
adding them to the batch list as running e.g. weekly

Suggested frequency is monthly

Reopening as still work in progress.


feat: add root path argument

Duplicate of #11 but different implementation.
@g5t does this fit your use case?

Hopefully late comments are still appreciated: this implementation meets my requirements :partying_face:


Add missing copy right

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/lgtm
/approve


Add Event Logos

It would be very useful to allow optional event logos.
This will help people find what they're looking for quickly.
We should do this by adding a logo field to the event toml file
Images could be added to the repo (safer) and/or linked externally (riskier)
must constrain size (maximums)

to keep color less overwhelming / overloading, we could try making the colors grayscale, and then full color on hover (there's a css class for grayscale images IIRC)


[GitHub Commenter] WARNING: Empty table records of issue BlackDuckHubResults from BlackDuck

While running the GitHub action for Blackduck, I can see the results properly, but the comments are not coming as PR comments
Action:

name: Perform Blackduck checkout
id: bd-scan
uses<EMAIL_ADDRESS>env:
DETECT_PROJECT_NAME: '${{ env.blackduckProjectName }}'
DETECT_PROJECT_VERSION_NAME: master
DETECT_PARENT_PROJECT_NAME: master-project
DETECT_PARENT_PROJECT_VERSION_NAME: master
DETECT_PROJECT_DESCRIPTION: '${{ env.blackduckProjectName }}'
DETECT_TOOLS_EXCLUDED: SIGNATURE_SCAN
DETECT_WAIT_FOR_RESULTS: TRUE
DETECT_RISK_REPORT_PDF: TRUE
DETECT_POLICY_CHECK_FAIL_ON_SEVERITIES: BLOCKER,CRITICAL,MAJOR,MINOR
DETECT_TIMEOUT: 3600
LOGGING_LEVEL_COM_SYNOPSYS_INTEGRATION: DEBUG
DETECT_RISK_REPORT_PDF_PATH: ./bd-scan
DETECT_OUTPUT_PATH: ./bd-scan
DETECT_PROJECT_CODELOCATION_UNMAP: true
# DETECT_BLACKDUCK_RAPID_COMPARE_MODE: ALL
with:
blackduck_token: ${{ env.blackduckAuth }}
blackduck_url: ${{ secrets.DS_BLACKDUCK_URL }}
github_token: ${{ secrets.GITHUB_TOKEN }}
blackduck_scan_full: false
blackduck_automation_fixpr: false
blackduck_prComment_enabled: true
blackduck_scan_failure_severities: 'BLOCKER,CRITICAL,MAJOR,MINOR'
include_diagnostics: true

Github action logs

202***-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- ======== Detect Result ========
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- Rapid Scan Result: (for more detail look in the log for Rapid Scan Result Details)
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 		Critical and blocking policy violations for
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			* Components: 0
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			* Security: 0
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			* License: 0
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 		Other policy violations
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			* Components: 3
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			* Security: 11
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			* License: 0
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 		Policies Violated:
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			High Security Vulnerability
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			Medium Security Vulnerability
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 		Components with Policy Violations:
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 		Components with Policy Violation s:
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			Lodash .6.0 (npmjs:lodash.omitby/.6.0)
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			follow-redirects 1.15.5 (npmjs:follow-redirects/1.15.5)
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- ===== Transitive Guidance =====
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 		Transitive upgrade guidance:
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- 			Upgrade component axios/1.6.0 to version 1.6.8 in order to upgrade transitive component follow-redirects/1.15.5
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- ======== Detect Stat ========
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- GIT: SUCCESS
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- NPM: SUCCESS
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- Overall Stat: SUCCESS - Detect exited successfully.
202***-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- ===============================
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: ---
202-05-25 :30:31.0000 UTC [Blackduck Execution] [main] INFO: --- Detect duration: 00h 01m 26s 268ms
202-05-25 :30:31.1515 UTC [Blackduck Execution] INFO: Provided value for resource 'blackduck.completed'
202-05-25 :30:31.1515 UTC [Blackduck Execution] DEBUG: Provided value '' for resource 'blackduck.completed'
202***-05-25 :30:31.1522 UTC [Blackduck Execution] INFO: Provided value for resource 'blackduck.results.path'
202-05-25 :30:31.1523 UTC [Blackduck Execution] DEBUG: Provided value '/home/runner/work//.bridge/Blackduck Execution/detect' for resource 'blackduck.results.path'
202***-05-25 :30:31.1527 UTC [Blackduck Execution] INFO: Adapter finished
202-05-25 :30:31.2980 UTC [Synopsys Bridge] INFO: Starting adapters for stage githubprcomment
202-05-25 :30:31.2898 UTC [Blackduck Results] DEBUG: reading report file "/home/runner/work//.bridge/Blackduck Execution/detect/runs/202***-05-25--29-07-186/scan/_master_BlackDuck_DeveloperMode_Result.json"
202***-05-25 :30:31.738 UTC [Blackduck Results] INFO: *** retrieved successfully
202-05-25 :30:31.2981 UTC [SCM Checker] INFO: Adapter finished
202-05-25 :30:31.2981 UTC [Synopsys Bridge] INFO: Starting Adapter: GitHub Commenter
202-05-25 :30:31.5502 UTC [Blackduck Results] INFO: Added entry to resource 'commenter.issues'
202-05-25 :30:31.5502 UTC [Blackduck Results] DEBUG: Added entry 'BlackDuckHubResults' to resource 'commenter.issues.[0].uid'
202-05-25 :30:31.5502 UTC [Blackduck Results] DEBUG: Added entry '
x Found dependencies violating policy!
' to resource 'commenter.issues.[0].commentTable.description'
202-05-25 :30:31.5502 UTC [Blackduck Results] DEBUG: Added entry '[Policies Violated Dependency License(s) Vulnerabilities Short Term Recommended Upgrade Long Term Recommended Upgrade]' to resource 'commenter.issues.[0].commentTable.heads'
202-05-25 :30:31.5502 UTC [Blackduck Results] DEBUG: Added entry 'table' to resource 'commenter.issues.[0].commentType'
202-05-25 :30:31.5502 UTC [Blackduck Results] DEBUG: Added entry 'BlackDuck' to resource 'commenter.issues.[0].from'
202-05-25 :30:31.550 UTC [Blackduck Results] INFO: Adapter finished
202-05-25 :30:31.595 UTC [Blackduck Component Locator] INFO: skipping fix pull requests creation as "blackduck.automation.fixpr" or "blackduck.fixpr.enabled" is configured to ***
202***-05-25 :30:31.6067 UTC [Blackduck Component Locator] INFO: Adapter finished
202-05-25 ***:30:31.6539 UTC [GitHub Commenter] INFO: will e default GitHub API URL "https://api.github.com/", as "github.api.url" and "github.host.url" is not configured
202-05-25 :30:32.6915 UTC [GitHub Commenter] WARNING: Empty table records of issue BlackDuckHubResults from BlackDuck
202-05-25 :30:32.70 UTC [GitHub Commenter] INFO: Adapter finished

Did you get this working @harsharora001 ? I'd like to get PR comments working for our blackduck scans for visibility, but am getting the same warning despite there being security warnings in the detect rapid scan results.


raftstore: add detail log for large region

What problem does this PR solve?
Add detailed log for large regions with printing the ssts involved and corresponding size/keys to give more information to investigate related problems.
Related changes

Need to cherry-pick to the release branch

Check List

No code

Release note

PTAL


Remote scan

Can we somehow use this to remotely scan (internal) servers? Like foreach server in .txt or from an AD filter?

Yes, as some people have already done so, see #8
I think you could deploy the windows executable (if AV blocks it, you might want to create your own binary) via SSCM and let it write the logs to a share. I would also recommend to lock down the share if possible that not everyone can just list and read files from it.

I have opened GitHub discussions https://github.com/fox-it/log4j-finder/discussions, feel free to start a thread there so we don't have discussions in closed tickets and lose visibility. I hope other people can share their experiences on how they used and deployed it.


[BUG] [2.0] No menu reaction - "gddb_constants" isn't declared

Hello
I tried to use this add-on. I can dowload and install it as described in documentation.
When I enable it in Project Settings, Godot returns the following issues:
 res://addons/godot_db_manager/db_interface.gd:15 - Parse Error: The identifier "gddb_constants" isn't declared in the current scope.
 modules/gdscript/gdscript.cpp:599 - Method failed. Returning: ERR_PARSE_ERROR

 res://addons/godot_db_manager/dlgs/new_db_dlg.gd:30 - Parse Error: The identifier "gddb_globals" isn't declared in the current scope.
 modules/gdscript/gdscript.cpp:599 - Method failed. Returning: ERR_PARSE_ERROR

However, I can start it in Project>Tools and the main window appears. After this point, the commands in File>New DB/Load DB don't answer.
OS : Windows10
Godot 3.2.2.stable
The error occured for downloads from the Godot Engine and Github.
I committed the folder as well as a few screenshots here : https://github.com/Arkadeievitch/DataBaseManager_Issue/tree/master
Thanks for reading.

Hello,
Please make sure you enable the plugin in the Project settings:
From menu:
"Project" -> "Project Settings" -> "Plugins" tab -> check the status.
The checkbox should be enabled.

Hello
I tried to use this add-on. I can dowload and install it as described in documentation.
When I enable it in Project Settings, Godot returns the following issues:
 res://addons/godot_db_manager/db_interface.gd:15 - Parse Error: The identifier "gddb_constants" isn't declared in the current scope.
 modules/gdscript/gdscript.cpp:599 - Method failed. Returning: ERR_PARSE_ERROR

 res://addons/godot_db_manager/dlgs/new_db_dlg.gd:30 - Parse Error: The identifier "gddb_globals" isn't declared in the current scope.
 modules/gdscript/gdscript.cpp:599 - Method failed. Returning: ERR_PARSE_ERROR

However, I can start it in Project>Tools and the main window appears. After this point, the commands in File>New DB/Load DB don't answer.
OS : Windows10
Godot 3.2.2.stable
The error occured for downloads from the Godot Engine and Github.
I committed the folder as well as a few screenshots here : https://github.com/Arkadeievitch/DataBaseManager_Issue/tree/master
Thanks for reading.

Hello! I know it's been quite a while since you posted this and I have to find the actual reason as to why that error is happening, but the issue seems to be related to gddb_constants/gddb_globals being tried to be accessed before the interface enters the tree and so before they can be declared as singletons, so adding this line:
var gddb_constants = load("res://addons/godot_db_manager/core/GDDBConstants.gd").new()
Right at the beginning of db_interface.gd seems to mitigate it. I'm probably going to be forking this project soon and I'll be adding the fix, plus a few more changes to better adapt to my own needs.

Hello,
Thank you for your feedback.
I just merged 2.1 branch into master. Please pull and let me know if this still occurs.
I will update the addon on Godot Assets Lib soon.


Fixed the Projects view button

Added the live projects links to the projects.json and fixed the View button for the projects

Good job @OkenHaha!!

Fixes issue #374


Show a general warning prompt pointing to the upgrade guide

Show a general warning prompt pointing to the upgrade guide, in case we see any warnings related to deprecation from isort
Look at the following warning codes to see if the message is related to deprecation: https://github.com/timothycrosley/isort/issues/1363#issuecomment-670385448
Double check the message with Luciana:
“We found outdated configuration for sorting imports in this workspace. Check the isort upgrade guide to update your settings.”
Options:
Also, log all the warnings as errors in the output channel, otherwise  won't show the warnings by default.

Blocker: https://github.com/PyCQA/isort/issues/1447


On trying to update the gateway the screen shows install instead of update.

[Enter feedback here]
On trying to update the gateway the screen shows install instead of update.

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

ID: 860519a0-9f73-14e7-66c1-faaba7f943b5
Version Independent ID: c9c5d0a1-36e8-72bf-4d8d-5aafe0e01272
Content: Update an on-premises data gateway
Content Source: data-integration/gateway/service-gateway-update.md
Product: on-premises-data-gateway
Technology: ****
GitHub Login: @arthiriyer
Microsoft Alias: arthii

Close/open to trigger our bot. Please ignore. #please-close

Hi @rubeesh
Did you uninstall the old gateway before running the gateway install program? If so, you can still update your on-premises data gateway by selecting Install in the screen you show above, and after entering your credentials, you can select Migrate, restore, or take over an existing gateway. Select Next, and then in the following screen, enter the name of your old gateway and the recovery key for that gateway.


Add README.

Add README with usage instructions.
Include Docker tags: 3.5 -> Alpine 3.5

Fixed.


No apparent way to specify imports for instantiating a WASI module

Looking at the create_wasi_instance  function, it doesn't accept a list of imports. While the main use case for WASI might be to access the low-level syscalls supported by the interface, we should still be able to build WASI modules that import from the runtime host. The ability to specify imports for a WASI module is a feature that's available on other runtimes.
Is there a way using existing public functions to configure imports for a WASI module?

On this line here, the set of imports are empty. It should be fairly straightforward to add a parameter to carry through allowing imports:
https://github.com/bytecodealliance/wasmtime/blob/master/crates/wasi/src/instantiate.rs#L81
If this is the case, please let me know and I can try and submit a PR for this

Would it be possible to solve this using a similar approach to https://github.com/bytecodealliance/wasmtime/pull/901 ?
Where we can configure the wasmtime engine to expose WASI imports to all instantiated modules. This would be as an extension to WASM C-API, declared in its own header file

wasmtime.h was used in the config PR referenced.

My main need is just the simple ability to have both WASI and standalone wasm modules have the ability to have imports. Not letting WASI modules import host functions blocks functionality that I have available in other engines like wasmer

Hi @autodidaddict.  I think there might be some confusion here (on my part, at least).  When you speak of a WASI module do you mean a module that imports WASI functions or a module that implements the WASI spec (i.e. exports WASI functions)?
In the Wasmtime API, a WASI instance is the latter: a module instance that implements WASI itself and exports functions defined by WASI.  Currently there is no way to provide host imports to a WASI instance since WASI doesn't define any imports.  If you're looking at customizing Wasmtime's WASI implementation, that is done currently via the WasiCtxBuilder type.  Recently create_wasi_instance was replaced with a generated Wasi type that represents a WASI instance.  The Wasi type takes a WasiCtx (the type created by WasiCtxBuilder) for its construction to configure the WASI instance.  The wasmtime run command constructs a Wasi instance here.
If you meant how do you instantiate a module that imports WASI functions using the Wasmtime API, you would pass a WASI instance export as an import to Instance::new when instantiating the module.  The wasmtime run command does this here.
@gatesn FYI I actually have a working extension to the C API to enable configuring WASI and easily binding module imports to the engine's WASI instance.  Part of that work also includes a .NET API that wraps the C extensions.  Hopefully I should have that up today for review.

What I mean is... there are two kinds of wasm modules when I think of things - a standalone one that just imports functions from the host that it and the host are aware of. The other is a wasm module that imports wasi functions from the host (e.g. a wasm module that can invoke println!()). In the latter, I can't specify additional host imports above and beyond the ones that it expects for wasi.

The scenario is I have a well-known contract between the host and the guest (e.g. wapc. I want to be able to load either a standalone (no WASI imports) module that requires these imports or a wasm module that imports the wasi standard functions and the ones I need for the well-known contract.

That should already be possible in the Wasmtime API with the list of imports provided to Instance::new when instantiating the module.  The WASI imports can be resolved to a Wasi instance's exports and the remaining imports can be provided by custom host functions.
Essentially like this code is doing in the run command is doing, but instead of bailing when an import isn't found, resolve the import to a host function.  Does that make sense or am I off base?


Support querying external data sources

This feature is also known as "external tables." See Querying External Data Sources for requirements.

Hi MIke, is this really P0?

At standup on Monday I was told this was P0.

I believe that although this deliverable is P0 internally, it should be P1 on GitHub, similar to the other BigQuery "P0" issues that @geigerj changed to P1 some time ago (see log above.)

Ah, that does seem familiar. I'll move it back.

Thanks guys.  Yes, I think the BigQuery "P0" just means absolutely required for next release.  Issue label P0 means drop everything, the house is on fire :)

Closed by #1711 and #1725.


Rasa train should detect changes is external dataset used by custom NLU component

Description of Problem:
I have created a custom RASA NLU component that loads additional training data from a file.
Both for debugging and in production it would be nice if the command "rasa train" could detect changes in the NLU component code or the data file and retain it. Similar to how it detects changes in config, domain etc. Most important is to detect changes in the external training dataset.
Overview of the Solution:
Maybe RASA components could also be fingerprinted in a way to optionally include other files?

Thanks for submitting this feature request 🚀@Ghostvv will get back to you about it soon!✨

I don't think it is a research issue

this could be related to #7581 . Potentially there could be an architectural change in the cards where components decide if they need retraining or not? Not sure how common this kind of setup is however.


BulkAll vs. Exceptions

Using NEST 5.2 with this index code;

 var waitHandle2 = new CountdownEvent(1);

            var bulkAll = elasticClient.BulkAll(docs, b => b
                .MaxDegreeOfParallelism(8)
                .BackOffTime(TimeSpan.FromSeconds(10))
                .BackOffRetries(2)
                .Size(1000)
                .RefreshOnCompleted()
                .Index(indexName)
            );

            bulkAll.Subscribe(new BulkAllObserver(
                onNext: (b) => { Console.Write("."); },
                onError: (e) => { throw e; },
                onCompleted: () => waitHandle2.Signal()
            ));

            waitHandle2.Wait();

            return;

If an exception is thrown the onError is hit, but the code never reaches the return statement
Please advise

Ended up using this solution:
var waitHandle2 = new ManualResetEvent(false);
var docs = new[] {new Product(),new Product()};
var bulkAll = client.BulkAll(docs, b => b
	.MaxDegreeOfParallelism(8)
	.BackOffTime(TimeSpan.FromSeconds(1))
	.BackOffRetries(1)
	.Size(1000)
	.RefreshOnCompleted()
	.Index(indexName)
);

//we set up an observer
Exception ex = null;
var bulkObserver = new BulkAllObserver(
	onError: (e) =>
	{
		ex = e;
		waitHandle2.Set();
		throw e;
	} ,
	onCompleted: () => waitHandle2.Set(),
	onNext: (b) =>  Console.Write("on next")
);

bulkAll.Subscribe(bulkObserver);
waitHandle2.WaitOne();

if (ex != null )
	throw ex;

In the first example noone signals waitHandle2 in RX only onError or onCompleted are called at most once.
If you include a reference to the full RX framework you'll gain handy operators like Finally() and others to deal with this in a more composable way.
It should not be necessary to rethrow in the onError but reviewing our current code i do think i spotted a bug where we need to throw here:
https://github.com/elastic/elasticsearch-net/blob/master/src/Nest/Document/Multiple/BulkAll/BulkAllObservable.cs#L89-L94
and rely on this guy to call OnError once:
https://github.com/elastic/elasticsearch-net/blob/master/src/Nest/Document/Multiple/BulkAll/BulkAllObservable.cs#L57

Thanks mate - and keep up the good work!

Instead of calling .Subscribe() you can now also call .Wait(TimeSpan, Action onNext) which will block and throw exceptions more naturally if blocking is the desired behavior.

Thank @Mpdreamz,
Does BulkAllObservable<T> have a .Wait method? - can't seem to find it


[Autofix error] RET503

versions
$ python --version
Python 3.11.2
$ ruff --version
ruff 0.0.251

example
def foo(bar: list[str]) -> str | None:
    for baz in bar:
        match baz:
            case "yo":
                return sub_foo(baz)

def sub_foo(baz: str) -> str:
    return baz

failing command
(there's no pyproject.toml)
$ ruff check -n --fix --select RET503 .

error: Autofix introduced a syntax error. Reverting all changes.

This indicates a bug in `ruff`. If you could open an issue at:

    https://github.com/charliermarsh/ruff/issues/new?title=%5BAutofix%20error%5D

...quoting the contents of `foo.py`, along with the `pyproject.toml` settings and executed command, we'd be very appreciative!

foo.py:2:5: RET503 Missing explicit `return` at the end of function able to return non-`None` value
Found 1 error.

Thanks!