Error: filename ... used twice

Configuration
System:
OS: macOS 10.14.5
CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Memory: 100.54 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.15.3 - ~/.nvm/versions/node/v10.15.3/bin/node
Yarn: 1.15.2 - /usr/local/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.15.3/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.2, macOS 10.14, tvOS 12.2, watchOS 5.2
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 26.0.2, 26.0.3, 27.0.3, 28.0.3, 29.0.0
System Images: android-23 | Intel x86 Atom, android-23 | Google APIs Intel x86 Atom, android-26 | Intel x86 Atom_64, android-26 | Google APIs Intel x86 Atom, android-27 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-Q | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.4 AI-183.6<IP_ADDRESS>22156
Xcode: 10.2.1/10E1001 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.0 => 0.60.0
npmGlobalPackages:
react-native-cli: 2.0.1
"react-native-track-player": "^2.0.0-rc4"
Issue
Im upgrading to RN 0.60 and i facing a error in Xcode:
<unknown>:0: error: filename "AudioSession.swift" used twice: '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/SwiftAudio/Classes/AudioSessionController/AudioSession.swift' and '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/SwiftAudio/Classes/AudioSessionController/AudioSession.swift' <unknown>:0: note: filenames are used to distinguish private declarations with the same name <unknown>:0: error: filename "DSL.swift" used twice: '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/Example/Pods/Quick/Sources/Quick/DSL/DSL.swift' and '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/Example/Pods/Quick/Sources/Quick/DSL/DSL.swift' <unknown>:0: note: filenames are used to distinguish private declarations with the same name <unknown>:0: error: filename "NowPlayingInfoCenter.swift" used twice: '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/SwiftAudio/Classes/NowPlayingInfoController/NowPlayingInfoCenter.swift' and '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/SwiftAudio/Classes/NowPlayingInfoController/NowPlayingInfoCenter.swift' <unknown>:0: note: filenames are used to distinguish private declarations with the same name <unknown>:0: error: filename "NowPlayingInfoController.swift" used twice: '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/SwiftAudio/Classes/NowPlayingInfoController/NowPlayingInfoController.swift' and '/Users/maikmacs/code/react-native/project-APP/node_modules/react-native-track-player/ios/RNTrackPlayer/Vendor/AudioPlayer/SwiftAudio/Classes/NowPlayingInfoController/NowPlayingInfoController.swift' <unknown>:0: note: filenames are used to distinguish private declarations with the same name Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc failed with exit code 1

Try upgrading to 2.0.0-rc10. It seems that the current latest points to rc4 which fails to build and throws error on pod install
npm i<EMAIL_ADDRESS>

or
npm i react-native-track-player@next

@mhabegger , I'm facing with this error:
Unhandled JS Exception: Super expression must either be null or a function

Can you post your package.json ?

or
npm i react-native-track-player@next

My issue was fixed updating to "react-native-track-player": "^2.0.0-rc10" ,  After that i clean the project and reinstall the pods.

@mhabegger , I fixed it changing my ProgressBar component class to a functional component and import useProgress().

@ithustle, is it possible show an example?
"react-native": "0.60.4",
"react-native-track-player": "^2.0.0-rc13",

@rochapablo , something like this ...
import TrackPlayer, { useProgress } from 'react-native-track-player';
export const ProgressBarPremium = props => {
    const progress = useProgress();
    return (
        <View { ...props } style={styles.progressContent}>
            <Text style={{ color: "#fff", alignSelf: "center" }} >{formatTime(progress.position)}</Text>
            <Slider
                value={progress.position}
                maximumValue={progress.duration}
                onValueChange={value => {
                    TrackPlayer.seekTo(value)
                }}
                style={{ width: "70%" }}
            />
            <Text style={{ color: "#fff", alignSelf: "center" }} >{formatTime(progress.duration)}</Text>
        </View>
    )
}


Update nested error handling

I changed the implementation to what @marius0 suggested—I think it is cleaner.  Also added a test.
An important caveat is that JSON API—and Ember Data by extension—does not support nested resources and therefore does not support nested errors.  What we are doing here is essentially allowing the nested errors to come through as parent resource errors with slash-delimited attribute names.  This allows the response to be processed without blowing up, but technically the result is incorrect—the child resource's isValid continues to be true.  There is not much we can do about it except to put on this band-aid.
Related discussion: https://github.com/json-api/json-api/issues/899
See also #131 and #137
/cc @marius0 @peec

I'm going to take a stab at using the "relationships" field and see if that works.

That didn't work.  @benkonrath this is good to merge.

@dustinfarris Thanks for your work on this. I read through the patch and everything looks good. So it's just adding the link (if you agree).

Added


Generic IPMI boot utils  support

Add common place lib/boot_utils.robot for all modules to use for IPMI
and we we may need to separate
lib/boot_utils.robot to
lib/boot_rest_utils.robot
lib/boot_ipmi_utils.robot

@micwalsh TODO ahead.. we would want this..

not going to work out. Closing


[Feature Request]: Making substantial documentation update towards missing LC problem numbers 194, 195, 196 in DSA solutions folder

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Describe the new feature or enhancement you'd like to see:
I propose adding documented solutions for the following LeetCode problems to the project repository:
Problem 194: Transpose File
Problem 195: Tenth Line
Problem 196: Delete Duplicate Emails
This involves providing clear, commented code solutions along with explanations of the approaches used for each problem.
Use Case
Use Case:
For a developer working on shell scripting or data manipulation tasks, having access to well-documented solutions for these problems can significantly enhance their productivity. For example, they can use the solution for problem 194 to transpose data files, the solution for problem 195 to extract specific lines from a file, and the solution for problem 196 to clean up email data by removing duplicates. These solutions provide practical, real-world applications that can streamline various tasks in data processing and manipulation.
Benefits
What benefits would this feature bring to the project or community?
Practical Utility: Provides practical implementations for common data manipulation tasks using shell scripting.
Educational Resource: Enhances project documentation with detailed examples of file operations and data processing techniques.
Community Engagement: Encourages collaborative learning and contributions, fostering a stronger developer community around shell scripting and data manipulation.
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Dear @Ajay-Dhangar Sir.
I am writing to request the assignment of three problem solutions under LEVEL-3/2 for GSSoC 2024. Given that I will be providing documentation for three solutions simultaneously, I believe this classification is appropriate.
Thank you for your consideration.

Dear @Ajay-Dhangar Sir.
I am writing to request the assignment of three problem solutions under LEVEL-3/2 for GSSoC 2024. Given that I will be providing documentation for three solutions simultaneously, I believe this classification is appropriate.
Thank you for your consideration.

@aaryaanshh, read https://github.com/orgs/CodeHarborHub/discussions/1028 carefully

Dear @Ajay-Dhangar Sir.

Okay sir, thanks for clarifying.


Add Lock mouse feature for Battle royale games.

[ ] I have checked that a similar feature request does not already exist.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

#269?


thread-instruction-count: tidelta / ticount don't exist in tracing file

Environment 1
puppeteer-core: 2.0.0
docker image: node:12-slim
os version: macOS 10.14.6
node.js version: 12
chrome version: 77/78
Environment 2
puppeteer-core: 2.0.0
virtualisation: virtualbox 6
os version: Ubuntu 18.04
node.js version: 12
chrome version: 77
What steps will reproduce the problem?
According to this message. Puppeteer provides RTI data in trace file when flags: --enable-thread-instruction-count and --no-sandbox are used. Information should be placed in tidelta and ticount properties.
Case:
const puppeteer = require('puppeteer')

;(async () => {
  const browser = await puppeteer.launch({
    args: ['--no-sandbox', '--enable-thread-instruction-count'],
  })
  const page = await browser.newPage()

  await page.tracing.start({ path: './trace.json' })
  await page.goto('https://www.example.com/')
  await page.tracing.stop()

  await browser.close()
})()

Dockerfile
Chrome-Detect&Downloader
What is the expected result?
tidelta exist in trace.json and parameter not empty.
What happens instead?
tidelta doesn't exist in trace.json.
What a goal to use this feature?
I want to use RTI data for Web Perf Testing in tools like size-limit, estimo, etc.
PS
I tried this case with docker image node:10-slim, chrome 77 and chrome 78.
But tidelta always didn't exist in trace file.

I got more information about this problem.
After launching script with dumpio: true I got chromium log:
DevTools listening on ws://<IP_ADDRESS>:39853/devtools/browser/f1ed78b3-cd2b-418c-a7bc-79a24a7021d3
[0109/131032.904194:WARNING:ipc_message_attachment_set.cc(49)] MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[0109/131032.904284:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
[0109/131032.918871:WARNING:ipc_message_attachment_set.cc(49)] MessageAttachmentSet destroyed with unconsumed attachments: 0/1
[0109/131032.918890:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
tracing_service_impl.cc: Configured tracing, #sources:2, duration:0 ms, #buffers:1, total buffer size:102400 KB, total sessions:1
[0109/131032.951528:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.951529:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.951764:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.952957:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.954586:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.954995:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.955406:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.957047:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.960385:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.960369:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.960750:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.960873:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.960894:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.960788:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131032.961589:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131033.252945:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131033.285899:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131033.333724:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[0109/131033.624007:WARNING:cors_url_loader_factory.cc(214)] |cors_exempt_headers| contains unexpected key: Purpose
[0109/131033.806456:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
tracing_service_impl.cc: Tracing session 1 ended, total sessions:0

perf_event_open failed, omitting instruction counters - seems like by default in Docker environment new API doesn't have access to required syscall.
Without this fix, we cannot use new awesome API on CI.
Any thoughts about how we can fix it?

According to this article and Docker docs (link1, link2) there are three ways to allow this syscall:

Add special linux capability (--cap-add SYS_ADMIN)
Run Docker image in privileged mode (--privileged)
Extend default Docker seccomp profile, add perf_event_open to SCMP_ACT_ALLOW group, remove perf_event_open from group with "caps": ["CAP_SYS_ADMIN"] and  use it as custom seccomp profile.

I have tested all these ways in a few different environments:

macOS / LinuxKit VM / Docker
Win10 / VirtualBox / Docker
VMware / CentOS

But neither didn't work for me (still same chromium error output).

One gets the impression that this API can only work from under bare Linux, and any virtualization breaks it.
Can you help me to find out about this problem?

Ok. It definitely works on a bare Linux machine.
So, I have two ideas:

I mess up with granting permissions to docker (for executing perf_event_open)

Something else wrong behind perf_event_open

I tried to run perf tool in docker container (in --privileged mode) manually and got this output:
# perf stat -d ls
CHANGELOG.md  Dockerfile  LICENSE  README.md  chrome.json  index.js  node_modules  package.json  scripts  seccomp-conf.json  src  temp  test  yarn.lock

 Performance counter stats for 'ls':

          1.371443      task-clock (msec)         #    0.561 CPUs utilized
                 0      context-switches          #    0.000 K/sec
                 0      cpu-migrations            #    0.000 K/sec
                79      page-faults               #    0.058 M/sec
   <not supported>      cycles
   <not supported>      instructions
   <not supported>      branches
   <not supported>      branch-misses
   <not supported>      L1-dcache-loads
   <not supported>      L1-dcache-load-misses
   <not supported>      LLC-loads
   <not supported>      LLC-load-misses

       0.002445000 seconds time elapsed

Seems like linuxkit/docker doesn't support some of the processor's hardware performance counters, which perf uses.
I also tested all ways which I used to grant permissions to docker and all of them work well. So, this issue not about permissions for executing perf_event_open anymore.

My perf list cpu output:
# perf list cpu

List of pre-defined events (to be used in -e):

  cpu-clock                                          [Software event]
  cpu-migrations OR migrations                       [Software event]

  cpuhp:cpuhp_enter                                  [Tracepoint event]
  cpuhp:cpuhp_exit                                   [Tracepoint event]
  cpuhp:cpuhp_multi_enter                            [Tracepoint event]
  kmem:mm_page_pcpu_drain                            [Tracepoint event]
  power:cpu_frequency                                [Tracepoint event]
  power:cpu_idle                                     [Tracepoint event]
  syscalls:sys_enter_getcpu                          [Tracepoint event]
  syscalls:sys_exit_getcpu                           [Tracepoint event]
  thermal:thermal_power_cpu_get_power                [Tracepoint event]
  thermal:thermal_power_cpu_limit                    [Tracepoint event]
  xen:xen_cpu_load_idt                               [Tracepoint event]
  xen:xen_cpu_set_ldt                                [Tracepoint event]
  xen:xen_cpu_write_gdt_entry                        [Tracepoint event]
  xen:xen_cpu_write_idt_entry                        [Tracepoint event]
  xen:xen_cpu_write_ldt_entry                        [Tracepoint event]

It looks like this API depends on PMU/PMC metrics which not available in virtualized environments.
In fact, this not only depends on environment but on your CPU device too.
More context:

PMU/PMC
similar problem.
linux perf basics

I think we need an opinion from someone who more deeply in these things. Maybe there is some workaround or I miss something.

Does it work on CI with Linux environment? It could be just Docker virtualization problem.

Tomorrow I gonna prepare a few special tests for CircleCI, TravisCI, GitHub Actions and then will provide the results here.

@ai
I made a few tests and run them on CircleCI and TravisCI.
rti-api › [rti-api]: should throw when RTI API does not support by the platform - always pass
rti-api › [rti-api]: should contain "tidelta" and "ticount" if RTI API supported by the platform - always fails
So, it isn't working :(

@mbalabash @ai Is there any more information around this problem?
Would love if we could get a solution for this issue

This may help on investigation, when runing on bare metal Linux (The one that worlds and displays the tidelta correctly we have this execution header):
{
  "chrome-bitness": 64,
  "clock-domain": "LINUX_CLOCK_MONOTONIC",
  "command_line": "/opt/google/chrome/google-chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-features=TranslateUI --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --headless --hide-scrollbars --mute-audio --enable-thread-instruction-count --no-sandbox --disable-setuid-sandbox --disable-dev-shm-usage --remote-debugging-port=0 --user-data-dir=/tmp/puppeteer_dev_chrome_profile-TOVbOO --use-gl=swiftshader-webgl --allow-pre-commit-input about:blank",
  "cpu-brand": "Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz",
  "cpu-family": 6,
  "cpu-model": 158,
  "cpu-stepping": 13,
  "gpu-devid": 65535,
  "gpu-driver": "<IP_ADDRESS>",
  "gpu-gl-renderer": "Google SwiftShader",
  "gpu-gl-vendor": "Google Inc.",
  "gpu-psver": "3.00",
  "gpu-venid": 65535,
  "gpu-vsver": "3.00",
  "highres-ticks": 1,
  "network-type": "WiFi",
  "num-cpus": 12,
  "os-arch": "x86_64",
  "os-name": "Linux",
  "os-version": "5.5.13-arch2-1",
  "perfetto_trace_stats": {
    "buffer_stats": [
      {
        "buffer_size": 209715200,
        "bytes_overwritten": 0,
        "bytes_read": 458752,
        "bytes_written": 622592,
        "chunks_committed_out_of_order": 0,
        "chunks_discarded": 0,
        "chunks_overwritten": 0,
        "chunks_read": 14,
        "chunks_rewritten": 0,
        "chunks_written": 19,
        "padding_bytes_cleared": 0,
        "padding_bytes_written": 0,
        "patches_failed": 0,
        "patches_succeeded": 0,
        "readaheads_failed": 0,
        "readaheads_succeeded": 0,
        "trace_writer_packet_loss": 0,
        "write_wrap_count": 0
      }
    ],
    "chunks_discarded": 0,
    "data_sources_registered": 11,
    "data_sources_seen": 4,
    "patches_discarded": 0,
    "producers_connected": 5,
    "producers_seen": 0,
    "total_buffers": 1,
    "tracing_sessions": 1
  },
  "physical-memory": 31744,
  "product-version": "HeadlessChrome/80.0.3987.163",
  "trace-capture-datetime": "2020-5-22 2:22:7",
  "trace-config": "{\"enable_argument_filter\":false,\"enable_systrace\":false,\"excluded_categories\":[\"*\"],\"included_categories\":[\"devtools.timeline\",\"v8.execute\",\"toplevel\",\"blink.console\",\"blink.user_timing\",\"latencyInfo\",\"disabled-by-default-devtools.timeline\",\"disabled-by-default-devtools.timeline.frame\",\"disabled-by-default-devtools.timeline.stack\",\"disabled-by-default-v8.cpu_profiler\",\"disabled-by-default-v8.cpu_profiler.hires\"],\"record_mode\":\"record-until-full\"}",
  "user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/80.0.3987.163 Safari/537.36",
  "v8-version": "8.0.426.30"
}

Running it from a docker container WITH PRIVILLEGES and without "tidelta" on the response we get this:
{
  "chrome-bitness": 64,
  "clock-domain": "LINUX_CLOCK_MONOTONIC",
  "command_line": "/usr/bin/google-chrome --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-default-apps --disable-dev-shm-usage --disable-features=TranslateUI --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --disable-sync --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --headless --hide-scrollbars --mute-audio --enable-thread-instruction-count --no-sandbox --disable-setuid-sandbox --disable-dev-shm-usage --remote-debugging-port=0 --user-data-dir=/tmp/puppeteer_dev_chrome_profile-5xPBH6 --use-gl=swiftshader-webgl --allow-pre-commit-input about:blank",
  "cpu-brand": "Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz",
  "cpu-family": 6,
  "cpu-model": 158,
  "cpu-stepping": 13,
  "gpu-devid": 65535,
  "gpu-driver": "<IP_ADDRESS>",
  "gpu-gl-renderer": "Google SwiftShader",
  "gpu-gl-vendor": "Google Inc.",
  "gpu-psver": "3.00",
  "gpu-venid": 65535,
  "gpu-vsver": "3.00",
  "highres-ticks": 1,
  "network-type": "Ethernet",
  "num-cpus": 12,
  "os-arch": "x86_64",
  "os-name": "Linux",
  "os-version": "5.5.13-arch2-1",
  "physical-memory": 31744,
  "product-version": "HeadlessChrome/84.0.4147.13",
  "trace-capture-datetime": "2020-5-22 2:34:7",
  "trace-config": "{\"enable_argument_filter\":false,\"enable_systrace\":false,\"excluded_categories\":[\"*\"],\"included_categories\":[\"devtools.timeline\",\"v8.execute\",\"toplevel\",\"blink.console\",\"blink.user_timing\",\"latencyInfo\",\"disabled-by-default-devtools.timeline\",\"disabled-by-default-devtools.timeline.frame\",\"disabled-by-default-devtools.timeline.stack\",\"disabled-by-default-v8.cpu_profiler\",\"disabled-by-default-v8.cpu_profiler.hires\"],\"record_mode\":\"record-until-full\"}",
  "trace_processor_stats": {
    "android_log_num_failed": 0,
    "android_log_num_skipped": 0,
    "android_log_num_total": 0,
    "clock_sync_cache_miss": 31,
    "clock_sync_failure": 0,
    "compact_sched_has_parse_errors": 0,
    "compact_sched_switch_skipped": 0,
    "compact_sched_waking_skipped": 0,
    "counter_events_out_of_order": 0,
    "empty_chrome_metadata": 0,
    "ftrace_bundle_tokenizer_errors": 0,
    "fuchsia_invalid_event": 0,
    "fuchsia_non_numeric_counters": 0,
    "fuchsia_timestamp_overflow": 0,
    "gpu_counters_invalid_spec": 0,
    "gpu_counters_missing_spec": 0,
    "gpu_render_stage_parser_errors": 0,
    "graphics_frame_event_parser_errors": 0,
    "guess_trace_type_duration_ns": 1392,
    "heap_graph_location_parse_error": 0,
    "heap_graph_non_finalized_graph": 0,
    "heapprofd_missing_packet": 0,
    "heapprofd_non_finalized_profile": 0,
    "interned_data_tokenizer_errors": 0,
    "invalid_clock_snapshots": 0,
    "invalid_cpu_times": 0,
    "json_tokenizer_failure": 0,
    "meminfo_unknown_keys": 0,
    "metatrace_overruns": 0,
    "mismatched_sched_switch_tids": 0,
    "misplaced_end_event": 0,
    "mm_unknown_type": 0,
    "ninja_parse_errors": 0,
    "packages_list_has_parse_errors": 0,
    "packages_list_has_read_errors": 0,
    "parse_trace_duration_ns": 2222259,
    "perf_samples_skipped": 0,
    "perf_samples_skipped_dataloss": 0,
    "power_rail_unknown_index": 0,
    "proc_stat_unknown_counters": 0,
    "process_tracker_errors": 0,
    "rss_stat_negative_size": 0,
    "rss_stat_unknown_keys": 0,
    "rss_stat_unknown_thread_for_mm_id": 0,
    "sched_switch_out_of_order": 0,
    "sched_waking_out_of_order": 0,
    "slice_out_of_order": 0,
    "stackprofile_invalid_callstack_id": 0,
    "stackprofile_invalid_frame_id": 0,
    "stackprofile_invalid_mapping_id": 0,
    "stackprofile_invalid_string_id": 0,
    "stackprofile_parser_error": 0,
    "systrace_parse_failure": 0,
    "task_state_invalid": 0,
    "thread_time_in_state_out_of_order": 0,
    "thread_time_in_state_unknown_cpu_freq": 0,
    "tokenizer_skipped_packets": 0,
    "traced_buf": [
      {
        "buffer_size": 209715200,
        "bytes_overwritten": 0,
        "bytes_read": 557056,
        "bytes_written": 688128,
        "chunks_committed_out_of_order": 0,
        "chunks_discarded": 0,
        "chunks_overwritten": 0,
        "chunks_read": 17,
        "chunks_rewritten": 0,
        "chunks_written": 21,
        "padding_bytes_cleared": 0,
        "padding_bytes_written": 0,
        "patches_failed": 0,
        "patches_succeeded": 0,
        "readaheads_failed": 0,
        "readaheads_succeeded": 0,
        "trace_writer_packet_loss": 0,
        "write_wrap_count": 0
      }
    ],
    "traced_chunks_discarded": 0,
    "traced_data_sources_registered": 11,
    "traced_data_sources_seen": 4,
    "traced_patches_discarded": 0,
    "traced_producers_connected": 5,
    "traced_producers_seen": 0,
    "traced_total_buffers": 1,
    "traced_tracing_sessions": 1,
    "track_event_parser_errors": 0,
    "track_event_tokenizer_errors": 0,
    "vmstat_unknown_keys": 0,
    "vulkan_allocations_invalid_string_id": 0
  },
  "user-agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/84.0.4147.13 Safari/537.36",
  "v8-version": "8.4.371.7"
}

Key interesting differences is that in the "bare metal" we get perfetto_trace_stats and on docker we get trace_processor_stats

It may seem like within docker we are getting into this path https://github.com/google/perfetto/blob/master/src/trace_processor/export_json.cc#L166

Looks like what controls if trace_processor_stats or perfetto_trace_stats is used was defined in here https://github.com/google/perfetto/commit/bb0e154023150a87068ea3c5172eb51afba95f0c

It seems that the trace_processor_stats could have been introduced in https://github.com/google/perfetto/commit/e2b4e5c6c0da4ca0d9d3aeaeb562a95c3b6b5844 But it's unclear to me still why within docker we get one over the other

I just noticed that I was comparing two different chrome versions:

  "os-version": "5.5.13-arch2-1",
  "product-version": "HeadlessChrome/80.0.3987.163",
  "v8-version": "8.0.426.30"

  "os-version": "5.5.13-arch2-1",
  "product-version": "HeadlessChrome/84.0.4147.13",
  "v8-version": "8.4.371.7"

Will update chrome and test again

Hey @mittermayr!
Did you have any progress with your idea?

As described in article JavaScript component-level CPU costs - this feature was work well on Chrome 78, so maybe try to retest this in exact 78 version of Chromium, and in later version this feature is changed/broken?

@MurzNN As we know from the article, that code was executed on a bare metal linux machine. And as I know, it wasn't tested in docker environment.
Also, all tests at the beginning of the story were with Chrome 78.

But ticount not show even on my bare metal linux machine (Intel(R) Core(TM) i3-4330 CPU @ 3.50GHz, using Ubuntu Linux 16.04), so the source of this issue seems not in Docker, but in Chromium itself?

@MurzNN Which version of Chrome do you use?
Could you please run this example on your machine:
const puppeteer = require('puppeteer')

;(async () => {
  const browser = await puppeteer.launch({
    args: ['--no-sandbox', '--enable-thread-instruction-count'],
  })
  const page = await browser.newPage()

  await page.tracing.start({ path: './trace.json' })
  await page.goto('https://www.example.com/')
  await page.tracing.stop()

  await browser.close()
})()

Then:

Copy content from trace.json file
Create gist and paste content from the previous step
Provide a link to this gist in your comment.

Done: https://gist.github.com/MurzNN/5e2683d1c4e2e59d8478b4cc95c4366e

@MurzNN Yes, you right. Your trace file don't contain ticount and tidelta values.
It means that something has been changed in the latest Chrome versions.
I not familiar with changes which were happened in 81, 82, 83 versions. So, I'm going to do homework and will provide an update ASAP.

the source of this issue seems not in Docker, but in Chromium itself?

It's hard to be sure at 100%. But my main hypothesis is that a problem could be in hypervisors or hardware (hope I wrong).
Looks like a ton of changes were applied to tracing feature. One of them could possibly break enable-thread-instruction-count API.
@MurzNN Could you please do the test, which Andrey did on his bare metal Linux machine?
That test will run Chrome 79 and enable-thread-instruction-count API should work as expected.

@mbalabash, I do test on Ubuntu 20.04, output is here: https://gist.github.com/MurzNN/52c8944c747d026d8afee509537c7a75

When I manually launch chrome and enable tracing, I see in output
$ ./chrome --no-sandbox --enable-thread-instruction-count
[329820:329820:0609/065603.823454:ERROR:sandbox_linux.cc(369)] InitializeSandbox() called with multiple threads in process gpu-process.
[329820:329820:0609/065605.305150:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
tracing_service_impl.cc: Configured tracing, #sources:2, duration:0 ms, #buffers:1, total buffer size:102400 KB, total sessions:1
[329975:329977:0609/065638.525405:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[329975:329975:0609/065638.524778:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[329822:329856:0609/065638.528999:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[329975:329978:0609/065638.528997:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[329822:329853:0609/065638.529197:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[329820:329847:0609/065638.535137:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters
[329894:329894:0609/065638.535123:ERROR:thread_instruction_count.cc(65)] perf_event_open failed, omitting instruction counters

Seems perf_event_open failed is source of problem?

@MurzNN I had the same behavior with perf_event_open on my Mac laptop. You can read all thread from start.

After enabling it - I see ticount in json results of your test file!

Which case works for you? First or Second? Maybe both?

@mbalabash after echo 1 | sudo tee /proc/sys/kernel/perf_event_paranoid - both becomes work, and all other cases too!

@MurzNN Cool. It means that it still works on bare metal Linux )

I test this in Docker - ticount shows well with docker run --cap-add SYS_ADMIN myImage (and even with echo 3 | sudo tee /proc/sys/kernel/perf_event_paranoid, without this argument - ticount missing.
Also ticount not available on virtual environment, running same code natively or via Docker on several cloud VPS's, that I have, not show me ticount.

Here is my quick script for check ticount support:
const puppeteer = require('puppeteer');
const fs = require('fs');

puppeteerStart = async function() {
  const browser = await puppeteer.launch({
  args: [
    '--no-sandbox',
    '--enable-thread-instruction-count',
  ]});
  const page = await browser.newPage();
  await page.tracing.start({path: 'trace.json'});
  await page.goto('https://google.com/');
  await page.tracing.stop();
  await browser.close();
  let traceData = fs.readFileSync('trace.json').toString();
  // console.log(traceData);
  if(traceData.includes(',"ticount":')) {
    console.log('ticount support is enabled!');
  } else {
    console.log('ticount support is disabled!');
  }
}

puppeteerStart();

@MurzNN Thank you for your work. It is really helpful to understand this issue.
Your tests also confirm the hypothesis that the problem is in hypervisors.
Which means we can't use it in CI 😔.

So, is there any improvements about ticount support checking planned for puppeteer?

It's confirmed, just waiting for the response!

So, is there any improvements about ticount support checking planned for puppeteer?

I don't think we plan anything in this area and it looks like the issue for the original reporter is resolved (skimming over the comments). Also, Puppeteer just forwards the traces from the browser so if there is a problem with the tracing data it's better to open an issue at crbug.com.

So I am going to mark this one as not planned, because we are unlikely to do anything about it in Puppeteer. I recommend raising the issue at crbug.com with the owners of the --enable-thread-instruction-count flag in Chromium.

For anyone else curious – it appears that support for these fields was removed in Chrome in this Jun 2022 commit, which landed in release 105.0.5137.0:
https://chromium.googlesource.com/chromium/src/+/736be85b0d7c4fbfaacc7fcd8571828f8ad4dee1


Add new API: ShareFileClient::GetRangeListDiff

closes https://github.com/Azure/azure-sdk-for-cpp/issues/1908
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[x] C++ Guidelines
[x] Doxygen docs
[x] Unit tests
[x] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[x] Related issue listed

[x] Comments in source
[x] No typos
[x] Update changelog
[x] Not work-in-progress
[x] External references or docs updated
[x] Self review of PR done
[x] Any breaking changes?

/azp run cpp - storage

/azp run cpp - storage


Make mapEntryBuilderInfo public

This change exposes the private BuilderInfo variable mapEntryBuilderInfo as a public variable.
The benefits are described in the issue, but I will restate/refine here:

Allows accessing enumValues for map values that are enums (was not possible before)
Also allows general access to the FieldInfo of map key/values (developer flexibility)
Exposing the BuilderInfo allows the direct use of the PbMap constructor as opposed to needing to call createMapField on an instance of a GeneratedMessage

Fixes #276

@googlebot I signed it!
On Sun, Sep 8, 2019, 12:16 googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project (if not, look below for help).
Before we can look at your pull request, you'll need to sign a Contributor
License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot
I signed it!) and we'll verify it.
What to do if you already signed the CLA Individual signers

It's possible we don't have your GitHub username or you're using a
different email address on your commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.

Corporate signers

Your company has a Point of Contact who decides which employees are
authorized to participate. Ask your POC to be added to the group of
authorized contributors. If you don't know who your Point of Contact is,
direct the Google project maintainer to go/cla#troubleshoot (Public
version https://opensource.google.com/docs/cla/#troubleshoot).
The email used to register you as an authorized contributor must be
the email used for the Git commit. Check your existing CLA data
https://cla.developers.google.com/clas and verify that your email is
set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
The email used to register you as an authorized contributor must
also be attached to your GitHub account
https://github.com/settings/emails.

ℹ Googlers: Go here
https://goto.google.com/prinfo/https%3A%2F%2Fgithub.com%2Fdart-lang%2Fprotobuf%2Fpull%2F280
for more info.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/protobuf/pull/280?email_source=notifications&email_token=AA7SPTE7T62SFKJSS54RQRDQIVFSDA5CNFSM4IUUQKJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6FXJ7I#issuecomment-529233149,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7SPTEAPVN6DQAAU7TZ4Y3QIVFSDANCNFSM4IUUQKJQ
.


HEAD request with empty body but set content-length triggers panic

Version
hyper 1.5.0
Platform
MacOS
Description
With HEAD requests it seems it is often the case that content-length is set to relevant GET body response, but payload is empty.
That's what for example tower_http ServeDir does. In debug mode this triggers panic:
https://github.com/hyperium/hyper/blob/master/src/proto/h1/role.rs#L704C36-L704C89
I guess this assertion should skip HEAD method completely or maybe it's more of a tower_http bug and body should define different sizehints here?
Release version works as expected, as assertion is skipped.

Hm, Yea, that check should probably include checking if an actual body is expected. I imagine we have a function for that elsewhere in this file...


chore(walletsync): enhance the websocket notifications hook for watch loop

✅ Checklist

[ ] npx changeset was attached.
[ ] Covered by automatic tests.
[x] Impact of the changes:

watch loop

📝 Description

reduce the loop to 10s

small evolution on the watchConfig object,
as documented by https://ledgerhq.atlassian.net/wiki/spaces/WXP/pages/4902912002/future+improvement+consideration
we simply can consider that websocket notifications is a small enhancement on top of the regular polling mecanism.

We can test on the web tools, the websocket mode is disabled by default

❓ Context

JIRA or GitHub link:

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

/generate-screenshots


fixing a broken repo url

Signed-off-by: Dave Huseby<EMAIL_ADDRESS>

@ryjones will you give this a looksee and merge it if it looks good?


chore: adjust samples timeout

It looks like our samples have been timing out for some time. I took a quick look and it seems that a couple of our tests sometimes take well over a minute to complete. I've adjusted the ava timeout to match our system tests timeout (10 minutes).
I also noticed that some commands accept a timeout argument, this ended up superseding the ava timeout causing some tests to exit early and fail.

@callmehiphop is the other sample test failure here unrelated?

@JustinBeckwith yeah, back to random failures, haha.


yield* test now fails with iojs

no idea why
1a85931965fdc519631bd933d895bcc4f499c675

yield* iterates through the iterable ~_~


Fix #857: allow logging NoWorkingMirrorError to include details

Fixes issue #857, allowing logging of NoWorkingMirrorError to include details for contained errors that use calculated error messages (like ReplayedMetadataError).
The PR does this by adding __repr__() functions to the contained errors.
While it's at it, this PR additionally:

adds __repr__() funcs to some other exceptions that have __str__() funcs
fixes some minor style issues
for reviewers, adds commented-out direct-reproduction code
to the __repr__() funcs (probably will be cut before merging)

👍
A tuf.log excerpt from running the tests on this branch shows ReplayedMetadataError details in a NoWorkingMirrorError log line.
[2019-04-19 17:39:56,710 UTC] [tuf.client.updater] [ERROR]<EMAIL_ADDRESS>Failed to update 'timestamp.json' from all mirrors: {'http://localhost:33283/tmpj3hx5_qv/TestReplayAttack__u7ayn0g/repository/metadata/timestamp.json': ReplayedMetadataError : Downloaded 'timestamp' is older (1) than the version currently installed (2).}

Didn't catch the recent review before merging via cmd line.  (I guess the page I looked at hadn't refreshed in a few hours?)  I'll add a PR to address the comments.


Possible Coverage Maxiumum?

This would fall under the question label but I've been curious without fuzzying wasm which fuzzilli doesn't natively support how much coverage percentage is possible to reach? What is the fuzzer coverage represent does it represents code coverage as whole in JavaScriptCore if so then could one infer that the fuzzer can never truly reach 100%, Only asking out of curiosity because I notice around the 17%-20% mark the coverage increase starts to slow drastically almost to a standstill for hours even though exec/second is still in the high hundreds this was observed around reaching the 10M exec mark with fuzzilli also let's say 100% is reached would fuzzilli stop the session or something if it reaches 100%?

Yeah, Fuzzilli will usually only reach ~25% or so on current JSC builds, for V8 it's even less (and coverage increase drops sharply after a few hours, as you've noted). There's a ton of code that cannot be reached during Fuzzing, also there are many conditions (such as all the assertions) that will normally always branch in one direction (so only get 50% covered). If you're curious where coverage is missing, you could generate and inspect source coverage reports from a Fuzzilli corpus: https://clang.llvm.org/docs/SourceBasedCodeCoverage.html
Fuzzilli doesn't stop fuzzing unless you've specified a --numIterations value.

@saelo Thanks that was a perfectly explained answer and exactly what I was wondering :).


feat: support non-worldid bridge usage on core

we still want to provision deep face in the developer portal? Makes sense just to have a place to set it up but just checking


Choose câmera in mobile

There is no way to choose the camera on the mobile phone.
Android 5 - Chrome

So this doesn't really work properly in any mobile browser I tested.  Totally different problems for each browser of course.  I believe it is really only meant for the mobile app (which we aren't working on yet) so I've disabled the feature all together.  If we ever do the mobile app we can re-enable it there.
Thanks for reporting!


Proposal for refactor using reflect

Infers field reading/setting based on target type from go-thousandeyes library, eliminating repeated translation of values and the need for separate functions to unpack representations of certain types.
Build schemas dynamically based on target type, making it easier to use a single source of truth for schemas (but still enable overriding them if need be).

@johntdyer

@william20111  Any comments on this approach ?

Sorry been busy at work and home.
I like and dislike this approach. The complexity is slightly off putting for long term maintainability and I have looked around to see if other providers are doing this and can’t see anything out there doing anything like this. Just wondering why that is the case:
Let me review it properly this week sorry for delay.

@william20111 Thanks for taking a look (when you're able)
Maintainability was my thought in trying this.  In the branch where I have all providers converted, it's thus far a net reduction of about 1500 lines of code--particularly the repetitive parts where errors become harder to spot.  Removing five extra translations of each individual field removes a lot of opportunities for mistakes (and in effect, a fair number of actual mistakes from each of us).
I can understand the hesitancy when looking at the reflect code.  Idioms in reflect aren't as straightforward, and the flow may not be obvious without knowing the form of both sides of the data.  But it's fairly compact and provable, and the more complicated bit could instead just leverage existing code.
I don't know of another Terraform provider that uses this specific method, but in my (limited) experience they often have more complicated logic for their CRUD calls or don't have such a long list of straightforward value to value translations with duplicated schema definitions where there could be as much gained by this method.  The TE API itself provided the both impetus and the opportunity to  optimize.

Tests have been added to cover the new reflect inference functions.  I think that these can provide a high degree of confidence should any changes need to be made.  Since these are reused through the different providers, it should hopefully give us some more confidence in overall code.
There is one function still lacking a test: ResourceUpdate.  I have a bit more digging to do to work the right way to shim the Terraform struct instances I need to simulate config diffs.  But this is one of the simpler functions, that operates very closely to other functions that do have tests.
As noted in the gitter discussion, inferring the values would require that some of the field names in go-thousandeyes structs to be closer in line to their JSON tags.  I can have a PR for that shortly.

Update to my last comment:  After updating go-thousandeyes, it seems that the fields with definitions that would need to be changed are either cases of functions that aren't yet implemented in the Terraform provider or things that are need of correction for other reasons.
Which is to say, no coordination should be needed between any changes here and any changes for a go-thousandeyes release.

On further testing, it seems the exception for "test_name" to translate to "name" will not work, as there are some cases where the TE API uses "name" for other values.  My intention had been to not break any existing config name conventions with this (the only cases where name updates were required had not been working in the Terraform provider yet), but this would not be possible without less elegant measures.
Though deviating from existing function is one of the cardinal sins, I can appeal to convention here:  The other examples of Terraform providers I'm examining do not try to make the config names more generic, and prefer to have direct representations of the field names they represent.  Outside of external convention, I think there is some clarity value in the config names translating more directly to the API field names.

@william20111 does @JTBlanchard  owe you anything else on this PR before you can maybe get this merged?

will try to get this merged today


Port BoundedMailbox to C#

The bounded mailbox has some nice properties in terms of low GC overhead.
It would be good to have the same for C# too.

Started to have a look at this. The BoundedMailbox in Go uses the RingBuffer package, based on the bounded MPMC queue described here: http://www.1024cores.net/home/lock-free-algorithms/queues/bounded-mpmc-queue
There is a .NET implementation of that algorithm here: https://github.com/alexandrnikitin/MPMCQueue.NET
The code looks very solid to me - should we bring it in?

Go for it! , it should be fairly easy to find out if it is OK by using it in the ping-pong benchmark.


Implement horizontal regridding of irregular grids

The regridding of irregular grids to regular grids is availalbe in the regrid module but is not yet tested.
As a test case, the sic variable (sea-ice concentration) will be used.

@valeriupredoi, I'd like to volunteer to test changes related to irregular grids. Let me know when you're ready for me to have a crack at it!

hey guys, I've just started looking into this just today -- I grabbed MPI-ESM-LR/MR files for sic variable and had a first looksee through the files. Data has shape = (time, len(i), len(j)) where (i, j) represent  the indices along (dim1, dim2), in this case (lat, lon). The metadata comes with a set of (lat, lon) as well, as AuxCoords but len(j) differs from len(lon) (whereas len(i) = len(lat = 220). My question to the oceans and gridding experts @bjlittle @ledm and @mattiarighi  is how to project the irregular grid onto a regular grid in the most precise way, without massive loss of generality. I found this that explains the relation between x,y (lat, lon) and p,q (i,j): http://polar.ncep.noaa.gov/waves/workshop/pdfs/wwws_2013_irregular_grids.pdf but the problem is that the indexing of (lat, lon) won't work if len(j) = len(lat). Any advice how to get a metric g=(i, j, lat, lon) to map to a regular (lat_rg, lon_rg) grid?

@valeriupredoi @ledm Generally, the question of how to correctly interpolate data from the irregular grids of some ocean models to regular (lat-lon) grids has been hotly debated in the ocean modelling community for a long time. Some people would like to do an interpolation (e.g. us a for a meaningful intercomparison of several CMIPi models), and other people object to it because any interpolation always means a loss of accuracy, and hence loss of conservation in (interpolated) tracer fields.
But I guess you know this already.
Back to the actual question. For the case of the ORCA configurations, at least the direct model output netcdf files and the mesh_grid netcdf file contain all the information about where exactly in lat-lon space every single grid vertex sits. From that, interpolation scripts (e.g. SCRIP) can calculate mapping weights for the actual interpolation - your metric g(i,j,lat,lon). I guess the problem you've got with the MPI data is that this mapping doesn't work because the information about the grid in the metadata doesn't match the grid that the actual data are on. Is that right? If so, I'd contact MPI to be honest. Perhaps it's a bug they've sorted out already.

one more thought @valeriupredoi : if you len(j) and len(lon) differ by only 1 or 2, it could be a wrap-around thing? in that case, if we assume len(j) is that bit larger, the first and last values are identical perhaps?

We have just discussed with @valeriupredoi different ways of interpolation. I will just live here several links  that can be useful in this respect:
Interpolation between grids with Basemap
Interpolation between grids with cKDTree
Interpolation between grids with pyresample
Several libraries that can do interpolation:
Relativelly simple:
scipy interp2d
More powerful, aware of geographcal coordinates:
pyresample
Very powerful, but the API is not the most "pythonic" one:
ESMpy

It would be best if the regridding could be done through iris, possibly using one of those packages. @bjlittle Can you say something about this?

hey guys, cheers muchly for the input -- great responses! I am thinking a simple interpolation will do for now, and then we can get to more complex solutions starting from this. @bouweandela iris has an interpolator: https://scitools.org.uk/iris/docs/v2.0/userguide/interpolation_and_regridding.html but am not sure how well it works for a case like ours, I have never used it myself. @bjlittle is the main man here :grin:

Sorry for double posting to some of you. Here is what is available now in iris:
https://scitools.org.uk/iris/docs/latest/iris/iris/experimental/regrid.html
The functions are experimental for now.
I would still go for solutions like pyresample or especially ESMPy since they are more general. For them, it does not matter if the original data are on regular or the curvilinear grid (or unstructured mesh for that matter). So you write a function that covers all cases at once.

Outcome of the workshop discsussion on this topic:

the first goal would be to have a regridding package for dealing with 2D variables on irregular grids (like sic)
Iris does not provide such a method (yet)
the ESMF package is the preferred alternative and it is well established
@koldunovn @zklaus and @valeriupredoi will work towards a first implementation within the ESMValTool .preprocessor._regrid.py module
the order of operations of the preprocessor will not be changed for now

This is implemented in the branch version2_irregular_2d_regridding. If someone wants to give it a spin, they are welcome, but at the moment automated tests are missing.

Thanks @zklaus, this is great!
Could you open a pull request? This would allow us to see code changes and comment.

Some specific model / variable combination may require a fix for the irregular regridding to work properly. This will be addressed in separate issues.
Thanks @zklaus for this essential new feature!

yes - big thanks from me as well @zklaus :beer:

Fantastic work @zklaus, I'm very glad that this is done. We can now use the main development branch of ESMValTool for evaluating ocean models. This is tremendous progress.

Thanks guys! I'm happy too :)


Commit / rollback never called

I am working on React native app , I am trying to use redux-offline lib in my project.
When I tried to add user from offline but  none of actions INSERT_NEW_USER_OFFLINE / INSERT_NEW_USER_FAILURE called, i.e commit or rollback is not calling.It always its call INSERT_NEW_USER
insertNewUserData: (userData) => {
const effectReconciler = () => {
return (api.setUsers({
user_id: userData.id,
user_first_name: userData.firstName,
user_last_name: userData.lastName,
updated_at: Math.floor(Date.now() / 1000)
}));
};
const commit = () => {
return { type: 'INSERT_NEW_USER_OFFLINE', payload: userData, meta: { userData } };
};
const rollback = () => {
return { type: 'INSERT_NEW_USER_FAILURE', payload: userData, meta: { userData } };
};
return {
type: 'INSERT_NEW_USER',
payload: userData,
meta: {
offline: {
effect: effectReconciler(),
commit,
rollback
}
}
};
Let me know if anything need to change in above code..

Instead of action creators, the commit and rollback need to be actions:
- const commit = () => {
+ const commit = {
  return { type: 'INSERT_NEW_USER_OFFLINE', payload: userData, meta: { userData } };
};
- const rollback = () => {
+ const rollback = {
  return { type: 'INSERT_NEW_USER_FAILURE', payload: userData, meta: { userData } };
};

After making above changes still these two actions are not calling . I am using redux-offline 2.0 version..
When I add user I was in offline and then changed offline mode to online mode  with the expectation  commit or rollback action will be called.But nothing is happening.. I am using  redux-offline with ignite project.
import { createStore, applyMiddleware, compose } from 'redux';
import { autoRehydrate } from 'redux-persist';
import Config from '../Config/DebugConfig'
import createSagaMiddleware from 'redux-saga';
import RehydrationServices from '../Services/RehydrationServices'
import ReduxPersist from '../Config/ReduxPersist'
import { offline } from 'redux-offline'
import offlineConfig from 'redux-offline/lib/defaults'
// creates the store
export default (rootReducer, rootSaga) => {
/* ------------- Redux Configuration ------------- */
const middleware = [];
const enhancers = [];
/* ------------- Saga Middleware ------------- */
const sagaMonitor = DEV ? console.tron.createSagaMonitor() : null;
const sagaMiddleware = createSagaMiddleware({ sagaMonitor });
middleware.push(sagaMiddleware);
/* ------------- Assemble Middleware ------------- */
enhancers.push(applyMiddleware(...middleware));
/* ------------- AutoRehydrate Enhancer ------------- */
// add the autoRehydrate enhancer
if (ReduxPersist.active) {
enhancers.push(autoRehydrate());
}
// if Reactotron is enabled (default for DEV), we'll create the store through Reactotron
const createAppropriateStore = Config.useReactotron ? console.tron.createStore : createStore;
//  const store = createAppropriateStore(rootReducer, compose(...enhancers))
const store = createAppropriateStore(rootReducer, {}, compose(...enhancers), offline({ ...offlineConfig}));
// configure persistStore and check reducer version number
if (ReduxPersist.active) {
RehydrationServices.updateReducers(store);
}
// kick off root saga
sagaMiddleware.run(rootSaga);
return store;
};

I believe this line is incorrect:
const store = createAppropriateStore(rootReducer, {}, compose(...enhancers), offline({ ...offlineConfig}));

In Redux Offline 2.x, you should compose the offline enhancer as one of the enhancers inside compose, rather than pass it as the 4th argument to createStore as in 1.x.
See release notes and migration guide from 1.x->2.x: https://github.com/jevakallio/redux-offline/releases/tag/v2.0.0

Thanks. I made appropriate changes to the code  as below,
 const store = createAppropriateStore(rootReducer, {}, compose(...enhancers, offline(offlineConfig)));
Still it calling INSERT_NEW_USER action , not OfflineActions(commit and rollback) even though I am in offline

hitting the same issue, and I track it down to effect not being called

@enahum For me too :( , the effect does not get triggeredm but the redux-persist works (the offline data)

Just to weigh in on this I think that there may be some confusion about how the meta.offline key works. To summarise it seems a few of the commentors are thinking they need to pass functions as the values for effect, commit and rollback, but these are actually all just objects. So to give an example from the docs your actions should look like:
{
  type: 'FOLLOW_USER_REQUEST',
  payload: { userId },
  meta: {
    offline: {
      // the network action to execute:
      effect: { url: '/api/follow', method: 'POST', body: { userId } },
      // action to dispatch when effect succeeds:
      commit: { type: 'FOLLOW_USER_COMMIT', meta: { userId } },
      // action to dispatch if network action fails permanently:
      rollback: { type: 'FOLLOW_USER_ROLLBACK', meta: { userId } }
    }
  }
}

The effect reconciler (if you want to configure one) needs to be configured when setting up the store.

Inserting the sample code, as @DylanGriffith showed, the problem continues

@davidsonsns did you get anywhere with this? Facing the same issue :-/

Can we reopen this issue I have exactly the same

Please open a new issue following our bug report template. Also add an example of how you declare an offline action

My issue was a PEBKAC problem, but just in case anybody else is stuck, make sure your commit and rollback properties are on the offline object, not that object's effect object.


Check if onMatch is null before calling

fixes #2
Amazingly simple yet so powerful addon to the TextEditingController btw xP

Already worked it out in the new version, Thanks!

Already worked it out in the new version, Thanks!


Center player over Tube, Tree when caught in collision vortex

Description of Issue
This is to fix the issue where Lopez does not center in tube on jump to end game.

New Look samples
This fix makes the Lopez and Monkey look like there jumps are appropriately centered.  However, as both reach the floor they seem to appear to the left of automatic centering.  This is another issue to code fix.

Sample code fix
The x position needed to be adjusted to be offset from center of obstacle, not the same as obstacles x position.
This fix  was made in collision code.  The only reason Mario looked OK is because sprite width of Tube and Mario were similar.   This was not the case with Lopez and the Monkey.

GameObject.js.   Fix math to find proportional x to be related to center of other object.
Player.js.  Relocate Player when in vortex of obstacle to move its x position to proportional x

Issue
Game was not supporting different sprite animation on same line.  Code has been altered to add this behavior.
Other observations
There are instance where monkey still distorts.  Like when jumping on Goomba or rapid Jumping.  These seem minor, but would require additional investigation.
File Summary
GameSetup.js - supports an option optional min key/value to be used primarily when start is NOT zero
Character.js - supports frameX starting at min frame
Player.js - animation support for min frame, removed key up extra animation call


services/horizon:  Make LedgerTransaction's Meta a private field

This change transforms
type LedgerTransaction struct {
	...
	Meta       xdr.TransactionMeta
}

into
type LedgerTransaction struct {
	...
	meta       xdr.TransactionMeta
}

Unfortunately I've had to add a getter and a setter:

func (t *LedgerTransaction) UnsafeSetMeta(meta xdr.TransactionMeta), needed for test fixtures
(t *LedgerTransaction) UnsafeGetMeta() xdr.TransactionMeta), needed for db ingestion (see transactionToRow(transaction ingest.LedgerTransaction, sequence uint32)).

As a result the participants processor (participantsForTransaction()) now uses func (t *LedgerTransaction) GetChanges() which constitutes a change of behavior (for the better, I believe, although new participants may be found).
To make sure participantsForTransaction()works with old transactions, GetChanges() now also returns the changes of Meta version 0.
In addition, and for consistency, participantsForTransaction() now uses GetFeeChanges() instead of LedgerTransactions FeeChanges field.
I think FeeChanges should probably be made private in the future.
Fixes #3491

Close in favor of #3561


cannot be build under cargo

i'm writing envoy-mobile-sys and envoy-mobile-rs as hobby projects, in addition to working on py-envoy-mobile. cargo doesn't include cargo-based subpackages while attempting to package + publish.
envoy-mobile depends currently on envoy a55ae7ee8, which has an explicit bazel/external/cargo dir, which is ignored while building under cargo.
any commit after envoy 9aa5c75d6 can be built just fine, as it removes the dependency on a pre-existing cargo dir.
i'm opening this ticket to track fast-forwarding past 9aa5c75d6, which i'm happy to work on to continue to unblock my downstream work

...this is the part where i slink away in shame, because i now see that #1230 was merged two days ago.
closing this issue as it's no longer relevant.

...this is the part where i slink away in shame, because i now see that #1230 was merged two days ago.
closing this issue as it's no longer relevant.


Codes needs cohesive restructuring to make them testable

We have done some refactoring recently to so that we can add structured unit tests. However, there are still some more refactoring need to be done. As we can see some challenges with mocking netlink functions and some side-effects of doing so. see #42
Here's what I suggest we can do to improve the code-base:
We are using netlink library in following pkgs/files:

sriov/sriov.go
pkg/config.go

Here is what I suggest we should do in upcoming days:

Move sriov/main.go into a new cmd/main.go directory – add integration test for this file
Move sriov/sriov.go into new package named sriov into pkg/sriov/sriov.go
Define an Interface as NetlinkManager pkg/sriov/sriov.go with all of the netlink functions that we use in the pkg/sriov/sriov.go –so we can mock them at once & only place in its unit-test file
Move AssignFreeVF() function from pkg/config.go into pkg pkg/sriov/sriov.go so the netlink library only to be imported there. We have to mock it for unit tests only once in here. Netlink no longer needed for config.go

@ahalim-intel I think this has been done at this stage, right?

@killianmuldoon yes, It's done


put captcha on SOTC 2016 submission form

labeled 2016 state of the commons submissions in forms.. please?

Remind me if this is this a Google Form or a Gravity Form or a CIvi form pls? :-)

Gravity!
On Tue, Oct 4, 2016 at 10:57 AM, Rob Myers<EMAIL_ADDRESS>wrote:

Remind me if this is this a Google Form or a Gravity Form or a CIvi form
pls? :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/creativecommons.org/issues/472#issuecomment-251463936,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGTmSx1KdFs5iJiNQ-y8gMz0lJ0Pxbiks5qwpOlgaJpZM4KN9VR
.

--
Jane Park
Director of Platforms and Partnerships
Creative Commons
@janedaily
Get updates: http://bit.ly/commonsnews
Invest in the commons: https://donate.creativecommons.org/

Thanks. I'll take a look after the call.

Let me know when this is done and I'll publish the post after. Thank you!
On Tue, Oct 4, 2016 at 10:59 AM, Rob Myers<EMAIL_ADDRESS>wrote:

Thanks. I'll take a look after the call.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/creativecommons.org/issues/472#issuecomment-251464455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGTmQYgBrYWtGXodlI7fYFpfNnTCOQrks5qwpQFgaJpZM4KN9VR
.

--
Jane Park
Director of Platforms and Partnerships
Creative Commons
@janedaily
Get updates: http://bit.ly/commonsnews
Invest in the commons: https://donate.creativecommons.org/

I've enabled reCaptcha in Gravity on the live site.
reCAPTCHA fields are available in "Advanced Fields".
I've added one to this form but I haven't tested it yet. If you click on the usual Gravity Forms reveal icon at the top right of the field it will show you the styling options if you need to change any.


Allow excluding imports from lll

We have some long imports which exceed our lll length configuration.
We'd like to disable lll from anything inside import ( XYZ ) as there's not really much we can do about these import lengths.
Is there any way this could be added as a configuration?
Thanks!

Implemented on golangci-lint side https://github.com/golangci/golangci-lint/pull/3288

Thank you!


[ENH] Add mne.viz.Brain.remove method

A coherent style would be to have actors added with mne.viz.Brain.add_volume_labels, mne.viz.Brain.add_head, etc. and then they could similarly be removed with a corresponding remove method that removes the meshes from the renderer and deletes them from an internally stored list. There could be some refactoring/general code to share for adding/removing.
Related to https://github.com/mne-tools/mne-python/issues/9584

@GuillaumeFavelier @larsoner


Cannot press a key on Linux Wayland

I'm trying to simply press a key with a minimal example :
use std::thread::sleep;
use std::time::Duration;
use tfc::{traits::KeyboardContext, Context, Key};

fn main() {
    println!("Hello, world!");
    let mut ctx = Context::new().unwrap();
    loop {
        sleep(Duration::from_secs(1));
        ctx.key_click(Key::A).unwrap();
        println!("A pressed");
    }
}

It runs without any error but the A key isn't pressed in practice when I open a text editor for example.  I did the chmod +0666 /dev/uinput command but it still seems to do nothing.  Any idea of what could be wrong ?

I'm really not sure about this one. This worked fine for me. /dev/uinput should work on any Linux distro because it's a part of the kernel. Does anything work or is it all broken? Are there any errors or warnings anywhere? Did following the other permission steps in the README have any effect?

The minimal example only works within XWayland applications for me. I think it's because I'm using swaywm, and it sets $DISPLAY if XWayland is enabled, which looks like it's causing tfc to build the X11 version instead of the Wayland version.
That being said, even when forcing tfc to build the Wayland version it still doesn't work, I get this output & error:
Hello, world!
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Platform(XOpenDisplay)', src/main.rs:7:34
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Ah. This is starting to make a bit more sense now. It seems that the code that checks for X11 doesn't work in all cases.
@notewio From the error message, it looks like you're still running the X11 code path. To force it one way or the other, update build.rs and then do a clean build. At some point I'll update that file to do more robust platform detection. Any further insights on the differences between the two would be appreciated!

Deleting the platform detection in build.rs gives a couple of compile errors:
error[E0308]: mismatched types
  --> The-Fat-Controller/src/command/execute.rs:62:23
   |
62 |             return Ok(true);
   |                       ^^^^ expected `()`, found `bool`

error[E0308]: mismatched types
  --> The-Fat-Controller/src/command/execute.rs:71:28
   |
71 |             _ => return Ok(false)
   |                            ^^^^^ expected `()`, found `bool`

warning: unreachable call
  --> The-Fat-Controller/src/command/execute.rs:66:9
   |
66 |            match self {
   |   _________^
   |  |_________|
   | ||
67 | ||             UnicodeCharDown(_) => panic!("UnicodeKeyboardContext is not implemented"),
68 | ||             UnicodeCharUp(_) => panic!("UnicodeKeyboardContext is not implemented"),
69 | ||             UnicodeChar(_) => panic!("UnicodeKeyboardContext is not implemented"),
70 | ||             UnicodeString(_) => panic!("UnicodeKeyboardContext is not implemented"),
71 | ||             _ => return Ok(false)
72 | ||         }?;
   | ||_________-^ unreachable call
   | |__________|
   |            any code following this `match` expression is unreachable, as all arms diverge
   |
   = note: `#[warn(unreachable_code)]` on by default

error[E0308]: mismatched types
  --> The-Fat-Controller/src/command/execute.rs:74:12
   |
74 |         Ok(true)
   |            ^^^^ expected `()`, found `bool`

error[E0308]: `?` operator has incompatible types
   --> The-Fat-Controller/src/command/execute.rs:141:12
    |
141 |         if self.execute_unicode(ctx)? {
    |            ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `bool`, found `()`
    |
    = note: `?` operator cannot convert from `()` to `bool`

error[E0599]: no variant or associated item named `COUNT` found for enum `key::Key` in the current scope
   --> The-Fat-Controller/src/linux_wayland/mod.rs:40:33
    |
40  |         for k in 0..crate::Key::COUNT {
    |                                 ^^^^^ variant or associated item not found in `key::Key`
    |
   ::: The-Fat-Controller/src/enum.rs:110:9
    |
110 |         pub enum $name {
    |         -------------- variant or associated item `COUNT` not found here
    |
    = help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
    |
1   | use crate::r#enum::Enum;
    |

Some errors have detailed explanations: E0308, E0599.
For more information about an error, try `rustc --explain E0308`.
warning: `tfc` (lib) generated 1 warning
error: could not compile `tfc` due to 5 previous errors; 1 warning emitted

Not sure if the fixes I did for these were actually correct or not but the minimal example works now. I put my fixes in a fork here https://github.com/notewio/The-Fat-Controller

@notewio I had a look at your fork and tested it myself. Would you like to open a PR? There are some minor things I'd want you to change (primarily addressing the Clippy warnings). I have noticed that there are Clippy warnings in code that you didn't touch but don't worry about that.

Thanks to @notewio's contribution, this has been fixed in version 0.6.2.


Factorize all --json option decorators

Defining --json in 3 different places is a bit too much :)
Move utils.json_output_option_decorator() to common_options, renaming it json_option(). Make it use create_ctx_callback().
Add a use_json() helper function to common_options, to know if --json has been set.
Uses these new functions in:

cmd.iac.scan
cmd.secret.scan.secret_scan_common_options
cmd.status
cmd.quota

Codecov Report

Merging #553 (61c9d3b) into main (885cf56) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #553      +/-   ##
==========================================
- Coverage   93.79%   93.78%   -0.01%
==========================================
  Files          84       84
  Lines        3866     3863       -3
==========================================
- Hits         3626     3623       -3
  Misses        240      240

Flag
Coverage Δ

unittests
93.78% <100.00%> (-0.01%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ggshield/core/utils.py
97.66% <ø> (-0.03%)
:arrow_down:

ggshield/cmd/common_options.py
97.67% <100.00%> (+0.17%)
:arrow_up:

ggshield/cmd/iac/scan.py
98.59% <100.00%> (ø)

ggshield/cmd/quota.py
65.62% <100.00%> (-1.05%)
:arrow_down:

...ield/cmd/secret/scan/secret_scan_common_options.py
100.00% <100.00%> (ø)

ggshield/cmd/status.py
90.90% <100.00%> (-0.40%)
:arrow_down:


Preserve navigation scroll position/toggle state on page change

What version of starlight are you using?
0.4.1
What version of astro are you using?
2.7.4
What package manager are you using?
npm
What operating system are you using?
Linux (WSL)
What browser are you using?
Chrome/Edge/Firefox
Describe the Bug
If you have a very long set of navigation links, the scroll position resets on page transitions. The same is true for toggle state, which makes the page look jumpy on transitions even without a lot of pages. It's not the end of the world but it is annoying. It would be preferable to maintain these across page changes.
This can be done using some script and it's not too heavy weight. It would be nice if this were included. Alternatively if there was a way to add custom scripts to the default layout -- something like customCss that would let me insert an Astro component or even just some TS -- I could do it myself without forking starlight.
Link to Minimal Reproducible Example
No response
Participation

[X] I am willing to submit a pull request for this issue.

Thanks for the issue. Would be nice to improve this indeed.
For a simple solution in your own project, you can add scripts using the head config option: add your JS to the public/ directory, and then add it to your site’s head in astro.config.mjs:
  head: [{ tag: 'script', attrs: { src: '/my-script.js' } }],

Sorry, I missed that. I thought I had scoured for places to insert stuff.
I would still prefer a way to inline it (I know I can inline it in that head object, but I mean as a proper module) but this works great for the time being. If anyone is interested here's my working example (scroll position only):

(() => {

  const key = 'toc-position';

  let timeout = 0;

  let position = { scrollTop: 0 };

  const sidebar = document.querySelector('#starlight__sidebar > .sidebar-content');

  if (sidebar) {

    const data = sessionStorage.getItem(key);
    if (data) {
      try {
        const obj = JSON.parse(data);
        position = {
          ...position, ...obj,
        };
        sidebar.scrollTop = position.scrollTop || 0;
      }
      catch (err) {
        // ...
      }
    }

    sidebar.addEventListener('scroll', () => {
      position.scrollTop = sidebar.scrollTop;
      if (!timeout) {
        timeout = window.setTimeout(() => {
          sessionStorage.setItem(key, JSON.stringify(position));
          timeout = 0;
        }, 100);
      }
    });

  }

})();

I just tried this  and it works great. Thank you @duncanwerner for sharing.
Now the only issue is that the open-state of the detail-elements is not saved. After clicking on a menu item, all previously closed ones open again.
This means that the scoll position is not correct in this case.
Am I missing something or is it not possible to save this state at the moment?

Here's our current version, which saves the detail state:
https://gist.github.com/duncanwerner/d49fd9574ecd7a26d1febd0077dd012b
Example:
https://docs.treb.app
You are welcome to use it, just remember that it is fragile to future changes in Starlight.

I wonder if @swup/astro with morph config would do the trick

Wondering, any progress on this?

I had a similar issue, and also worse, with websites having a high pages count, the menu building on each page slowed down my build time considerably. So I designed this client side shamefully injected menu with vanilla js, the advantage is the open closed state storage https://github.com/MicroWebStacks/astro-big-doc/blob/main/src/layout/client_menu.js
but from Starlight I would expect more, closed state and position indeed and I was wondering if it is not possible to keep the whole menu state with ViewTransition.

Any reasons why the solution of @duncanwerner couldn't be merged into the project? Looks like a solid implementation to me.


Lab1

Fixes #162
Review of colleague's PR #
Changes proposed in this PR:

Implement Lab1 Fibonacci numbers
Implement Lab1 NegaFibonacci numbers
Test Lab1

Codecov Report

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

@@          Coverage Diff          @@
##           master   #165   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      2    +1
  Lines           2     14   +12
=====================================
+ Hits            2     14   +12

Impacted Files
Coverage Δ

01_fib/CameronSchafer/fib.go
100% <100%> (ø)

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 7984f47...f21ad0e. Read the comment docs.

This looks good to me the tests are passing and seem to cover most interesting edge cases except maybe 0
I had a suggestion and question for the author but no required changes.


Filenames should be Statamic id when slugs are not required

When a slug isn’t required on a collection, the filename created for each entry should be the Statamic id. Currently, the filename is a slugified version of the title.
Ideally this would be detected from the collection’s settings. I believe this is a fairly recent option available in Statamic.
Current workaround:
– do the import
– manually rename each new entry’s filename with its id
Thanks. Fantastic tool otherwise!

Seems like it shouldn't be too hard to add. Don't have a lot of time currently to work on issues, so if you're willing to try out a PR it would be very welcome!

I wish I could write that PR but I wouldn’t know where to start.
Would you considered sponsored development on this?


[csrng, testutils] Refactor testutils to return status_t for all csrng

Description
See https://github.com/lowRISC/opentitan/issues/17495 for more details.

We can close this since all entropy complex testutils are in one library I believe? and the task is covered in #17530.

Looks like there is a csrng testutils lib, so reopening.


Memory leak while using ImageDataGenerator flow function

When I using the ImageDataGenerator flow function to train the model (train_on_batch), the memory will leak. My keras version is 2.0.1, but the 1.2.0 version does not enconter this problem. Code:
def extract_imagelist(target_path):

     with open(target_path, 'r') as f:
            images, labels = [], []
            for l in f.readlines():
                l = l.strip('\n').split()
                images.append(l[0])
                labels.append(int(l[1]))
     image_len = len(images)
     all_images = np.empty([image_len, 224, 224, 3])
     all_labels = []
     for i in range(image_len):
           img = image.load_img(images[i], target_size=(224, 224))
           img = image.img_to_array(img)
           img = np.expand_dims(img, axis=0)
           img = preprocess_input(img)
           lab = labels[i]
           all_images[i, :, :, :] = img
           all_labels.append (lab)
     all_labels = to_categorical(all_labels)
     return all_images, all_labels

files_list = "train.txt"

X, Y = extract_imagelist(files_list)

datagen = ImageDataGenerator(horizontal_flip=True)

net.compile(optimizer=SGD(lr=0.001, momentum=0.9), loss='categorical_crossentropy')

for e in range(10):
      batches = 0
      for X_batch, Y_batch in datagen.flow(X, Y, batch_size=16):
            loss = net.train_on_batch(X_batch, Y_batch)
            if batches % 20 == 0:
	        print ('Epoch', e, 'iteration:', batches, 'loss:', loss)
            batches += 1
            if batches >= len(X) / 16:
                break'

I'm having some memory leak with ImageDataGenerator. I'm using fit_generator.
It's strange; I'm running a few different configurations, and some of them leak while others don't. I've switched between multithreading, multiprocessing, and single-thread (the default); it leaks no matter what I choose.
As keras/image.py contains nothing but numpy processing, which does not invoke much references, I don't see how this can leak.

To be sure, when using a pure ImageDataGenerator and the model constructed with pure Keras layers, the memory should not consistently grow after an epoch or two, right? There wouldn't be that much thing to be in memory.

@Namnamseo Did you solved this issue?

I haven't.
I tried training each batch manually, measuring memory with objgraph before and after the train_on_batch.
Install objgraph by pip or such, and try:
import objgraph

for e in range(10):
    batches = 0
    for X_batch, Y_batch in datagen.flow(X, Y, batch_size=16):
        print('BEFORE')
        objgraph.show_growth()
        loss = net.train_on_batch(X_batch, Y_batch)
        print('AFTER')
        objgraph.show_growth()
        if batches % 20 == 0:
            print ('Epoch', e, 'iteration:', batches, 'loss:', loss)
        batches += 1
        if batches >= len(X) / 16:
            break

For me, after the first call, all objects were garbage collected. In other words, nothing came after AFTER. So it means that no Python object is leaking. It might be somewhere in the backend(TensorFlow or Theano), or even (but possibly not) CUDA.


Right click context menu on tabs to offer actions like: "Close other tabs"

feeling the pain of this missing feature in multi tab client reporting app

Closing this ticket - we would like to revisit this in the context of the big tab-switcher rethink underway in #3671


Crash on Undercover (Update 108)

Seems to be a crash caused by Goonmod related to enemy spawning in the latest update.
Application has crashed: C++ exception
[string "lib/managers/group_ai_states/groupaistatebe..."]:404: attempt to index field '_tweak_data' (a nil value)
SCRIPT STACK

Callstack:
     payday2_win32_release  (???)     ???
     payday2_win32_release  (???)     ???
     payday2_win32_release  (???)     ???
     payday2_win32_release  (???)     zip_get_name
                     ntdll  (???)     RtlFreeHeap
                     ntdll  (???)     ZwQueryVirtualMemory
                KERNELBASE  (???)     VirtualQueryEx
                KERNELBASE  (???)     SetUnhandledExceptionFilter
                KERNELBASE  (???)     SetUnhandledExceptionFilter
     payday2_win32_release  (???)     ???
     payday2_win32_release  (???)     zip_get_name

I also get this same error on Train Heist, and I think all heists TBH.

As far as I can tell it seem to be related to snipers, and maybe swat van turrets. First tested on first world bank, and it seem to crash right as they spawn or take aim. Did a second test  on four stores, to see if was just the snipers, and it crash right as things got loud. the crash log end up a bit different
[string "lib/managers/group_ai_states/groupaistatebe..."]:3311: attempt to index field '_tweak_data' (a nil value)
basically the same line but a 3311 instead of 404. btw I tested the snipers with the mod disable and they spawn perfectly fine but hadn't tested the swat van with out mods yet.(wasted to much time on this already) also hadn't tested silent runs because I'm not that good at that. Hopefully this help narrow down the error search.

Until Goonmods updated, here's a tempoary fix:
Go to PAYDAY 2 > mods > Goonmod > goonbase.lua.

Thanks @Afbg123, that did fix the instant crash.
However, I just crashed on Murky Station. Haven't crashed for a long time. However, here is the crash log proving it was a GoonMod fault:

Current thread: Main
Script stack:
update()  lib/units/beings/player/states/playerstandard.lua:332
update()  @mods/GoonMod/lua/PlayerStandard.lua:42
lib/units/beings/player/playermovement.lua:264
()  =(tail
call):-1  ()
=(tail
call):-1

Thanks, @Afbg123. That fixed the instant crashes, however I just crashed at random on Murky Station. The crashlog blames it on GoonMod, see below.
`-------------------------------
Callstack:
     payday2_win32_release  (???)     ???

Current thread: Main
Script stack:
update()  lib/units/beings/player/states/playerstandard.lua:332
update()  @mods/GoonMod/lua/PlayerStandard.lua:42
lib/units/beings/player/playermovement.lua:264
()  =(tail
call):-1  ()
=(tail
call):-1
-------------------------------`
Or for an easier read, here's a picture: http://i.imgur.com/zQWMTJt.png

Should be fixed in r32. @iguaan please create a separate issue if you are still experiencing your crash.


Train on custom dataset

@jacklanchantin @qiyanjun @jakegrigsby
How to implement C-Tran on custom dataset.
I have the information like
img_123.jpg - dog, cat, lion
img_124.jpg - cat,lion
etc...
Is there some specific format I need to follow to train with C-Tran

Are you able to download the example datasets (coco, voc)? If so, you should be able to simply match the format of those datasets.

你好，请问数据集这块您解决了吗，我也遇到同样的问题，请教一下

I have the same problem and I am not able to download the dataset.

I've updated the urls. You should at least be able to download the original datasets.


[Task]: Static Schema Definition docs are not in nav

What needs to happen?
The Static Schema Definition documentation pages are not included in the navigation:

https://hop.apache.org/manual/next/pipeline/transforms/schemamapping.html
https://hop.apache.org/manual/next/metadata-types/schema-file-definition.html

Additionally, there's some room for improvement in the documentation
Issue Priority
Priority: 2
Issue Component
Component: Documentation

.take-issue


Updates to schoology sso

Record where the schoology auth request comes from, and use that host
instead of the default. Also, change the default to app.schoology.com
instead of www.schoology.com.

Looks reasonable to me.  Can you test it out on itsi-master-staging?  You could just deploy this branch there to test it.


Add android-Ultra-Pull-To-Refresh

Add android-Ultra-Pull-To-Refresh

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: $500k Worth of Airdrop is Ready, here's how to Claim

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

3. Share the Excitement on Twitter:

Spread the word about claiming your free tokens!

Tweet: Share on Twitter

Winners: @khushmeeet, @shohi, @iEthereal, @WreathCrystal, @huangfuxin, @aoxee8, @serenefall, @JYisus, @Codefreyy, @bigtreeljc


fix: Correct timeout value in tests to match #55

BREAKING CHANGE: Backend service now inherits the same timeout used for health checks, instead of the former hardcoded value of 10 seconds.

Thanks for the PR! 🚀✅ Lint checks have passed.


Robert Longson: Watch considir.com

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

considir\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Error on Case.net path

Update: Error on case.net path as either attorney entering appearance or just as tenant
Defend Against An Eviction.pdf

Another version of the #168 bug.  I made it so that it won't ask about the docket if the county isn't set by geocode.

I changed the url encode to use the trial_court.county, which fixed the problem
However, the link goes to a screen that says
Location Unavailable
If "%0A" is removed from the end of the url it works

That worked


Fixes #518: Add dark mode and icons

What does this PR do?
Hello.
Instead of adding a new app I made some improvements to the "Meme Share Java" Android project.

Add dark mode using DayNight configuration
Add drawable icons to the buttons
Remove unused imports
Improve code format and readability
Add visibility modifiers to attributes

I also updated the readme file of the project, with suggestions for others to contribute.
Test Plan
I tried the app on my physical smartphone and one android emulator.
Have you read the Contributing Guidelines?
Yes, I did.
Related issue
#518

@kunal299 please review this

Hello @dubesar @kunal299
If you are out of time these days you can add the hacktoberfest-accepted label to the PR and then review later.
This is what Hacktoberfest recommends: https://hacktoberfest.digitalocean.com/hacktoberfest-update

Hello @dubesar @kunal299
If you are out of time these days you can add the hacktoberfest-accepted label to the PR and review later 😅
This is what Hacktoberfest recommends: https://hacktoberfest.digitalocean.com/hacktoberfest-update
Thanks!


Slow down webpack rebundle when migrate from 0.5 to 0.6

I recently migrated from version 0.5 to 0.6 and found that the webpack rebundle time increase from 500ms to 3000ms.
I have no idea why this happen, and don't know how to fix it.
Does anyone else has the same problem too?

The problem is caused by less-loader ...

@mofas these font icon references were removed in 0.7.0.


Voice Quality Issue During Calls Using JavaScript SDK

I'm having trouble with the Voice JavaScript SDK when making calls to customers or clients. While talking to them, their voices often become unclear or even cut off completely. But when I listen to the recordings afterward, their voices sound fine.
When I'm on a call, the other person's voice sometimes gets hard to hear or disappears altogether.
This problem keeps happening every time I make calls using the Voice JavaScript SDK.
This issue is causing a lot of trouble as it's difficult to have good conversations with clients. I really need help fixing this problem so I can communicate better.
I would really appreciate it if you could help me solve this problem. If you need more information or anything else from me, just let me know.
Thank you,

Have u tried making call from another device, switching ur network conn


Failed TC with Grocy 3.3.0

I have changed the test configuration to the demo instance of Grocy by modifying the test_const.py file and run the pytests against it.
However, the result of the test was not really successful:
test/test_battery.py .F.                                                                                [  3%]
test/test_chores.py FF...                                                                                [  8%]
test/test_generic.py F......                                                                                [ 15%]
test/test_grocy.py ..................................                                                                                [ 50%]
test/test_grocy_api_client.py ....                                                                                [ 54%]
test/test_meal_plan.py FF.F                                                                                [ 58%]
test/test_meal_plan_sections.py F..                                                                                [ 61%]
test/test_misc.py .                                                                                [ 62%]
test/test_product.py FFF..F.                                                                                [ 70%]
test/test_product_groups.py F                                                                                [ 71%]
test/test_shoppinglist.py F......                                                                                [ 78%]
test/test_stock.py F.F..                                                                                [ 83%]
test/test_system.py F                                                                                [ 84%]
test/test_tasks.py F...                                                                                [ 88%]
test/test_users.py .F                                                                                [ 90%]
test/test_utils.py .........                                                                                [100%]

=========================================================================================== FAILURES ===========================================================================================

Maybe the tests should be updated to deal with the most recent demo instance of Grocy? This might also uncover missing feature implementations.

@SebRut what would you recommend on how to proceed?

In general, one would delete all files in tests/casettes and re-run the tests to re-record responses. After that, all failing tests have to checked (and changed if needed) for actual errors or simply assertions not matching responses anymore.


Manually ending a game doesn't execute logic to determine a winner

/end will only have a team win if specified as an argument.

Ending with /timelimit should use the win logic
He said that it did not

Check #397

Closing, as setting the time limit does execute the logic for this. #397 will be fixed soon and #394 will also be fixed.


Ui extra assets recurse

Added support in uploading from disk extra static assets which reside under a sub-folder such as:
x/y/z/my.css

Can you please rebase on master ?


Move top accounts to supply page and add filter

Fixes: https://github.com/solana-labs/explorer/issues/141
Fixes: https://github.com/solana-labs/explorer/issues/146
Changes:

Add largest accounts to supply page
Redirect /accounts/top to /supply
Add filter button (and url param) for showing "all", "circulating", and "non-circulating" largest accounts
Add line for "non-circulating" supply sol count to "Supply Overview"

Or at least, that top URL redirects to the circulating filter?

Oh I thought we wanted the default to be all accounts. I'll switch it to circulating then


Update Composer dependencies (2022-01-13-00-10)

Visual regression test passed!
View the visual regression test report


Add missing closing bracket in sample

By analyzing the blame information on this pull request, we identified @sahrens and @grabbou to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!


[Question] Volume mapping for Nomad

Has anyone tried volume mapping on Docker containers on Nomad (https://www.nomadproject.io/) and share some experience?

Hello @linusviking!
It looks like the relevant thread in Nomad is https://github.com/hashicorp/nomad/issues/150
The idea was being thrown around for how to actually enable this. Today there is no support since Nomad doesn't have persistent support and it does not allow arbitrary parameters when running docker run commands.


Website/Hugo: Update readme & package json links

Update readme with more info about the assets folder: typescript, scss & icons
Fix broken links in package.json

Closes 4ec89d6 as merged.


Add support for PEQ 3300-P contact sensor

This PR adds support for the PEQ 3300-P contact sensor.
I looked it up and centralite manufactured this for PEQ and smartthings seems to treat it the same as the 3300-S.  I tried it out and this config allowed me to add it.

Thanks!


Add template for rhel6

This PR adds a template that supports the redhat-6 platform. It is very similar to the centos-6 one except I changed it to use the node_binary location like in the default template.

:+1: