Slots component not working

Describe the bug
I want to implement slots feature, but just how do i add this? i implement below code but it's not working
here is my code, I implement it without making component out of it though
<Datepicker
  v-model="form.date" :enable-time-picker="false"
  :highlight-week-days="[1,2,3,4,5]"
  :preset-ranges="preset"
  auto-apply date-picker
  format="dd/MM/yyyy" multi-calendars multi-calendars-solo
  placeholder="Select Date Filter" range utc
>
  <template #left-sidebar>

Custom content

  </template>
  <template #right-sidebar>

Custom content

  </template>
</Datepicker>

To Reproduce
Steps to reproduce the behavior:

Init Inertia laravel vue
implement Vue Datepicker

Expected behavior
Left and Right side menu is showing
Screenshots

Desktop & mobile (please complete the following information):

Chrome
Library version 3.3.1

It does work, here is a simple demo. components is just a category, if you used it as a slot name, perhaps that is why it doesn't show up.


Make extendable Iterable interfaces

Fixes #19753
Requires updating @ types/node https://github.com/DefinitelyTyped/DefinitelyTyped/pull/21270.

@DanielRosenwasser Can we continue this?

@DanielRosenwasser Can you?


iOS Build Fastlane Error Exit status: 65

Build/Submit details page URL
No response
Summary
I'm facing a Fastlane Error when I build the project using the command eas build.
The error logs are:

React Native: 0.71.3
Expo: 48.0.4
Managed or bare?
Managed
Environment
npx: installed 2 in 2.877s
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.1
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 14.20.0 - ~/.nvm/versions/node/v14.20.0/bin/node
npm: 6.14.17 - ~/.nvm/versions/node/v14.20.0/bin/npm
Managers:
CocoaPods: 1.12.0 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
IDEs:
Android Studio: 2022.1 AI-221.6008.13.2211.9619390
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
npmGlobalPackages:
eas-cli: 3.7.2
expo-cli: 6.3.2
✖ Dependency tree validation for expo-modules-autolinking failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @expo/config-plugins failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @expo/prebuild-config failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @unimodules/core failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @unimodules/react-native-adapter failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for react-native-unimodules failed. This validation is only available on Node 16+ / npm 8.
🎉 Didn't find any issues with the project!
Error output
No response
Reproducible demo or steps to reproduce from a blank project
"scripts": {
"start": "expo start --dev-client",
"android": "expo run:android",
"ios": "expo run:ios",
"web": "expo start --web",
"eject": "expo eject",
"postinstall": "patch-package"
},
"dependencies": {
"@expo-google-fonts/inter": "^0.2.2",
"@react-native-async-storage/async-storage": "1.17.11",
"@react-navigation/bottom-tabs": "^6.5.6",
"@react-navigation/native": "^6.1.6",
"@react-navigation/native-stack": "^6.9.12",
"axios": "^1.2.6",
"deprecated-react-native-prop-types": "^2.2.0",
"expo": "~48.0.4",
"expo-build-properties": "~0.5.1",
"expo-device": "~5.2.1",
"expo-file-system": "~15.2.2",
"expo-font": "~11.1.1",
"expo-image-picker": "~14.1.1",
"expo-localization": "~14.1.1",
"expo-location": "~15.1.1",
"expo-network": "~5.2.1",
"expo-notifications": "~0.18.1",
"expo-splash-screen": "~0.18.1",
"expo-status-bar": "~1.4.4",
"expo-updates": "~0.16.3",
"lottie-react-native": "5.1.4",
"moment": "^2.29.3",
"patch-package": "^6.5.1",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.71.3",
"react-native-awesome-alerts": "^2.0.0",
"react-native-calendars": "^1.1284.0",
"react-native-check-box": "^2.1.7",
"react-native-crypto-js": "^1.0.0",
"react-native-dotenv": "^3.4.7",
"react-native-gesture-handler": "~2.9.0",
"react-native-maps": "1.3.2",
"react-native-progress": "^5.0.0",
"react-native-reanimated": "~2.14.4",
"react-native-safe-area-context": "4.5.0",
"react-native-safe-area-view": "^1.1.1",
"react-native-screens": "~3.20.0",
"react-native-star-rating": "^1.1.0",
"react-native-svg": "13.4.0",
"react-native-use-keyboard-height": "^0.1.1",
"react-native-webview": "11.26.0"
},
"devDependencies": {
"@babel/core": "^7.20.0",
"@types/react": "~18.0.27",
"@types/react-native": "~0.70.6",
"typescript": "^4.9.4"
}


[master] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

/cc we don't use Prow
/assign we don't use Prow

Codecov Report

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

@@           Coverage Diff           @@
##           master     #125   +/-   ##
=======================================
  Coverage   96.18%   96.18%
=======================================
  Files          16       16
  Lines         446      446
=======================================
  Hits          429      429
  Misses         15       15
  Partials        2        2

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d78c578...7d5f176. Read the comment docs.

lint failed with #126


【代码迁移】任务 20-2：A-Causal-U-net-based-Neural-Beamforming-Network

原论文代码运行结果：

迁移代码运行结果：

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


How can i use Metro4 with npm and Vuejs?

After NPM install Metro4... what the best aproach to use Metro4 (styles and javascript) in my project?

You better ask this question on stackoverflow.

I have successfully integrated Metro UI 4 to my Vue project, very easy.
npm install metro4@latest
Then import it to the webpack entry
import 'metro4';
import 'metro4/build/css/metro-all.min.css'

Finally, follow the author's guide:
How to use Metro 4 with VueJS framework.


v3.0.0 regression: TypeScript mixins broken in v3.0.0, working fine in rc7

Describe the bug
Hey @Akryum I know you how much you love  TypeScript typing issues, so I just know you'll love this one! 🤪
When using TypeScript Vue component after upgrading vue-apollo v3.0.0-rc7 to v3.0.0, mixins no longer compile. Typed mixins can be done with vue-typed-mixins or the using the mixins helper from Vuetify. I confirmed this by switching back to rc7 on a clean repository folder, building (works fine), then another clean repo folder with v3.0.0 and receive this error:
ERROR in /Users/bbugh/somewhere/SomeComponent.vue
ERROR in /Users/bbugh/somewhere/SomeComponent.vue(25,46):
TS2769: No overload matches this call.
  The last overload gave the following error.
    Argument of type '{ name: string; components: { PageForm: { name: string; components: { DeleteButton: any; ItemFormHeader: any; ItemSelector: any; FormImageUploader: any; FormSaveButton: any; FormItemSelect: any; }; ... 6 more ...; apollo: { ...; }; }; }; computed: { ...; }; methods: { ...; }; }' is not assignable to parameter of type 'ComponentOptions<{ currentProject: any; } & { respondWith(resource: { id: string; }, errors?: any[], message?: string, routeOptions?: RespondWithOptions): void; pushReturnTo({ hash, fallback }: { hash: string | null; fallback?: string | undefined; }): void; } & Record<...> & { ...; } & Vue, ... 4 more ..., Record<.....'.
      Types of property 'components' are incompatible.
        Type '{ PageForm: { name: string; components: { DeleteButton: any; ItemFormHeader: any; ItemSelector: any; FormImageUploader: any; FormSaveButton: any; FormItemSelect: any; }; mixins: any[]; ... 5 more ...; apollo: { ...; }; }; }' is not assignable to type '{ [key: string]: VueConstructor<Vue> | FunctionalComponentOptions<any, PropsDefinition<any>> | ComponentOptions<never, any, any, any, any, Record<string, any>> | AsyncComponentPromise<any, any, any, any> | AsyncComponentFactory<...>; }'.
          Property 'PageForm' is incompatible with index signature.
            Type '{ name: string; components: { DeleteButton: any; ItemFormHeader: any; ItemSelector: any; FormImageUploader: any; FormSaveButton: any; FormItemSelect: any; }; mixins: any[]; props: { project: { ...; }; ... 4 more ...; preservePhoto: { ...; }; }; ... 4 more ...; apollo: { ...; }; }' is not assignable to type 'VueConstructor<Vue> | FunctionalComponentOptions<any, PropsDefinition<any>> | ComponentOptions<never, any, any, any, any, Record<string, any>> | AsyncComponentPromise<any, any, any, any> | AsyncComponentFactory<...>'.
              Type '{ name: string; components: { DeleteButton: any; ItemFormHeader: any; ItemSelector: any; FormImageUploader: any; FormSaveButton: any; FormItemSelect: any; }; mixins: any[]; props: { project: { ...; }; ... 4 more ...; preservePhoto: { ...; }; }; ... 4 more ...; apollo: { ...; }; }' is not assignable to type 'ComponentOptions<never, any, any, any, any, Record<string, any>>'.
                Types of property 'apollo' are incompatible.
                  Type '{ item: { query: typeof import("*.gql"); skip(): any; variables(): any; update({ item }: { item: any; }): any; }; item: { query: any; variables(): any; skip(): any; update({ item }: { item: any; }): any; }; tracking: any; schedules: typeof import("*.gql"); }' is not assignable to type 'VueApolloComponentOptions<never>'.
                    Type '{ item: { query: typeof import("*.gql"); skip(): any; variables(): any; update({ item }: { item: any; }): any; }; item: { query: any; variables(): any; skip(): any; update({ item }: { item: any; }): any; }; tracking: any; schedules: typeof import("*.gql"); }' is not assignable to type 'PrivateVueApolloComponentOptions'.
                      Property 'item' is incompatible with index signature.
                        Type '{ query: typeof import("*.gql"); skip(): any; variables(): any; update({ item }: { item: any; }): any; }' is not assignable to type 'string | boolean | DocumentNode | WatchLoading | ErrorHandler | VueApolloQueryDefinition<any, OperationVariables> | Partial<VueApolloQueryDefinition<any, OperationVariables>> | VueApolloSubscriptionDefinition<...> | { ...; } | (() => VueApolloQueryDefinition<...> | null) | undefined'.
                          Type '{ query: typeof import("*.gql"); skip(): any; variables(): any; update({ item }: { item: any; }): any; }' is not assignable to type '{ [key: string]: VueApolloSubscriptionDefinition<OperationVariables>; }'.
                            Property 'query' is incompatible with index signature.
                              Property 'query' is missing in type 'typeof import("*.gql")' but required in type 'VueApolloSubscriptionDefinition<OperationVariables>'.

ERROR in /Users/bbugh/somewhere/SomeComponent.vue
ERROR in /Users/bbugh/somewhere/SomeComponent.vue(39,35):
TS2339: Property 'params' does not exist on type 'ComputedOptions<any> | (() => any)'.
  Property 'params' does not exist on type 'ComputedOptions<any>'.

To Reproduce
Use mixins with v3.0.0. Here's an example component that builds fine with 3.0.0-rc7, but breaks when the only change is to upgrade to 3.0.0:
<script lang="ts">
import mixins from 'vue-typed-mixins'
import ProjectSubview from '...' // this is the mixin
import { itemCreateMutationOptions } from '...'

export default mixins(ProjectSubview).extend({
  name: 'SomeComponent',
  computed: {
    itemId () {
      return parseInt(this.$route.params.itemId)
    }
  },
  methods: {
    onSubmit (item: Item) {
      return this.$apollo
        // currentProject comes from ProjectSubview, breaks in v3.0.0
        .mutate(itemCreateMutationOptions(item, this.currentProject.id))
        .then(({ data: { itemCreate: { item, errors } } }) => {
          // respondWith comes from from ProjectSubview, breaks in v3.0.0
          this.respondWith(item, errors, 'Item created!', { hash: 'item' })
        })
    }
  }
})
</script>

Expected behavior
Mixins should work correctly in v3.0.0.
Versions
These are the versions as of the repository tag v3.0.0 (c36e334)
vue<EMAIL_ADDRESS>vue-apollo<EMAIL_ADDRESS>apollo-client<EMAIL_ADDRESS>Additional context
Add any other context about the problem here.

Has this been resolved? I can't use the apollo mixin on my components without TS complaining

It hasn't been for me. I had to roll back the upgrade to 3.0.0 and stuck with rc7, unfortunately.


Using hsmm.backward_estimation() as starting point for LOOCV might be biased

Possible problem:
The estimates from hsmm.backward_estimation() are based on the data from all subjects and thus contain information about the data that is omitted purposefully during LOOCV (i.e., the held-out data from a single subject). Since the estimate recovered by the EM, also used during the LOOCV, depends on the starting value the estimate might also end up being biased towards the solution that worked for all subjects.
Proposed solution:
Move the backward estimation into the LOOCV procedure and calculate a backward estimate for each fold (i.e. the remaining data after excluding one subject). Then use those for the remainder of the LOOCV procedure.
This does appear to affect the results from tutorial 3:
Here the original approach:

And here the proposed alternative:

See c5aa379 for possible implementation of proposed solution.

This does make a lot of sense and should be the default behavior of LOOCV (if not the only one). Additionally the new LOOCV profile of Tutorial 3 looks more credible as higher number of bumps get more punished.
I see two solutions for the problem:

Use your implementation and rely on the backward estimation
Optimize the starting points search independently of other solutions

Solution 1. has one potentially big downside is that the computation time will take much longer even more given that the __loocv_backwards function doesn't benefit from the parallelization. I have no clue how to use paralellization efficiently in that case, my guess is that we cannot distribute everything so we have to choose whether to parallelize over subjects or over n_bumps. I guess it is still better to parallelize over subjects as you are doing it. In the current state it would be useful to know whether computation time is still in an acceptable range for usual applications.
Solution 2. Would be faster but might not be as good to find the optimal set of starting points and would be hardly tractable so I guess it is not advised
Can you test for time difference between both methods?

Considering efficiency:
In the proposed solution the increase in complexity should be approximately linear in the number of subjects. In the current implementation we have to call backward_estimation() once and benefit from the parallelization over bumps. Then we call loocv_mp() and benefit from the parallelization over subjects. In the proposed solution we essentially call backward_estimation() not once but as many times as we have subjects, but in every call we still benefit from the parallelization over bumps. Since these calls to backward_estimation() via __loocv_backwards() still happen before the original parallelized loop in loocv_mp(), the actual LOOCV procedure should remain unaffected and should thus take the same time.
In tutorial 3 there are only 4 subjects but up to six bumps, so I think here this is efficient. However, with more subjects it might actually become more efficient to parallelize over subjects and then essentially call backward_estimation(cpus=1) for every subject (but that is currently not supported I think?).
In that case we should maybe replace:
if bests is None:

        for p in participants:
            if verbose:
                print(f'Estimating LOOCV backwards solutions for participant {p}')

            best_est_p = __loocv_backwards(unstacked_data, p, init.sf, init.bump_width, cpus, max_starting_points)
            bests_est.append(best_est_p)

with:
if bests is None:

        with multiprocessing.Pool(processes=cpus) as pool:
            bests_est = pool.starmap(__loocv_backwards,
                zip(itertools.repeat(unstacked_data), participants,
                    itertools.repeat(init.sf), itertools.repeat(init.bump_width),
                    itertools.repeat(1), # Make sure that cpus is 1 for every call to __loocv_backwards()
                    itertools.repeat(max_starting_points)))

Here the time data:
In tutorial 3 the call to backward_estimation() for all data reports a wall time of 14.3 seconds on my machine. The loocv_mp() call using these estimates as starting values reports 14.2 seconds.
Calling loocv_mp() with bests=None to obtain backward estimates per fold takes 1 min and 8 secs - which would indeed suggest that the increase is approximately linear in the number of subjects.
I do like the idea of maybe finding an alternative way to optimize the starting points. Maybe backward_estimation() can be adjusted to not drop every other bump to recover the next bump-1 solution? I don't have a good idea yet how this selection could be made smarter but depending on the number of bumps which can be ignored this might speed things up. That would reflect a mixture of options 1 & 2. :-)

One thing I was just thinking about: can't we just estimate the max nr of bumps, and then for estimations with lower nrs of bumps pick the top X most likely ones?

@JoKra1 I don't understand your last suggestion
@jelmerborst It is easy to do and might be good to inspect other possible solution but I can't see yet how it addresses the problem raised by Joshua

Also as a general comment on the problem: With only 4 participants the weight of each on the starting point is very big so LOOCV will differ highly between the two methods, with larger groups it shouldn't be so much of a trouble although I think that larger number of bumps will be more penalized which is a good thing as this is expected when overfitting

I am working on a new version to find all possible numbers of bumps that also happens to work ~ 10 times faster than backward_estimation but it will imply slightly rewriting the LOOCV function so I keep you posted

This is fixed with #102


Data loss due to packet receive errors (MemErrors)

SC4S version: 3.31.0
Host OS: Ubuntu 22.04.4 LTS (Jammy Jellyfish)
Runtime: Docker + systemd

Hello,
I've been having issues related to dropped packets at a buffer level (fortinet_fortios over UDP). Only some data is lost (around 10% loss) and there are no dropped events by sc4s nor custom filters or parsers in place.
After increasing the default parameters like so (following this issue) to be safe:
net.core.rmem_default = 536870912
net.core.rmem_max = 536870912
SC4S_SOURCE_UDP_SO_RCVBUFF=536870912

I've managed to suppress all buffer errors completely. However, I'm still missing events at a rate of aprox. 1000 events per minute (compared to a setup for the same raw data deployed as HF+syslog-ng). Netstat shows the next output:
root@myserver:~# netstat -anus
[...]
Udp:
    6834146 packets received
    287775 packets to unknown port received
    1945378 packet receive errors
    1305 packets sent
    0 receive buffer errors
    0 send buffer errors
    MemErrors: 1945378
[...]

Be aware that the number of receive errors correspond exactly to the number of MemErrors. I'm wondering how can I fix this issue. I've also tried raising the number of workers from 4 to 8, unsuccessfully.
Thank you for your support.

Congrats for work so far!
If neither netstat nor metrics show drops anymore this will require a support call to check the env and investigate. Please open a support case


Always write out nested types tables

Remove the option to switch off nested types tables. In a world where
re-entrant direct lookup will cause deserialization to fail (or worse),
diabling these tables will only lead to further instability in the
compiler.

@swift-ci test

@swift-ci test source compatiblity

@swift-ci test source compatibility

I am going to kill macOS run to unblock testing master-rebranch merge

Build failed
Swift Test OS X Platform
Git Sha - 53b368b34fc0653fb09796b7f0cd605ae06a2393

Build failed
Swift Test Linux Platform
Git Sha - 53b368b34fc0653fb09796b7f0cd605ae06a2393

@swift-ci test

⛵


Update request: matrix-synapse 1.110.0 → matrix-synapse 1.112.0

Package name: matrix-synapse
Latest released version: v1.112.0

Current version on the unstable channel: 1.111.0
Current version on the stable/release channel: 1.111.0

[x] Checked the nixpkgs pull requests

Notify maintainers
@Ma27
@mguentner
@dali99
@sumnerevans
@NickCao
@teutat3s

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

They released 1.112.0 very quickly after 1.111.1, so I changed the issue.


Remove obsolete PathFilter class

Codecov Report

Merging #2367 into master will increase coverage by 0.04%.
The diff coverage is 50%.

@@             Coverage Diff             @@
##             master   #2367      +/-   ##
===========================================
+ Coverage     82.85%   82.9%   +0.04%
+ Complexity     2160    2153       -7
===========================================
  Files           352     351       -1
  Lines          6067    6054      -13
  Branches       1111    1106       -5
===========================================
- Hits           5027    5019       -8
+ Misses          469     466       -3
+ Partials        571     569       -2

Impacted Files
Coverage Δ
Complexity Δ

.../gitlab/arturbosch/detekt/cli/console/Colorizer.kt
76.92% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ain/kotlin/io/gitlab/arturbosch/detekt/cli/Junk.kt
33.33% <100%> (+13.33%)
0 <0> (ø)
:arrow_down:

...itlab/arturbosch/detekt/api/internal/Validation.kt
33.33% <0%> (-16.67%)
0% <0%> (ø)

...b/arturbosch/detekt/api/internal/DetektPomModel.kt
66.66% <0%> (-8.34%)
5% <0%> (ø)

...osch/detekt/api/internal/KotlinEnvironmentUtils.kt
84.9% <0%> (-1.37%)
0% <0%> (ø)

...gitlab/arturbosch/detekt/cli/runners/AstPrinter.kt
100% <0%> (ø)
4% <0%> (ø)
:arrow_down:

...ch/detekt/api/internal/ValidatableConfiguration.kt
100% <0%> (ø)
0% <0%> (ø)
:arrow_down:

...tlin/io/gitlab/arturbosch/detekt/cli/ReportPath.kt
100% <0%> (ø)
1% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0bbd0ab...9056db0. Read the comment docs.


Docs: create new source

Some documentation or wiki entries on creating new source it needed
For example, I use @liquidz 's awesome plugin for clojure development 'vim-iced' and it has omnifunc. Here is omnifunc is supported by default in nvim-compe, or a source needed be created.
Also I see he create custom source for  coc source and asyncomplete. How can I create and port these sources using nvim-compe.
This something the wiki should answer

OK.
I will add the documentation for it.

Hey @hrsh7th any updates on this? thanks

Sorry for delay.
I've created wiki page. Could you see it?

@hrsh7th That's okay, I'm checking it out right now

@hrsh7th i think the example code has an issue, I copied it to test.vim and source it, but I got all kind of errors. I also tried to add it to plugin/ dir but same erros
Error detected while processing /home/tami/repos/nvim/plugin/month.vim:
line    1:
E700: Unknown function: s:get_metadata
E700: Unknown function: s:datermine
E700: Unknown function: s:complete
Error detected while processing function compe#source#vim_bridge#register:
line    4:
E5108: Error executing lua Vim(return):E15: Invalid expression: s:sources[a:id].get_metadata()

It would be awesome if both lua and vim examples are operational as it would help users quickly test things out in there env.
Could you please fix the code examples to a working ones. I hope I'm not asking a lot. Thanks

Sorry. I've updated it.
I'm happy if you update the wiki entry.

Nice I will check it out, @hrsh7th I don't think I can edit the wiki, is it open for anyone to edit? or must I clone it? check permissions

Yes, I tested the viml version and it worked right a way.
How about after you give me permissions to edit the wiki, I add general Q/A under "creating new source" section and you would later answer them?

I've updated wiki permission.,Thak you!

@hrsh7th check it out, I added some todos and a question, also reword introduction, hope you like it

Thank you.
Feel free to update it.

I will check the todos and add explain for it.


[FEA]Support HiveTableScanExec to scan a Hive text table

I wish we can support HiveTableScanExec to scan a Hive text table.
Say you already created a Hive text table using the code in https://github.com/NVIDIA/spark-rapids/issues/6419, then query it
spark.sql("select * from test_hive_text_table").collect

Not-supported-messages:
! <HiveTableScanExec> cannot run on GPU because GPU does not currently support the operator class org.apache.spark.sql.hive.execution.HiveTableScanExec

A couple of questions for clarification:

What is the priority of data types to be supported for Hive's text file-format? Specifically, are non-primitive types (e.g. ARRAY, STRUCT, MAP) an immediate priority?
Are custom field / row delimiters important for the first cut? Hive (and likely Spark) support overriding the delimiter specs, such that CSV might well be a subset of the default  Hive text serialization format.

(I'm having a little trouble locating the official documentation for the following.)
The default Hive text serialization format uses LazySimpleSerde, with \n as the record delimiter, and a series of single-byte field delimiters, beginning with ^A:

First level field delimiter:  ^A, i.e. \u0001.
Second level field delimiter: ^B, i.e. \u0002. (E.g. Array element separator for top-level arrays.)
Third level field delimiter:  ^C, i.e. \u0003. (E.g. Array element separator for ARRAY<ARRAY> elements, or key-value separators in top-level maps.)
Et cetera.

Consider the following table schema:
CREATE TABLE f1_team(
  name STRING,
  drivers ARRAY<STRING>,
  top_positions <STRING, INT>)
STORED AS TEXTFILE...

Consider the following records in said table:
{ "Mercedes", [ "Hamilton", "Russell" ], [ "Spa":4, "Monza":3, "MarinaBay":9 ] },
{ "RedBull",  [ "Verstappen", "Perez" ], [ "Spa":1, "Monza":1, "MarinaBay":1 ] }

By default, the Hive text format will serialize these records (in Hive and Spark) as follows:
Mercedes^AHamilton^BRussell^ASpa^C4^BMonza^C3^BMarinaBay^C9\n
RedBull^AVerstappen^BPerez^ASpa^C1^BMonza^C1^BMarinaBay^C1\n

A couple of notes regarding the CSV reader in libcudf as it currently stands:

There is no support for nested types. No LIST (ARRAY), no STRUCT. Certainly no MAP.
The field delimiter is configurable via csv_reader_options::set_delimiter(). Setting this to \u0001 might provide some semblance of the Hive default text serialization format.
read_csv() does column type inference via heuristics. This may be overridden with an explicit type schema (via _dtypes), but nested types aren't supported.

Using the existing CSV reader to support Hive's text serialization format will prove limited in scope. I'm still investigating.

A couple of questions for clarification:
1. What is the priority of data types to be supported for Hive's text file-format? Specifically, are non-primitive types (e.g. `ARRAY`, `STRUCT`, `MAP`) an immediate priority?

Complex types are lower priority than primitive types.

2. Are custom field / row delimiters important for the first cut? Hive (and likely Spark) support overriding the delimiter specs, such that CSV might well be a subset of the default  Hive text serialization format.

Custom field delimiters are not priority for the first cut.

This issue is partially addressed by the following PR:
https://github.com/NVIDIA/spark-rapids/pull/7013
In the 22.12 release, there is support for default Hive text tables (i.e. ^A separated fields, newline separated records, \\ for escapes).
This also has support for partitioned Hive text tables.
The following are not supported:

Custom delimiters (i.e. other than ^A with newlines).
Complex datatypes like STRUCT, ARRAY, MAP, BINARY.

Additionally, there are some deviations from the behaviour of Hive's LazySimpleSerDe:

NVIDIA/spark-rapids/issues/7068
NVIDIA/spark-rapids/issues/7069
NVIDIA/spark-rapids/issues/7085
NVIDIA/spark-rapids/issues/7086

The GPU reader should still be safe to use, if the conditions described above do not occur in the input data.

This issue should be safe to close now. The pending items are as follows:

Support for complex types (ARRAY, STRUCT, MAP, BINARY).
Support for escape characters.
Support for custom row/column delimiters, custom escape characters, etc.

This issue captures reading primitive types, with default table settings. We can pursue the remainder in separate issues, whenever they are prioritized.


Fingerprint of my browser to fingerprint-suite

Do you have any tools/scripts to get the fingerprints of my own browser so I can use it for fingerprint-suite?
I know I can do it manually by changing every values of the generated fingerprint but I'm hoping you guys have an automated way of doing this? Any help would be appreciated.

Hi @steinpigs and thank you for your interest in our project!
Unfortunately, the fingerprint collection script is a part of our proprietary codebase, so I cannot share the exact implementation. In addition to that, we don't collect our data in the same format the fingerprints are generated, so if would be of little use.
However - the entire idea is a client-side JS script that simply reads all the required properties via the Web APIs in your browser. I think it's a matter of minutes to write such a client-side script that collects the navigator properties, for example. You can basically walk an existing fingerprint generated from our library and have it access the properties in your window.navigator object, something along these lines:
// the generated fingerprint will help us to keep the structure the same
const generatedFingerprint = {
    "navigator": {
        "userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36",
        "platform": "Win32",
        "deviceMemory": 8,
        "hardwareConcurrency": 4,
        "maxTouchPoints": 0,
        "product": "Gecko",
        "productSub": "20030107",
        ...
    }
};

const myFingerprint = {navigator: {}};
Object.keys(generatedFingerprint.navigator).forEach(key => {
    myFingerprint.navigator[key] = window.navigator[key] // here you read the actual value to your object
})

The object myFingerprint.navigator should then contain your "navigator" fingerprint.
I will close this issue now as wontfix, since hopefully, this shows enough for you to help you with your use case. Nonetheless, feel free to ask any additional questions even after this. Thanks! :)


Yatin: Watch yoursanswer.com

Yatin requests the watch of the watch_keyword yoursanswer\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

yoursanswer\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


update django-nose

@wedaly @macdiesel @symbolist @muzaffaryousaf Please have a look. Thanks

:+1:


Added dummy first argument to all CmdLineOpts

This fixes Issue #41.

Thanks! We don't need to pass a core to DPDK. AFAIK that's for their "lcore"/"lcore remote launch" features which we don't use. In this case it's fine if DPDK prints an error message.

Keeping "-c 0x0" rather than "-c 0x1" breaks the tests for me. Do they work for you?
For me, DPDK prints an error message, followed by Usage, followed by an EAL FATAL error, and stops.
I think we have two choices:

"-c 0x1". I tested this and it works.
Removing the "-c 0x0" option altogether since we don't use this feature.


Sum of n natural numbers

Thank you for contributing to Algorithms/javascript, your pr got merged! ✨


[TEST]:Review my portfolio

Thanks for making issue, now you can close issue

Thanks for making issue, now you can close issue


Does this tool handle aarch64 binaries?

Does your dataset include firmware for ARMv8 processors? and if there is, how it performed on them?
I'm asking this question because the addressing mechanism in aarch64 binaries is different where the program counter register no longer exists instead there are address pages.
when I was testing angr against handcrafted programs based on aarch64 binaries, it couldn't construct a proper CFG and DDG and.

Hi, karonte is based on angr, and it does support aarch64. However, if you
are experiencing some issues with angr with some aarch64 binaries, you ll
experience similar problems with karonte too on the same binaries.
On Tue, Oct 27, 2020, 6:51 PM behnam<EMAIL_ADDRESS>wrote:

Does your dataset include firmware for ARMv8 processors? and if there is,
how it performed on them?
I'm asking this question because the addressing mechanism in aarch64
binaries is different where the program counter register no longer exists
instead there are address pages.
when I was testing angr against handcrafted programs based on aarch64
binaries, it couldn't construct a proper CFG and DDG and.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ucsb-seclab/karonte/issues/8, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH5GZAYTWI3XWCXNG6N5L3SM52J5ANCNFSM4TBVFOUQ
.


Tachiyomi apk

Source name
none
Source language
none
Describe your suggested feature
Can u upload the latest version of tachiyomi and tachiyomi preview apks if u have it, thanks.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I have updated the app to version 0.15.3.
[X] I will fill out all of the requested information in this form.

No


Followup #535.

This is a follow-up PR for #535. It makes InMemoryStorage.update_cache method private and adds unit tests for the method in tests/storage_tests/test_in_memory.py.

LGTM!


Biomes 'o Plenty is Incompatible, But Only on Servers

I'm hosting the server myself, but this same issue also occurs on, say, aternos.
The server has 8gb alloc. ram, 6gbminimum, (pc has 16gb total), intel i5 12th gen, rtx 2050, the 2nd pc im joining the server with is even better.
A modpack with just Biomes 'o Plenty (and terrablender) and the Changed Mod 0.13 will sometimes fail to load newly-generated chunks. Reloading the chunk by rejoining or by moving away and then coming back (i do this by tping) fixes it. reloading chunks with f3+a does not fix it. This  never occurs in singleplayer, only on servers. I can provide the server's log and other files upon request. See https://youtu.be/ZE2NwA0w3Pw for demonstration of the bug.
Apparently this only occurs with 0.13, earlier versions are fine.
Changed mod's config file's bottom three settings, fastandcheap as well as two other cache related configs, do not fix this when toggled.

After looking into this issue, I've determined the actual incompatibility is TerraBlender. I've had reports before about how TerraBlender was eating up all of a servers RAM.

I think you were actually right the whole time with the issue being terrablender. Although a modpack with just terrablender and other, non-biome mods in it, terrablender + any biome adding mod (i used terralith, which doesnt use terrablender) + changed produces this issue.
Strangely, removing changed resolves the terrablender issue, so I dont know what's up with that. It seems like something about terrablender + a biome adding mod + changed makes the server have a heart attack. I hope that this helps you narrow down the issue.
Also, I deleted some old, unused configs the server had, and the issue with biomes 'o plenty has changed a bit... Still is a problem though. Explained in the video. I get confused by my own minimap and lie at 2:03. More terrain DOES generate than before but its not that ocean. https://youtu.be/ZCQqRvudtm8?si=C3I0I_r5FqURdCVD

Perhaps the workaround/fix for this would be to scrap Changed's compatibility with Terrablender,as relatively no one utilizes purely the two together but rather some other,larger biome mods like BYG or BoP in the mix.Though it's also to note that this issue came around 0.13 instead,whereas in 0.12 and earlier it wouldn't have taken place at all.

I went to the mcmod site and found that people weren't that impressed with the mod （Terrablender）.

I quote this comment, "Folks, be aware that in version 1.18.2 if you're using a server that is cat or a-side using the MV Multi-Worlds plugin to generate worlds will result in a generated world that has no trees, no grass, no anything but squares (seems to be the case with all plugin+mod hybrids)."

Maybe the mechanics of the module should be looked into...


better multi-threading support

While encoding / decoding works fine in multi-threaded environments, one issue we found is that vertex / index codecs are using global variables for bitstream versioning, namely gEncodeVertexVersion and gEncodeIndexVersion. These variables are then used in the main encoding functions such as meshopt_encodeVertexBuffer or meshopt_encodeIndexBuffer which makes these calls harder to parallelize when an explicit bitstream version is requested via meshopt_encodeVertexVersion or meshopt_encodeIndexVersion. Currently, these functions can be called only once otherwise data races may occur (in a multi-threaded environment), which requires either explicit synchronization between threads or initialization before the threading starts which is often not feasible.
A simple solution would be to provide new overloads for meshopt_encodeVertexBuffer or meshopt_encodeIndexBuffer that would take the version as an input which would remove all dependencies on the shared global variables.

The intent here is that you really don't need to change these except for once at startup, just like the memory allocation function.

... in fact it's really time to change the defaults so that you just don't need to call these functions in general unless the application is doing something incredibly specific.

I understand the intent but in practice it complicates deployment on multi-threaded systems where the initialization step is pretty much independent on the worker threads. If the initialization happens when the workers are already running an explicit synchronization is needed. Of course the situation is solvable but it just unnecessarily complicates things and it is bug prone because it is not immediately obvious from the API point of view that it can lead to data races (the only reason we found out was TSAN).
As for us, we actually want to be able to lock the bitstream on a specific version so even when the library gets updated it doesn't change what the encoders produce (because decoders are deployed in environments where they can't be updated that easily). I can even imagine that we may want in future produce different bitstream versions at the same time (e.g. for different clients devices) which would be actually impractical with the current design (in a multi-threaded environment, we would have to basically put a mutex around the entire meshopt_encodeVertexBuffer function).

Can you explain why it's impractical to call the function exactly once before any worker threads start? That, again, was the original intent.

It's mostly about the overall architecture of the system. Basically the worker threads are calling libraries that call other libraries and so on. Meshoptimizer is integrated in a very deep layer of this system and the scheduler that runs the worker threads doesn't know anything about it and most of the libraries in between don't really have any initialization API to begin with. We can't even put meshoptimizer initialization directly to the scheduler (which would be a rather poor solution anyway) because the library where meshoptimizer lives is already initializing it and it would overwrite the previous initialization. All this could be solved on our end by refactoring of the system but frankly that is not really feasible, especially when other, much easier, solutions are available (which includes explicit synchronization but all I'm saying is that it would be much easier if we didn't have to do that).

If this is in C++, would it be possible to simply set the version before the call once? eg using C++11's safe statics:
static int once = (meshopt_encodeVertexVersion(1), 0);

I'm basically trying to reconcile:

it should be easy to specify a single fixed version of the encoding in the app
while it's indeed a problem if you want to encode multiple versions, right now there's no valid use case to encode multiple versions in the same app (IMO) - simply using the fixed latest version should work just fine. This may change if the new versions are being added, but we could simply wait until then to introduce different APIs and I'd rather have this as an actual use case that exists in production to act on this
at the same time, of course it's not that big of a deal to simply add two more APIs

Here's the original decision framework for this btw (early 2020): https://gist.github.com/zeux/ace5c2372ab05d8e1590a824120f36cf


Any plan to support Windows 10?

We really like this sketch plugin. However we notice it keeps crashing on Win 10. Any ideas on how to fix it? Or do any plan for Win 10 support.

@fsundjaja, thank you for reporting this issue.
This repo is part of our legacy code base and is no longer supported/maintained by us. You are welcome to create/publish a fork to npm or do what you want with the code.
Apologies for any inconvenience.


Unicode problem in understudied-languages.bib

Mulder, Jean Gail. 1994. Ergativity in Coast Tsimshian (Sm’algy̲x). Berkeley: Uni- versity of California Press.
There is an underlined a that does not come out as unicode.
@book{mulder94,
Address = {Berkeley},
Author = {Jean Gail {Mulder}},
Date-Added = {2019-06-25 23:33:03 -0500},
Date-Modified = {2019-06-25 23:33:03 -0500},
Publisher = {University of California Press},
Title = {Ergativity in {C}oast {T}simshian ({S}m'algy𝚊̲x)},
Year = {1994}}

This glyph is not available in the font Libertine, which is still in use in your book project. If you import the current class version from our langscibook repository, the switch to Libertinus should resolve the issue. The current Libertinus font has this font available.
There are two ways to print this glyph. One is "Latin lower a with macron below", the other "Latin lower a with line below".
Please note that I'm planning a push to Libertinus in mid-January to add missing glyphs and correct diacritics placement. If you find any further issues with the Libertinus font, could you open an issue in the langsci/langsci-libertinus repository?


[BUG] Azure sdk takes too long to report back disk status after attaching

Describe the bug
We are using azure sdk version "com.azure.resourcemanager:azure-resourcemanager:2.20.0" and it takes very long(upwards of 13 minutes) for the disk to be attached to a vm and the correct status to be returned on sdk. Although the disk is attached to vm when checked via the azure portal. This happens intermittently
Exception or Stack Trace
vmInfo.update().withExistingDataDisk(disk).apply();
To Reproduce
Create a new disk and attach it to an existing vm through sdk. The call above takes too long to be returned. The event on the vm is created within expected limits(a couple of seconds) but the same event doesn't reflect on the disk until after 10+ minutes.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

@XiaofeiCao Could you take a look? It might be an LRO, but 10+ minutes seems too long.

Any updates here?

It is about 34 seconds in my test. It is not super fast, but definitely in minutes.
Would you let us know what's specifical in your case? Code snippet if possible.
            // prepare resources
            var vm1 = azure
                    .virtualMachines()
                    .define(vmName)
                    .withRegion(region)
                    .withNewResourceGroup(rgName)
                    .withNewPrimaryNetwork("<IP_ADDRESS>/28")
                    .withPrimaryPrivateIPAddressDynamic()
                    .withoutPrimaryPublicIPAddress()
                    .withPopularLinuxImage(KnownLinuxVirtualMachineImage.UBUNTU_SERVER_18_04_LTS)
                    .withRootUsername("weidxu")
                    .withSsh(sshKey)
                    .withSize(VirtualMachineSizeTypes.STANDARD_B1S)
                    .create();

            var disk1 = azure.disks().define("datadisk1")
                    .withRegion(region)
                    .withExistingResourceGroup(rgName)
                    .withData()
                    .withSizeInGB(10)
                    .create();

            // do the update
            vm1 = azure.virtualMachines().getById(vm1.id());

            long nanoStart = System.nanoTime();

            vm1.update().withExistingDataDisk(disk1).apply();

            long nanoStop = System.nanoTime();

            System.out.println((double) (nanoStop - nanoStart) / 1E9);

output
34.8285229


Error Detect Lifecycle with Base builder version v0.2.26

What happened?
When using the version v.0.26 and above, the below error is getting reported in the Detect lifecycle phase when trying to build using the base builder.
Error:
======== Output<EMAIL_ADDRESS>========
pyproject.toml must include [tool.poetry.dependencies.python], see https://python-poetry.org/docs/pyproject/#dependencies-and-dev-dependencies
err<EMAIL_ADDRESS>(1)
======== Output<EMAIL_ADDRESS>========
pyproject.toml must include [tool.poetry.dependencies.python], see https://python-poetry.org/docs/pyproject/#dependencies-and-dev-dependencies
err<EMAIL_ADDRESS>(1)
ERROR: No buildpack groups passed detection.
ERROR: failed to detect: buildpack(s) failed with err
*This works fine when using the base builder version v0.2.25.
Below is the output when trying to use base builder version v0.2.25 in detect lifecycle phase
======== Output<EMAIL_ADDRESS>========
pyproject.toml must include [tool.poetry.dependencies.python], see https://python-poetry.org/docs/pyproject/#dependencies-and-dev-dependencies
err<EMAIL_ADDRESS>(1)
======== Output<EMAIL_ADDRESS>========
pyproject.toml must include [tool.poetry.dependencies.python], see https://python-poetry.org/docs/pyproject/#dependencies-and-dev-dependencies
err<EMAIL_ADDRESS>(1)
6 of 10 buildpacks participating
paketo-buildpacks/ca-certificates 3.1.0
paketo-buildpacks/node-engine     0.12.2
paketo-buildpacks/npm-install     0.8.0
paketo-buildpacks/node-module-bom 0.2.3
paketo-buildpacks/node-run-script 0.3.2
paketo-buildpacks/npm-start       0.8.0

What were you attempting to do?

Trying to build Node js angular application in the first phase using node js buildpack  and using Nginx build pack to create the final build in Tekton using lifecycle phases.
Build Configuration

What platform (pack, kpack, tekton buildpacks plugin, etc.) are you
using? Please include a version.

Tekton - v0.33.2 ( tekton-pipelines)
CNB Platform API version - 0.8

What buildpacks are you using? Please include versions.

Nodejs
Nginx

What builder are you using? If custom, can you provide the output from pack inspect-builder <builder>?

base builder

Can you provide a sample app or relevant configuration (buildpack.yml,
nginx.conf, etc.)?

project Structure
├── README.md
├── angular.json
├── cypress
├── cypress.json
├── karma.conf.js
├── local
├── mime.types
├── nginx-conf.template
├── node_modules
├── pa11yci
├── package-lock.json
├── package.json
├── proxy.conf.json
├── proxyssl.conf.json
├── sonar-project.properties
├── src
├── tsconfig.app.json
├── tsconfig.json
└── tsconfig.spec.json
The buildpacks uses the nodejs buildpacks to build the node app and then tekton step has a logic to re-name the nginx-conf.template to nginx.conf and then run the nginx buildpacks to create the final image.

This should be resolved by https://github.com/paketo-buildpacks/nodejs/releases/tag/v0.17.1.
That release is now available in the following builders:

https://github.com/paketo-buildpacks/full-builder/releases/tag/v0.2.38
https://github.com/paketo-buildpacks/base-builder/releases/tag/v0.2.30

Please let us know if you are still experiencing issues.


rbx_xml Implement Axes

Closes #89

Ran into a snag today -- this implementation is actually not quite right!
Roblox actually encodes the Axes type in a weird way:
<Axes name="Axes">
    <axes>7</axes>
</Axes>

I'll fix this on the master branch.


Adds back overclocking tests

Used pytest's parametrized tests to make it more clear

Imports are wrong, should be src.data.basicTypes for example so pytest . works in root directory. I tried pushing the change but not sure where it went

Nice, gh cli solved the problem

Ok that src. looks so weird to me. I can run the tests by pytest tests/test_overclocks.py in the project root without issues.

Sure, but tests are not meant to be run individually like that unless you are debugging/developing a particular test. The idea is to run the whole test suite using pytest . If you want to run an individual test you can do pytest -m tests/test_overclocks

I can pass all tests by running pytest . without src. on my side. Did you mean you can't do this on your machine? Maybe our pytest configs are different. I am just using the config out of box and version 8.1.1. Anyway this smells bad for me. src is only a directory, not a package.
However we can leave this issue behind for now, because I've noticed that the project is filled with src. imports. Removing them from tests is probably not enough. To remove them from everywhere, I guess project structure needs a fix. I will look into this later

Python has multiple valid ways to do imports, this is one of them. The imports are relative to the working directory of the caller, aka factory_graph.py in the root. We don't need to change it unless you want to turn it into a package - it would be wasted effort.


⚠ Bofrost.be has degraded performance

In 38aecd4, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1443 ms

Resolved: Bofrost.be performance has improved in 5832d15 after 50 minutes.


Derive Hash for Key

I was writing a quick console game, and I tried to make a HashMap<Key>. Unfortunately, Key doesn't derive Hash, though there's no reason why it can't.
Tiny PR, I know, but I think it's helpful and somebody had to add those 6 characters.

Makes sense.


Links not working in the pdf report file

Three links in the pdf file (report file) are not working (at the end of the document)

All the links should work now.


adding resources

Hello!, i wanted to add a couple of resources on both Youtube channeld ans Cyber security.

@lsomacruzl contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


require phpunit 7.1 via SYMFONY_PHPUNIT_VERSION env variable

Fixes https://github.com/symfony/demo/issues/811
When running the test suite on php 7.1 the wrong phpunit (non-maintained version 5) is required by the simple-phpunit-bridge which is not compatible with https://github.com/dmaicher/doctrine-test-bundle-demo.

Thanks for fixing this bug David.


feat: Merge feature discovery work into protected branch

Summary of Changes

Tests

Documentation

CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

@allisonsuarez let's merge into this protected branch


add theorems from Haitao and more

I started working in Haitao's "extras". There is a lot there!
@hthz, I will keep going over the next couple of change. I will send you notes about what I changed (mostly renaming, and stating theorems with iff instead of =). I have also cloned your repository, and I will make my version compatible with the changes I am making.
@leodemoura, note, I made algebra/function less reliant on function extensionality. For example, it is a lot more useful to say ∀x, f (g x) = x instead of f ∘ g = id. Similarly, in lists,
theorem map_id' {f : A → A} (H : ∀x, f x = x) : ∀ l : list A, map f l = l

is generally more useful than
theorem map_id : ∀ l : list A, map id l = l

if we are trying to avoid function extensionality.

@leodemoura, note, I made algebra/function less reliant on function extensionality. For example, it is a lot more useful to say ∀x, f (g x) = x instead of f ∘ g = id. Similarly, in lists,

I agree. This is a good change.


implement RGB bitmap loading

Current code only implements BGR loading per default, whatever the type of color expected as resulting image.

Completed via #39 completion. Still to be tested.


Use Amazon's newer built-in music slots for accuracy

A few months ago, Amazon extended their default built-in intents with some new music-related ones:
https://developer.amazon.com/public/solutions/alexa/alexa-skills-kit/docs/built-in-intent-ref/slot-type-reference#musicgroup
This pull request changes the intents, utterances, and lambda functions to use these instead. The accuracy in my experience with these slot types is much better.
Note that this also changes the behavior of the basic "play X" or "play X in the room" to assume it's an artist. Open to feedback on whether we want to do something different here, but given how it's easy to specify that you meant track/artist instead, and we'll get better accuracy by letting Amazon know what we're looking for, I think being more explicit is better.

Notable improvement, as accuracy has been a longstanding problem

This is great, but be aware that these new slots are only available in the US language (I.e. not UK or German).
Might change my language to US and try this out.

@roadz99 thanks for flagging that; #108 adds a note to the README to address that.

Nice!


Can't generate XLSX with a SQLite backend

Do the join on the SQL level instead of passing around lists of uids resulting in an IN query with a huuuuuge list.
The problems start in dump.py line 115.

Does not apply any more; reference the README and the command ftm export-excel :)


Prevent the possibility of an infinite while loop in calc_cpt_params

calc_cpt_params was unable to converge to a solution for some of the new CPT data, resulting in an infinite while loop.
As a quick fix, it now raises a ValueError if reaches 1e6 iterations, which takes about 2 or 3 seconds. I don't know how many iterations are usually required so I just set the limit to be very high.

Let me know what you think of the custom error name


UI wordwrap in "org-roam find"

Bug: Each entry in the org-roam-select prompt (Leader n f ) takes up two lines instead of one.
I was having a bit of weirdness on my Windows 10 machine (nvim 0.9.5), so I made a barebones nvim install with only 0.1.0 orgroam and 0.3.4 orgmode. Looked and functioned great! Also tried with the most up to date commit of both plugins (orgroam 45153562e7bfe806d84747d6518cad714c63ca2e, orgmode cc51c1914e3f0bf20bd543a7176df5bab12ec247). Still smooth!
So I ported over things from my personal nvim init.lua to the barebones config until I found the culprit. The setting that broke the UI: vim.opt.signcolumn = 'yes'
Here's a couple screenshots to clarify. The barebones install:

The barebones install with vim.opt.signcolumn = 'yes':

Anyway, just a small bug in an otherwise killer plugin. Your youtube video overview was super helpful in showcasing the features and workflow and I transitioned immediately from my system of scattered txt files. Thanks for sharing this plugin.

Thanks for the bug report and glad you like it!
This sounds like what https://github.com/chipsenkbeil/org-roam.nvim/pull/45 fixed, which is upstream of the 0.1.0 tag of this plugin.
If you think this fixes your issue, we can look at tagging a 0.1.1 release.

Oh wow, I must've not sync'd Lazy after updating init.lua with the latest commits. This totally fixes the issue. Big ups 👍


enhancement/extensibility + readme/ml_streaming

Reference Issues/PRs

add the ability to init PyMiloServer with ML model
fulfill readme with ML Streaming part

What does this implement/fix? Explain your changes.
Any other comments?

Dear Sepand, in this PR I've updated the README.md file and added the ML Streaming section to it, It would be great if you could help me enhance it to a great version. Feel free to apply your suggestions directly.
and Finally we can request review from Sadra on the final version.
@sepandhaghighi

Ready for your contribution
@sepandhaghighi


[SPARK-39959][BUILD][INFRA] Pin roxygen2 version to 7.2.0 in infra

What changes were proposed in this pull request?
Pin roxygen2 to 7.2.0 to make sparkr job work
Why are the changes needed?
R job failed due to checking for missing documentation entries
Does this PR introduce any user-facing change?
No
How was this patch tested?
All CI passed (lint/sparkr/pyspark)

The root reason of sparkr job failed should be roxygen2 7.2.0 --> 7.2.1
Docker cache not working (looks like is outdate for some reason) since 2 days before

https://www.diffchecker.com/TpOlQsg1 from results, it might related to change on github action docker config change.

Then do a real time build in each job, thus roxygen2 is upgraded in real time build job.

Solution: merge this if all CI passed (This will also do a cache refresh to make cache back again)

Awesome!!!!!

@dongjoon-hyun @HyukjinKwon Thanks, I do a local test in my repo all works well!
I also take a deep look on why cache not working: the ubuntu:20.04 hash changes before and after cache outdate. (FROM is a specific case in docker registry cache, it's not based on static text cache)
There might some improvement in followup:

https://github.com/apache/spark/pull/37402 Add separate image tag to help debug and recover CI if needed.
Pin to ubuntu:20.04 to static hash, and only change it when upgrade the hash when manully

Thanks @Yikun


Allow unlock for Chat option

Currently we only have Unlock for staking, or full unlock. We need to add an option for unlock for secure messaging too. The private keys are required in order to decrypt messages, so an encrypted wallet needs to be unlocked in order to send and receive messages.
Files and functions affected:
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/rpcwallet.cpp#L1590
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/wallet.h#L26
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/wallet.cpp#L184
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/walletdb.cpp#L15
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/qt/askpassphrasedialog.cpp
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/qt/forms/askpassphrasedialog.ui
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/qt/shadowbridge.cpp
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/qt/shadowgui.cpp
https://github.com/shadowproject/shadow/blob/v<IP_ADDRESS>/src/qt/walletmodel.cpp

Agreed.

@rynomster you can assign me to this issue.
I've fixed this tonight, will be pushing tomorrow.

fixed in #62


Add support for sendmmsg/recvmmsg

This PR aims to add support for the sendmmsg/recvmmsg syscalls.
The API exposed here is a bit simplified, where the "user friendly" functions don't expose the scatter/gather stuff (the _vectored variants found for recvmsg/sendmsg). This was not exposed to not blow up the API surface, while keeping the functionality using MmsgHdr(Mut) for advanced usages.
Thanks!

@Tuetuopay are you still interested in pursuing this functionality?

@Tuetuopay are you still interested in pursuing this functionality?

@xv-ian-c Hi! Thanks for the reminder. I completely forgot about this. Yes I still mean to get this through, whenever I get time to work on this :)


initialization and multifile directives

Consider the files bar.pl given by
:- include(foo).
:- multifile(foo/0).

foo :- write(bar), nl, halt.

and foo.pl given by
:- initialization(foo).
:- multifile(foo/0).

foo :- fail.

Running
$ tpl bar.pl

gives an error that goes away if the initialization directive is moved from foo.pl to bar.pl. The expected result is that the program works regardless where the initialization directive is located. See section <IP_ADDRESS> in the ISO Prolog standard.

Thank you for fixing it so quickly! The example code does work now. However, when include(foo) is replaced by ensure_loaded(foo), the error persists.
By ISO Prolog, the goals mentioned in initialization directives "shall be executed immediately after the Prolog text has been prepared for execution", and "[the] directive ensure-loaded(P-text) specifies that the Prolog text being prepared for execution shall include the Prolog text denoted by P-text". In other words, the processing of the initialization directive has to be deferred to after ensure_loaded as well.

I can confirm that it works now in the cases I tested. Thanks again for your hard work and this wonderful Prolog implementation. I think we can close this issue.


Roll Flutter Engine from f31988115453 to 9a6b6d85f180 (5 revisions)

https://github.com/flutter/engine/compare/f31988115453...9a6b6d85f180
2023-03-03<EMAIL_ADDRESS>[Impeller] Fix CanGenerateMipmaps (flutter/engine#40061)
2023-03-03<EMAIL_ADDRESS>Add new test font (flutter/engine#39809)
2023-03-03<EMAIL_ADDRESS>[Windows] Remove accessibility root ID assumption (flutter/engine#39994)
2023-03-03<EMAIL_ADDRESS>[Impeller] simplify text shaders by moving UV computation to contents (flutter/engine#39989)
2023-03-03<EMAIL_ADDRESS>Roll Skia from 274229be345c to 17451252b774 (1 revision) (flutter/engine#40058)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jsimmons@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Add Support for Snowflake Apache Iceberg tables

Snowflake has support for apache iceberg tables in private preview. It would be great if this was supported.

This issue can be closed. As it is solved in issue #172 and It is solved in the PR #138

@zvijayakumar https://github.com/dbt-labs/dbt-external-tables/pull/138 does not solve this please see https://github.com/dbt-labs/dbt-external-tables/issues/172#issuecomment-2083758876


[DNS] New section for Foundation DNS

PCX-7049

Think we can close this out as the underlying PCX ticket is closed


Kustomize common labels deprecated

When we run the kustomize procedure, we're getting some deprecation warning we should take care of.
# Warning: 'commonLabels' is deprecated. Please use 'labels' instead. Run 'kustomize edit fix' to update your Kustomization automatically.

Hi @squakez
I'd like to fix this. Can you please assign me this issue?


chore: bdd-spring-1580593818 to 0.0.1

chore: Promote bdd-spring-1580593818 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Syntax changes for interval syntax

Unifies the syntax for availability intervals. The distinction between bundle and port syntax is very simple:
bundle foo[N]: [G, G+1] 32

and
bundle bar: [G, G+1] 32

Also note that since we don't use the bundle parameter in the availability interval, we don't have to specify it. Additionally, this difference is consistent with port definitions in the signature as well.

We should try to merge this when all the tests are working with the IR flow


NOS-684 Convert ISPN indexing annotations to configuration in content-index

@jdcasey, seems the CI server was down.

retest this please


Is parsing working?

I was going to write my own solution, then I ended up here. It is exactly what I need, although I'm having issues with parse. I've taken the example from the doc:
  test("testing regent", () => {
    const json = {
      fooAndBar: {
        and: [
          {
            equals: ["@foo", "foo"],
          },
          {
            equals: ["@bar", "bar"],
          },
        ],
      },
    };

    const { fooAndBar } = parse(json);

    expect(fooAndBar({})).toEqual(false);
  });

regent.parse SyntaxError: Unexpected token o in JSON at position 1

TypeError: fooAndBar is not a function
     72|     const { fooAndBar } = parse(json);
     73|
     74|     expect(fooAndBar({})).toEqual(true);
       |           ^
     75|   });
     76| });

Clearly I'm doing something wrong, although I'm not sure why..

Ok my bad, I checked your tests and you use JSON.stringify(). This was not reflected in the doc (https://northwesternmutual.github.io/regent/#/?id=parse) hence my question 😉

Glad to hear you got it working. Was just about to comment 👍


Add hints for finding components or source files that cause warnings

I'm using create-react-app in development with react-a11y's setup in src/index.js. My developer console displays warnings as I expected, but unfortunately there are a lot of them and the stack traces only contain the line of code in react-a11y's source that fires warning, with no information on the components or source files that exhibit these warnings. This seems to be fixed if I set throw to true, though it halts my entire app and displays only one error at a time (at least on React 15) which is inconvenient for development.

Ideas

Produce stack traces in warnings (not just errors).
Display the names of React components containing errors (React does this for prop type validation) and/or the names of the tags. Line numbers would be even better but I'm not sure if this would be possible without generating stack traces or running code in VMs.
Set throw option to true by default. This would probably be the easiest solution to implement, but it's the most tedious to develop with on React 15 which only shows one error at once without boundaries.

For now adding { throw: true } to my test startup script seems to be an even more convenient workaround. Still, it would be nice to see multiple error sources in my app and not just its test suite.


Is isTypeOf required ? on builder.node - Relay Plugin

Typescript is yelling at me because isTypeOf on builder.node is required, so i looked at the codebase https://github.com/hayes/giraphql/blob/8787140f51d82247eb8a9c1804dacb5c8a5bc525/packages/plugin-relay/src/schema-builder.ts#L155 and it seems like the types are wrong in this case? because there is a default way to handle it if no isTypeOf is given.

The default resolve type only works if you use a class as the type param, or the shape associated with the type ref has a _type property that can be used to match again.
Something like:
builder.node(Some class, {... options}) or builder.node(builder.objectRef<{_type: 'SomeType'}>('SomeType'), {... options})
On a phone, so not sure how.ear that is.  If you are using one of these patterns, and still seeing type errors, some.more context on how you are calling the node function would be helpful

I'm at work right now, i can give a proper example in a few days. But i just tried your suggestion
builder.node(builder.objectRef<{ _type: 'SomeType'; id: string }>('SomeType'), {
	id: {
		resolve: (node) => node.id
	},
	fields: (t) => ({ id: t.exposeID('id') })
});

It's still yelling about isTypeOf is required.
If i create a class it goes away, but since my data usually is not represented in classes rather coming from prisma i don't know what the best way is to create nodes.
Also with the objectRef approach would i have to add _type to every object? Or am i misunderstanding something.

Sorry, small typo there, it should be __type, and yes, you would need to add the type to each instance of the node you resolve.
The issue isTypeOf solves is that when there is a field that resolves to the Node interface, graphql needs be able to figure out which type is actually being resolved.  If the node is being loaded through the default node or nodes queries we could determine what type the node is, but for custom fields that return nodes all we know is we got an object back and need to figure out what type it's supposed to be.  If it's an instance of a class, or the object has a property that tells us the type, we can create a default isTypeOf method that can use an instanceof check, or read the type property.  Lacking those, we don't have another way to figure out what the type should be, which is why it becomes required.
I've got a few ideas on how to make this better in the future, but currently you need to manually provide a way to resolve the type of a node.
In the mean time, I don't have a great solution for Prisma.  I know some people actually just add the graphql type into their db.  This is obviously not ideal.   There is a feature request out in Prisma to include the tabel/model name in query results.  This would make it trivial to write the isTypeOf functions.   Adding on the __type property manually is not perfect, but it might be the

@hayes That makes much more sense now, thank you! I will go ahead and close this issue for now.


cairo: Fix rectangle getter

This is a candidate for a clippy lint. If a getter/setter function is called almost like the field it is accessing then it's probably a mistake


Merge develop to Ct-DW

@aballway is added to the review. #Closed

@ms-jihua is added to the review. #Closed

More of an informative PR, plan to merge to CT-DW when CI build passes.

:shipit:


Fix this

Fix this rn
Traceback (most recent call last):
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 670, in urlopen
    httplib_response = self._make_request(
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 381, in _make_request
    self._validate_conn(conn)
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 978, in _validate_conn
    conn.connect()
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/connection.py", line 362, in connect
    self.sock = ssl_wrap_socket(
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/util/ssl_.py", line 386, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/data/data/com.termux/files/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/data/data/com.termux/files/usr/lib/python3.9/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/data/data/com.termux/files/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLEOFError: EOF occurred in violation of protocol (_ssl.c:1129)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/connectionpool.py", line 726, in urlopen
    retries = retries.increment(
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/urllib3/util/retry.py", line 446, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.proxyscrape.com', port=443): Max retries exceeded with url: /?request=displayproxies&proxytype=http&timeout=1500&ssl=yes (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/data/data/com.termux/files/home/nitro-generator/generator/main.py", line 47, in <module>
    scrape()
  File "/data/data/com.termux/files/home/nitro-generator/generator/main.py", line 30, in scrape
    r = requests.get('https://api.proxyscrape.com/?request=displayproxies&proxytype=http&timeout=1500&ssl=yes')
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/requests/sessions.py", line 530, in request
    resp = self.send(prep, **send_kwargs)
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/requests/sessions.py", line 643, in send
    r = adapter.send(request, **kwargs)
  File "/data/data/com.termux/files/usr/lib/python3.9/site-packages/requests/adapters.py", line 514, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='api.proxyscrape.com', port=443): Max retries exceeded with url: /?request=displayproxies&proxytype=http&timeout=1500&ssl=yes (Caused by SSLError(SSLEOFError(8, 'EOF occurred in violation of protocol (_ssl.c:1129)')))

:(

This error is only on termux (as far as i'm aware) so if you have a computer, use that. I would recommend linux subsystem for windows as this allows you to use bash.

i find you a little bit rude by coming here, not even knowing what's saying the error, and literally saying "fix this rn". But @unspecifiedhuman  answered right. Please be concious of your courtesy while opening an issue.


MB-7366 Review Service Items aria labelling refactor

Description
this branch resolves some critical a11y testing errors in the Review Service Items component(s). It moves aria labels to the Button component and adds empty alt text to icons in unstyled buttons to ensure their purpose is not read out twice by a screen reader. It also adjusts the form labeling on the rejection fields.
Reviewer Notes
cypress seems to dislike the htmlFor attribute, and reads it as a duplicated id, so I'll have to change the approach here if i see an integration test failure.
Setup
yarn storybook

http://localhost:6006/?path=/story/office-components-reviewserviceitems--basic
Code Review Verification Steps

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, IE, Edge).
[ ] Tested in the Experimental environment (for changes to containers, app startup, or connection to data stores)
[ ] User facing changes have been reviewed by design.
[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change
Buttons must have discernible text article explains more about the approach used.

Screenshots
no visual changes ~

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

Messages

:book:
:link: MB-7366

  Generated by :no_entry_sign: dangerJS against dd390bfa9a206f9274994e98c59304f1ea92b682


Index::len() reports how many files there are, not what is added to index

I'm not sure whether I understand all things correctly here, but from what I see, Index::len() reports the number of files that are in the working directory. Semantically, I would expect the number of files that are added to the index.
Maybe I am misunderstanding something.
What I basically try to do is to commit if the index contains files, if not do nothing. But I have no way of finding out whether the Index is empty or not... or at least I do not see one.

This currently corresponds to the git_index_entrycount function, so it may be not appropriately named perhaps?
As to what it's actually counting, that may be an issue for upstream libgit2 rather than here (as this is just delegating)

Yes, not properly named.
Anyways, from what I understand, git_index_entrycount should return the number of entries added to the index, so the number of git added paths, am I correct?
Because it does not, from what I see.

Hm perhaps that's a bug report for upstream libgit2 then?

This is how the git index works. The number of tracked files and the number of items in the index are the same number. The upstream bug was closed as a misunderstanding, so it looks like this bug can be closed the same way.

Oh awesome, thanks @carlosmn!


Support nested rules

It would be great if i could define nested rules for nested objects
const rules = {
    firstname: 'required',
    lastname: 'required',
    email: 'required|email',
    emailConfirm: 'required|same:email',
    payment: {
        selection: 'required'
    },
    company: {
        name: 'required',
        taxnumber: 'required'
    }
};

At the moment i had to write a helper function for that
const createValidator = (values, rules) => {
    const validator = new Validator(values, rules);
    validator.passes();
    return validator.errors.all();
};

const validate = values => {
    let errors = {};

    errors = createValidator(values, rules);
    errors.payment = createValidator(values.payment, rules.payment);
    errors.company = createValidator(values.company, rules.company);

    return errors;
};

Do you know if Laravel's Validator supports this?

It indeed does.
The same example as above in Laravel:
$this->validate($request, [
    'firstname' => 'required',
    'lastname' => 'required',
    'email' => 'required|email',
    'emailConfirm' => 'required|same:email',
    'payment.selection' => 'required',
    'company.name' => 'required',
    'company.taxnumber' => 'required'
]);

ok I will try and take a stab at this one.

Are there any updates on this? Not sure if you are working on that or should I use workaround or implement it on my own.

I haven't had time. Would love some help. :)

I added the support for nested rules in the PR #92.
Some basic tests also included. Check if it's fine and if could be included in the next version.
I would also recommend to rewrite library to ES6 code (or TypeScript), which improve readability and it's not difficult and time consuming task itself.

I'm open to using TypeScript. What do you think @garygreen?

I would suggest to go with ES6 rather than TypeScript. I personally haven't used TypeScript (haven't seen the need, though I'm sure it has some useful features), using it could further slow the development of validatorjs because it has a steeper learning curve and not as widely known as ES6, so would deter people to contribute to the library - which I think we should encourage.

@garygreen The advantage of using TypeScript would be to have type safe code which would help to eliminate some potential bugs at the compilation step without the need to write tests. TS is subset of Javascript so any valid JS code will still be valid TS code and if linter rules will not be too strict anyone could contribute with ES5/6 code.
Just for the record, I don't mind it to be ES6.

Probably just my ignorance of TypeScript on display there, I don't have any strong opinions either way -- it'll be a learning experience for me.

Anyway, this discussion should be moved to separate issue. I'm using this library in few project and will be glad to make some es6/typescript skeleton as reference for contribute over the weekend.

Going to move this to a separate issue. This issue is closed and released in 2.1.0


Fix PhysicsDirectSpaceState3D collide_shape return type

Use the PackedVector3Array return type for the 3D collide_shape method as that seems to be what it's actually returning.
I'm not sure if I should update the PhysicsDirectSpaceState3DExtension docs that reference "void*"? But I've updated PhysicsDirectSpaceState3D docs anyway.
I feel it was a find a replace error in https://github.com/godotengine/godot/pull/64009. Let me know if this is totally wrong!

Fixes: https://github.com/godotengine/godot/issues/73182

Looks good! Could you squash the commits? See PR workflow for instructions.

Thanks!


04/01/2018 14:53 : Create Pull Request for branch master -> prTesting1_2018040114

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Container bindMounts not documented

The NixOS options are documented: https://nixos.org/nixos/options.html#bindmount


Travis CI no longer shows as check on github pull request page

description

not sure why TravisCI no longer shows the result on Github page.

@kkdai  could you check  GitHub Apps Integration in Travis is activated?
link

I already enabled it for all my repo.

more information:  this issue happened after Aug 5, 2019.

one solution I found, hope it works.
fails-to-report-build-status-to-github

I have migrated this repo fro travis-ci.org to travis-ci.com, not sure if this is root cause.

It seems not working yet...
maybe check this permission(in settings->Applications)  again after migration

put references together:  all of them are solved by reauthorizing
Travis UI does not link a build to correct commit on GitHub PR
Status of builds not being sent to GitHub for commits and pull requests
travis-ci reports are broken
Pushes won’t trigger new builds anymore after the project has been inactive for a long time

Permission works well.

Not sure if related this

Send email to<EMAIL_ADDRESS>wait for response.

now it works!

果然是 Travis CI 關閉我權限  orz

是做什麼事了XD
@kkc 在麻煩你close了

okay, sure. I will close this issue. many thanks !!!


Race condition on line 22 of src/time/time.c

I compiled pelikan with clang-7 and -fsanitize=thread without error. I then ran ./pelikan_pingserver and was greeted with the following:
launching server with default values.
set up the ccommon::log module
Set up the ccommon::debug module
create logger with filename (null) cap 0
[Mon May 28 17:34:41 2018][INFO] /root/pelikan/deps/ccommon/src/cc_signal.c:77 override handler for SIGSEGV

**SNIP**

[Mon May 28 17:34:41 2018][INFO] /root/pelikan/deps/ccommon/src/event/cc_epoll.c:90 epoll fd 9 with nevent 1024
name: daemonize                       type: boolean          current: no                   ( default: no                   )

**SNIP**

name: tcp_poolsize                    type: unsigned int     current: 0                    ( default: 0                    )
==================
WARNING: ThreadSanitizer: data race (pid=31778)
  Write of size 4 at 0x0000011318a8 by thread T2:
    #0 time_update /root/pelikan/src/time/time.c:22:9 (pelikan_pingserver+0x4b7786)
    #1 _server_evwait /root/pelikan/src/core/data/server.c:301:5 (pelikan_pingserver+0x4b4a34)
    #2 core_server_evloop /root/pelikan/src/core/data/server.c:310 (pelikan_pingserver+0x4b4a34)

  Previous write of size 4 at 0x0000011318a8 by thread T1:
    #0 time_update /root/pelikan/src/time/time.c:22:9 (pelikan_pingserver+0x4b7786)
    #1 _worker_evwait /root/pelikan/src/core/data/worker.c:286:5 (pelikan_pingserver+0x4b58e4)
    #2 core_worker_evloop /root/pelikan/src/core/data/worker.c:297 (pelikan_pingserver+0x4b58e4)

  Location is global 'now' of size 4 at 0x0000011318a8 (pelikan_pingserver+0x0000011318a8)

  Thread T2 (tid=31781, running) created by main thread at:
    #0 pthread_create /b/build/slave/linux_upload_clang/build/src/third_party/llvm/compiler-rt/lib/tsan/rtl/tsan_interceptors.cc:965:3 (pelikan_pingserver+0x449da5)
    #1 core_run /root/pelikan/src/core/core.c:29:11 (pelikan_pingserver+0x4b5c93)
    #2 main /root/pelikan/src/server/pingserver/main.c:198:5 (pelikan_pingserver+0x4b2b71)

  Thread T1 (tid=31780, running) created by main thread at:
    #0 pthread_create /b/build/slave/linux_upload_clang/build/src/third_party/llvm/compiler-rt/lib/tsan/rtl/tsan_interceptors.cc:965:3 (pelikan_pingserver+0x449da5)
    #1 core_run /root/pelikan/src/core/core.c:23:11 (pelikan_pingserver+0x4b5c7a)
    #2 main /root/pelikan/src/server/pingserver/main.c:198:5 (pelikan_pingserver+0x4b2b71)

SUMMARY: ThreadSanitizer: data race /root/pelikan/src/time/time.c:22:9 in time_update
==================

@geeknik Thanks for reporting the issue, I think I understand why this is happening, an atomic (with relax setting) should give us the correct behavior. Coincidentally, we recently decided to improve the resolution of the cached timestamp, so I will make sure I test the issue you reported and we fix it with the new time.


orientation issue

while orientation view get changed

which error do you have exactly?

@ManojkumarKaliannan try this https://github.com/AndreiMisiukevich/CardView
Can't promise, but perhaps it will help you

I AM BACK.
Whats the issue?


Initial_prompt easily accessible

Made initial_prompt more easily accessible to be able to give context.
Fixed how the options.get is used.
Client now contains a parameter, which is now also described in the readme.
Only tested with faster_whisper, not TensorRT.

I do notice that the initial_context does not always work well. In my testing the first word was not really used, but that can be fixed by just putting another word at the front when using it.

@Spudra can we fix the tests according to the new param options?

@Spudra can we fix the tests according to the new param options?

Sure you can! (:
I also just fixed the conflict that appeared recently.

@Spudra I see the tests are still failing, would you mind updating the tests?


⚠ Bofrost.be has degraded performance

In f00dbd0, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2527 ms

Resolved: Bofrost.be performance has improved in 9314f08.


Angular2: Dynamic textMask

I have a form which I create dynamically with specific control types.  So a phone type will create a textbox with necessary validation for phone numbers and a phone text mask.  While a date of birth type will create everything necessary for dob.   There may also be types which don't require a mask such as name.
The challenge comes with dynamically creating the textMask.  It is possible to create the mask portion dynamically, but I haven't found a way to create the whole thing (mask, guide, keepCharPositions, pipe, etc) dynamically.   As well as have the option to not have any textMask at all.  Something like this would be nice:
html
    <input [textMask]="mask"  type="text"/>

component
get mask() {
   switch(controlType) {
      case 'phone': {
         return {mask: ['(', /[1-9]/, /\d/, /\d/, ')', ' ', /\d/, /\d/, /\d/, '-', /\d/, /\d/, /\d/, /\d/]};
         break;
      }
      case 'dob': {
         const autoCorrectedDatePipe = createAutoCorrectedDatePipe('mm/dd/yyyy');
         return {mask: [/\d/, /\d/, '/', /\d/, /\d/, '/', /\d/, /\d/, /\d/, /\d/], keepCharPositions: true, pipe: autoCorrectedDatePipe };
         break;
      }
      default: {
         return null;   // This causes errors within text-mask and so does returning {}
        break;
      }
   }
}

Anyone know a way to do this currently?

Looks like I missed this in the documentation:

Note: it is possible to set the mask to false to disable masking completely.

Using that, I can just use return {mask: false} as my default case which fixes this issue.


Wizardcleanup

Updated order block, please review and merge

Looks good - added to do's in issues


Creating honeycomb board with multiple panels using terraform fails with 500 Internal server error

Versions

Steps to reproduce

Run terraform plan to view the plan to create a board in honeycomb which has 23 panels
Run terraform apply to finish creating a board with multiple panels(in our case its 23 panels)

Expected Result: It should successfully create the board.
Actual Result: It throws `500 Internal Server Error: Something went wrong!

Additional context
It seems like a honeycomb API timeout is happening when we try to create a board with multiple panels.
We can work around it by trying to create 3 panels at a time and that seems to work, but it's a pain to create a board that has more than 20 panels.
Would be great if we could increase honeycomb API timeout or if something else needs to be fixed.

FYI: This is an API bug, not specific to Terraform. We're now tracking this internally, and I'll provide an update here once we believe it to be fixed.

I believe this has been resolved "server side". Please let us know if the issue remains.


Improve CI pod checking, including ripsaw itself

This adds a git_pod() function to common.sh that is more robust than the existing check_pods() function. It also uses the new function to validate the ripsaw pod before allowing the test CR to be applied. All test scripts are updated to use the new function.

rebased this @dustinblack, gonna wait for it to finish the run

/rerun all

/rerun minikube

/rerun minishift

/rerun kni


Re-exports of external modules with side effects are erased from ES5 targets

Re-exports of external modules with no public members are erased from the generated JS for ES5 targets. This causes problems in scenarios where the module is used to extend some class by patching the prototype (see #6213 and #6022).
The ultimate goal is to be able to do the following:
// a.ts
export class A { }

// b.ts
import {A} from './a';
A.prototype.foo = function () { };
declare module './a' {
  interface A { foo(): void; }
}

// c.ts
import {A} from './a';
A.prototype.bar = function () { };
declare module './a' {
  interface A { bar(): void; }
}

// all.ts
export {A} from './a';
export * from './b';
export * from './c';

Once this is built and distributed as a set of JS and definition files, the user should be able to do:
import {A} from 'somemodule/a';
import 'somemodule/all';

var a = new A();
a.foo();
a.bar();

Currently, this compiles without errors, but produces the following output for all.js:
"use strict";
var a_1 = require('./a');
exports.A = a_1.A;

You can see that ./b and ./c are not imported, which results in the prototype patches for A being unavailable at runtime. The user will therefore get the following exception:

TypeError: a.foo is not a function

Hopefully I'm not misusing the feature here.

The compiler omits the export * for ./b and ./c because it has concluded they don't export any values (this is so we don't emit export * for modules that contain only types, for example).
You can ensure that a side-effecting module with no exports is imported with a simple import 'xxx';. So, this should work:
// all.ts
import './b';
import './c';
export {A} from './a';
export * from './b';
export * from './c';

@ahejlsberg Should importing the side effecting module export its declared ambient modules to consumers? In other words, should the augmentations to a.ts in b.ts and c.ts be available to consumers of all.ts if it looks like this:
// all.ts
import './b';
import './c';
export {A} from './a';

Right now my workaround is to do this:
// all.ts
import './b'; export * from './b';
import './c'; export * from './c';
export {A} from './a';

Is there a nicer way to do this?

It works just with this:
// all.ts
import './b';
import './c';
export {A} from './a';

The augmentations don't need to be exported, they behave as if they were written on A itself. All that matters is that ./b and ./c are directly or indirectly imported in your program. Once they are, the augmentations appear on A anywhere you can access A.

@ahejlsberg Unfortunately this is not the behavior I'm seeing. When writing all.ts as you have it, and all other files as in my first comment, the generated all.d.ts looks like this:
export { A } from './a';

As you can see, no trace of the augmentations or the modules they occur in has remained, so consumers of these typings will not be aware of a.foo or b.foo.

that is true, we won't elide import "..." from implementation files but such imports won't be recorded in .d.ts files

We should emit import "mod"; in declaration files then. In the past, modules could not have a side effects, so it was safe to elide the imports from declaration files. Now with module augmentations, modules has side effects, so we should preserve these in the declaration files.


Support HandlerProvider definitions in handler.yml configuration definitions

Per suggestion in #249 , providing support for the list of handlers configured in handler.yml to allow listing of implementations of HandlerProvider.

@ddobrin no, nothing is changing in the handler.yml definition. Only that the classes being passed in can now implement HandlerProvider instead of just HttpHandler.


Make configuration non-static.

Codecov Report

Merging #7 (5796f57) into latest (13fe589) will increase coverage by 0.09%.
The diff coverage is 78.13%.

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

@@             Coverage Diff              @@
##             latest       #7      +/-   ##
============================================
+ Coverage     75.22%   75.32%   +0.09%
- Complexity     1285     1306      +21
============================================
  Files           109      111       +2
  Lines          7836     7914      +78
  Branches       1238     1245       +7
============================================
+ Hits           5895     5961      +66
- Misses         1478     1488      +10
- Partials        463      465       +2

Impacted Files
Coverage Δ

...in/java/com/msd/gin/halyard/common/RDFFactory.java
0.00% <0.00%> (ø)

...main/java/com/msd/gin/halyard/tools/RDFHasher.java
0.00% <0.00%> (ø)

...com/msd/gin/halyard/common/IdentifiableTriple.java
21.42% <20.00%> (+6.04%)
:arrow_up:

.../com/msd/gin/halyard/common/HalyardTableUtils.java
64.72% <39.13%> (-0.35%)
:arrow_down:

...om/msd/gin/halyard/common/IdentifiableValueIO.java
62.50% <62.50%> (ø)

...java/com/msd/gin/halyard/common/RDFIdentifier.java
71.42% <66.66%> (ø)

.../msd/gin/halyard/sail/HBaseSearchTripleSource.java
71.69% <66.66%> (ø)

.../main/java/com/msd/gin/halyard/common/ValueIO.java
79.12% <72.34%> (+2.78%)
:arrow_up:

...in/java/com/msd/gin/halyard/common/Identifier.java
75.55% <78.57%> (-1.37%)
:arrow_down:

.../main/java/com/msd/gin/halyard/common/RDFRole.java
73.58% <80.00%> (ø)

... and 35 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13fe589...b7e423f. Read the comment docs.