Support local images

When I try to convert a slide deck, the images used in my markdown cannot be found by md2googleslides:
Unable to generate slides: Error: Invalid URI "images/PyMC3.png"

This is despite the images directory being in place in the current directory.

The Slides API, and hence this tool, only supports publicly hosted image URLs at the moment. Changing this to a enhancement request.

It's perhaps beyond the scope of this project, but one option would be to upload the local files to Drive first, then have the imageUrl field refer to the Drive media view, with the access token embedded as a query parameter.
Using the same API in python, the code looks something like
# upload to Drive
response = drive_service.files().create(media_body=local_image_filename).execute()
url_with_auth = drive_service.files().get_media(fileId=response['id']).uri + '&access_token=%s' % credentials.token

slides_service.batchUpdate(body={'requests': [{
      'createImage': {
          'url': url_with_auth,
        }
      }]})

Google Slides stores the original URL of the inserted images and exposes that data to collaborators, so that approach could lead to the access token being shared more broadly than desired. You could instead temporarily make the image world-readable, avoiding the need for the access token, but that isn't the most secure and not every G Suite user is allowed to share files outside their domain.

Yep, have this change ready locally, but because the access token is leaked I need to find a different solution. Unless the Slides API changes to support specifying images by Drive ID instead of URL (have an open feature request for it,) all the other solutions I can think involve converting this into a hosted service. That has its own set of issues though and likely won't happen any time soon.

Got it. I hadn't realized that the url persists after the image is uploaded. I'm not familiar enough with Google's refresh tokens... I take it they persist for longtime? Can we request a short-lived token?
Using a short-lived token seems slightly less-bad than temporarily making the image world-readable since you don't have to worry about domain restrictions on sharing publicly and the script's untimely death won't leave resources dangling in the wild.

One hacky solution I'm playing around with:

Get a list of current collaborators
Revoke all permissions on the destination slides
Request a new OAuth token (and don't store it)
Generate the slides
Revoke the OAuth token from step 3 (GET https://accounts.google.com/o/oauth2/revoke?token=, no need to be logged in)
Restore collaborators

It's.... not pretty. @sqrrrl do you have a link to the open feature request in Slides API? This seems like such an oversight!

I'm also considering using something like file.io, but am a little concerned about uploading data to a 3P. Maybe doable with an explicit opt-in (CLI flag --use-fileio), will see...

Oooooh, found a nice little hack :)
Drive has a nice feature that if you try to download a file with the access_token in the query parameter, it redirects to a locked domain (ephemeral domain with auth encrypted and signed in the URL). That URL is safe to use since it's valid only for the particular file and doesn't directly expose the access token.
So logic becomes:

Upload file
Request download in client w/access_token but don't follow redirect
Capture the redirect URL and use that in as the image source URL

Yay :)

Previous mentioned hack isn't viable (can't rely on it long term.)
Ended up using https://file.io for ephemeral hosting with an explicit ack on the command line (--use-fileio). Fixed in master, will be in next release (0.5). Should get around to pushing that shortly.


I just needed to be answered few basic questions !

can i go for graduate level courses on MIT OCW after finshing all these stuffs ?
if i wish to learn any new/other programming language do taking these courses will be worthy in that case ?

Go for it -- I think you should be well prepared but it's normal for graduate students to take some undergraduate courses to get the background knowledge needed for a graduate course they want to take
I'm not sure what you mean by this question. If you're asking whether the current courses prepare you well enough to learn another new programming language, the answer is yes. You will be especially well-prepared once you've taken the Programming Languages courses.


Add groupId to api for data store creation in aqueduct

Description
Add groupId to api for data store creation in aqueduct.

i'd like to see an API council review of the planned usage here, as its not clear me how customer will use this.

i'd like to see an API council review of the planned usage here, as its not clear me how customer will use this: https://eng.ms/docs/experiences-devices/opg/office-shared/fluid-framework/fluid-framework-internal/fluid-framework/docs/dev/resources/design-councils#api-council

Sure, I will go through the link that you mentioned.

Closing this PR based on the discussion that we are not planning to add these in aqueduct layer yet.


No Interaction of dependent select field after being re-enabled

Package
filament/filament
Package Version
3.2.83
Laravel Version
11.9.1
Livewire Version
3.5.0
PHP Version
8.3.2
Problem description
When trying to disable a field based on a condition, like whether a previous field is filled or not the disabled select field is not interactable after the element itself was "enabled".
I also tried using the ->native(false) option but in both cases the same issue occurs.

Expected behavior
The select field should be interactable and behave as like it would when it wasn't disabled.
Here an example of how it should work by providing a default state for the continent field:

Steps to reproduce

Navigate to Customers
"Edit" any record from the table
Click the "New Address" button
Select any Continent
Issue occurred

Reproduction repository
https://github.com/dev-idkwhoami/filament-demo/tree/bug/dependent-disabled-select-fields
Relevant log output
No response

https://github.com/filamentphp/filament/issues/11289,
https://github.com/filamentphp/filament/issues/10263, https://github.com/filamentphp/filament/issues/8951, https://github.com/filamentphp/filament/issues/8935, https://github.com/filamentphp/filament/issues/8097, https://github.com/filamentphp/filament/issues/3068


Update project tt_um_a1k0n_demo (a1k0n/tt08-vgademo)

Update project tt_um_a1k0n_demo to commit a1k0n/tt08-vgademo@587fa746529ad07937aacf132ac138867c9f07c7
Project title: vgademo
Tiles: 1x2
Workflow: https://github.com/a1k0n/tt08-vgademo/actions/runs/10271229114

@a1k0n please put something more meaningful in info.yaml and submit another revision through https://app.tinytapeout.com


The side bar (the dark bar in the left)

If it'd be bigger than it now I think it's gonna be better :)

I kind of agree with you on this one, however, we opted into this size because more of the team seemed to like this size better including the designer @moradtaleeb and @RashaHussein


(AzureCXP) fixes MicrosoftDocs/azure-docs#302325

We made changes in line no: 64
Note: Space provided Before 2024-02-01

#sign-off


Draft: URL whitelist filter

first step to facilitate further discussions

hi @maditya , pls see if you have early comments on the whitelist xss filtering design.
the yuwlFactory() allows a number of options as stated in the comment block.
say, to use the most conservative one, we can do yuwl = yuwlFactory().
to check against if a URL must carry example.com and www.example.com, we can do yuwl = yuwlFactory(false, false, false, ['example.com', 'www.example.com'])
finally, yuwl('http://example.com')

what if a user wants to allow https://www.yahoo.com but disallow http://www.yahoo.com ?

have we considered implemeting it with a state machine as mentioned in the specs?

can we also allow configurable set of schemes? users might want to have other common schemes like mailto, xmpp or even their own custom schemes
what if a user wants to allow https://www.yahoo.com but disallow http://www.yahoo.com ?

similarly, can you suggest an interface to config this? I can think of:

['https://.yahoo.com', 'https://.flickr.com', 'http://*.flickr.com'] as allowHosts, or call it allowOrigins;
a separate array to take allowProtocols?

have we considered implemeting it with a state machine as mentioned in the specs? with regexes, we might miss out on something.

I've thought of that too. the most favorable reason of using regexp is that it consumes much less code size. The current whitelist-based regexp let us assert a stricter grammar than the specs. Say, the specs allows ipv6, but I suspect we may not need that in the near future, and feel like that's what we can miss out.

https://github.com/yahoo/xss-filters/commit/7809b14d8ae7785a40149d40926df2e3ad0e259a handled the comments.
some example use cases:

yuwlFactory({subdomain:true, hosts:['yahoo.com']})('http://www.yahoo.com') returns http://www.yahoo.com. Without the config, it returns unsafe:http://www.yahoo.com
yuwlFactory({protocols:['https', 'http', 'mailto'<EMAIL_ADDRESS>returns<EMAIL_ADDRESS>Without the config, it returns<EMAIL_ADDRESS>

hi @maditya, here's the major update to the URL processor. the url filter is well-documented.

the URL filters is now located at https://github.com/yahoo/xss-filters/pull/53/files#diff-dcfb674f6f2920a2de596e9d601901e6R38
it's then further enhanced to support base URL processing at https://github.com/yahoo/xss-filters/pull/53/files#diff-0c747b8d943a7352fc80efadaadc41ccR80
very much encouraged to start with looking at the test files: https://github.com/yahoo/xss-filters/pull/53/files#diff-80baed21d72496a71c7d700bf7d0092c and https://github.com/yahoo/xss-filters/pull/53/files#diff-a26f636f2aa516e8fddca465f4ecdcc4R14

this covers all the URL use cases so far known to me. pls check/review. thanks :)


Send Formatted Stack Traces

Right now this package only sends string messages. You lose out on lots of good stuff like grouping, linking to source files, and tons of other goodies by underusing the API!
The docs are here: https://rollbar.com/docs/api/items_post/
What you're looking for is the child of body. Right now you send { message: { body: "STRINGIFIED EXCEPTION" } }. What you ought to be sending is the trace or trace_chain.

Fixed in #19.


Update DDEV install instructions for pkg.ddev.com

pkg.ddev.com is the new CNAME for packages; update it.
Report of a typo in https://discord.com/channels/664580571770388500/1087760493986467871/1094750674031497256 - apparently happened during drud/ddev changeover.

This is related to the same set of changes for the docs:

https://github.com/ddev/ddev/pull/4808

Safe to merge now, @rfay?

I tested, already works, merge away when ready!


clinfo wrongly reports max work group size 256

ROCm 1.7, Ubuntu 17.10, Vega 64:
clinfo reports:
Max work items dimensions:			 3
Max work items[0]:				 1024
Max work items[1]:				 1024
Max work items[2]:				 1024
Max work group size:				 256
In particular the "max workgroup size" does not appear to be correct as I can execute workgroups with larger sizes just fine (tried 512).

This is the result of a number of considerations including performance and misbehaving programs that do not use the reqd_work_group_size kernel attribute and do not call clGetKernelWorkGroupInfo.  By using the kernel attribute, you can indeed have a work group "volume" as high as 1024, but of course this will affect the number of registers available per work-item.

Hi @preda,
This may not be communicated in the clearest way possible, but the max workgroup size being reported here is found by querying the runtime using clGetDeviceInfo(CL_DEVICE_MAX_WORK_GROUP_SIZE). This is runtime-level information, which can't make any guarantees about what kind of kernel will be be asked to run.
The AMD GCN ISA allows any thread to address up to 256 4-byte vector registers; in other words, each thread can use up to 1024 bytes of VGPR space. Every thread in a workgroup must run on the same compute unit (because, for instance, they must be able to communicate through that CU's local memory/LDS). Each compute unit in our existing microarchitectures has 256 KB of registers.
With 256 KB of registers and each thread able to use up to 1 KB, we can only guarantee that a worst-case kernel can run 256 threads on a single CU. The runtime can't say anything more in the general case.
However, if you have a kernel that does not use all of its available register space, the GCN architecture can fit more wavefronts in a workgroup. In the Vega ISA manual, Section 4.3 describes how up to 16 64-wide wavefronts can be combined into a workgroup. This means that, if you limit the kernel's dynamic resource requests such that 1024 threads can fit into a single CU, the hardware can run the larger workgroup.
For instance, if each thread only requests 64 VGPRs, then each thread will only requests 256 bytes of VGPR space. This would allow 1024 threads to fit within a single CU. However, the runtime can only know if this is possible after the kernel has been compiled and it has laid out its VGPR allocation size.
As such, one way to request this "larger than maximum workgroup size" is to call clEnqueueNDRangeKernel() with localWorkSize set to NULL (so that the runtime does not complain about the size being larger than the maximum workgroup size), but writing/compiling the kernel using __attribute__((reqd_work_group_size(X, Y, Z))), where X, Y, and Z make the total thread-count > 256. For instance, __attribute__((reqd_work_group_size(1024, 1, 1))).
The reqd_work_group_size() attribute will tell the compiler that you want to avoid using too many VGPRs and thus 1024 threads from this kernel will be able to fit within a single workgroup and CU.
I'm not an expert at this, so there may be other, deeper, reasons for this decision. However, does this explanation make sense for why clinfo is reporting what it shows?

Firstly, thanks for the explanations, it makes sense, but I still have these observations:
As I understand, there is a different, "hard" workgroup-size maximum, which is 1024. No matter how small a kernel is, the hardware can't execute a workgroup with more that 1024 threads. How is this value queried or reported by clinfo?
So there are two limits:

any kernel can be run with workgroup-size <= 256,
some kernels can be run with workgroup-size <= 1024 (if the kernel VGPR usage allows it).
no kernel can be run with workgroup-size > 1024.

(IMO, I'd still say that "Max work group size" is 1024)
@jlgreathouse:
https://www.khronos.org/registry/OpenCL/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html
says
The work-group size to be used for kernel can also be specified in the program source using the __attribute__ ((reqd_work_group_size(X, Y, Z))) qualifier. In this case the size of work group specified by local_work_size must match the value specified by the reqd_work_group_size __attribute__ qualifier.

Which seems to indicate that local_work_size can't be NULL when using reqd_work_group_size(), at least according to the spec.

I would say that you should look at the Max work items[] outputs of clinfo to understand the maximum work items that the hardware limits you to. This is found by querying each of the dimensions of CL_DEVICE_MAX_WORK_ITEM_SIZES.
You're right, there are multiple limits in play, and that's why it's a bit non-clear exactly what to report for "max work group size". One of the reasons I'm writing out these explanations here is because I don't think you want all of these details dumped to the screen very time you run clinfo. :)
However, if we reported the maximum work group size as 1024, and then the runtime failed when you tried to enqueue a kernel with 512 threads per workgroup, I would wager we would get a torrent of complaints about the runtime being broken. My personal opinion (not any official stance of AMD) is that the current "max work group = 256" description prevents this.
As for the reqd_work_group_size() attribute, my previous post was overly specific to say that you needed to set local_work_size to NULL.
The current ROCm OpenCL runtime allows you to set local_work_size to NULL and it will run with the reqd_work_group_size() of > 256 threads. You can also set local_work_size to the same dimensions as your reqd_work_group_size() attribute and it will work. (e.g. setting local_work_size={1024,1,1} and reqd_work_group_size(1024,1,1)). If you don't set reqd_work_group_size(), however, requesting local_work_size={1024,1,1} will fail.

OK, thanks! I'm going to close this issue. The information contained here is useful, and may be extracted to some documentation.


Warning Patch & Login Enhancement

Remove looping in run.sh
Updated get_inbox
Added "bypass_warning" defaulted to false
PGoAPI warning and Niantic Warning confirmation before bot continues. Can be by pass with "bypass_warning" set to true

👍


refactor: make captcha a real service

Best reviewed commit by commit, since there's some that are not too interesting (example: mass rename).
Paves the way for a future captcha service via interface.

Looks great, my only concern was CSP but it appears we are ahead of that!


[Android] Scaffold with elevation: 0 shows gray line between appBar and body

Steps to Reproduce

Scaffold with elevation: 0  on xiaomi(test on MI 9 and MI CC9 PRO) device

Expected results:
Fluid blue color top appbar
Actual results:
shows gray line between appBar and body on xiaomi ( MI 9 and MI CC9 PRO)devices, run ok on huawei (LYA TL00) and samsung(S10)、iphone simulator
If I set extendBodyBehindAppBar: true,the gray line has gone.

xiaomi-MI 9-android10
xiaomi-MI CC9 PRO-android11
samsung-Galaxy S10-android11

import 'package:flutter/material.dart';

void main() => runApp(new MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return new MaterialApp(
      title: 'Navigation Basics',
      home: FirstRoute(),
      theme: new ThemeData(
        primarySwatch: Colors.blue,
      ),
    );
  }
}

class FirstRoute extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      //shows gray line between appBar and body on android devices
      //If I set extendBodyBehindAppBar: true,the gray line has gone.
      // extendBodyBehindAppBar:true,
      backgroundColor: Colors.blue,
      appBar: AppBar(
        toolbarHeight: 30,
        title: Text('First Route'),
        elevation: 0,
      ),
      body:
          Navigator(
            initialRoute: '/',
            onGenerateRoute: (RouteSettings settins) {
            WidgetBuilder builder;
            switch (settins.name) {
              case '/':
                builder = (context) => SecondRoute();
                return MaterialPageRoute(builder: builder);
          }
        },
      ),
    );
  }
}

class SecondRoute extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      backgroundColor: Colors.red,
      appBar: AppBar(
        title: Text('SecondRoute'),
        elevation: 0,
      ),
    );
  }
}

Logs

[✓] Flutter (Channel stable, 2.8.1, on macOS 12.1 21C52 darwin-x64, locale zh-Hans-CN)

Hi @baihua666, Thanks for filing the issue. I am able to reproduce the issue on Xiaomi Redmi k20 pro (Android 11), With Scaffold. elevation: 0 there is a fine line below the first AppBar, This issue reproduces on almost all android devices except Samsung (as author mentions), and not reproducible on desktop or web. This issue reproduces on stable and the master channel.

output

Pixel 4 Api 30
Pixel 5 Api 29

IOS

I believe this could be related to the gap between the two AppBars, I changed the first scaffold's background color to white the line was still there but less visible.
Android

Scaffold Background Red
Scaffold background white

!

flutter doctor -v
[✓] Flutter (Channel stable, 2.10.1, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.10.1 at /Users/mahesh/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db747aa133 (8 days ago), 2022-02-09 13:57:35 -0600
    • Engine revision ab46186b24
    • Dart version 2.16.1
    • DevTools version 2.9.2

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 98.0.4758.102

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel master, 2.11.0-0.0.pre.582, on macOS 12.1 21C52 darwin-arm, locale en-GB)
    • Flutter version 2.11.0-0.0.pre.582 at /Users/mahesh/Documents/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (28 hours ago), 2022-02-16 00:00:11 -0500
    • Engine revision b09cf53269
    • Dart version 2.17.0 (build 2.17.0-105.0.dev)
    • DevTools version 2.10.0

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-31, build-tools 31.0.0
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.10.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.63.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.34.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 12.1 21C52 darwin-arm
    • Chrome (web)    • chrome • web-javascript • Google Chrome 98.0.4758.102

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Is it possible that https://github.com/flutter/flutter/issues/14288 is related? (And that the grey line only shows up depending on the screen resolution?)

Looks like it is, let's wait until secondary triage takes a look at it.

Thank you for taking the time to file this issue. This appears to be a duplicate of #https://github.com/flutter/flutter/issues/14288. Please track that issue for updates. If you believe I've made an error, please reply here with more details that explain the difference and we'll re-open this issue.


Fail on yaml lint errors

Fixes https://github.com/sds/overcommit/issues/737

I don't really know why the build fails, it seems that it fails on all the tests.
I'm not good enough in Ruby to analyze the issue though.

I don't really know why the build fails, it seems that it fails on all the tests.
I'm not good enough in Ruby to analyze the issue though.

@sds I have rebased on your current master just in case.
The three failing tests are out of my scope, so I don't know what else to do.
In any case, this is what we use right now in production: it correctly handles error messages from yamllint

Note that there are still CI failures that should be pretty easy to fix. Can you have a look?
lib/overcommit/hook/pre_commit/yaml_lint.rb:12:14: C: Layout/TrailingWhitespace: Trailing whitespace detected.
lib/overcommit/hook/pre_commit/yaml_lint.rb:13:36: C: Style/StringLiterals: Prefer single-quoted strings when you don't need string interpolation or special symbols.

OK @sds I did it!

Thank you for your help!


Accurate 3D positions of traffic lights

Is there any way to retrieve accurate 3D positions of the traffic lights? The actor location is not very useful since it's only an approximation (see a reprojection of the actors below)

The OpenDrive maps don't contain traffic lights (even though the format supports this) and the 3D maps are not useful unless one has access to the Unreal Editor as far as I can see.

Hi @joeda
Maybe you can use semantic segmentation alongside the 3D projected depth. Will this be enough for you?


Pipeline correctness check

Check the pipeline before the process and inform the user if he made any mistakes during pipeline creation phase.

We now use a tooltip on the broken pip entry and a red background color instead of the popup.

I guess we can close this issues as the error checking works fine


Invalid memory address or nil pointer dereference

I'm not sure if this is due to the permissions issue or not but the app will only build on the initial run. When I save a file it crashes immediately.
$ refresh run
Refresh (1.3.2)

refresh-log: 2017/04/04 21:37:21 === Rebuild on: :start: ===
refresh-log: 2017/04/04 21:37:21 === Running: go build -v -i -o tmp/sundial (PID: 36468) ===
github.com/jcloutz/sundial
refresh-log: 2017/04/04 21:37:21 === Building Completed (PID: 36468) (Time: 130.067865ms) ===
refresh-log: 2017/04/04 21:37:21 === fork/exec tmp/sundial: permission denied
 ===
refresh-log: 2017/04/04 21:37:45 === Rebuild on: sundial.go ===
refresh-log: 2017/04/04 21:37:45 === Running: go build -v -i -o tmp/sundial (PID: 36534) ===
github.com/jcloutz/sundial
refresh-log: 2017/04/04 21:37:45 === Building Completed (PID: 36534) (Time: 233.783206ms) ===
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x113aeef]

goroutine 1 [running]:
github.com/markbates/refresh/refresh.(*Manager).runner(0xc4200167d0)
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/refresh/runner.go:18 +0x12f
github.com/markbates/refresh/refresh.(*Manager).Start(0xc4200167d0, 0x12ff800, 0xc420018600)
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/refresh/manager.go:72 +0xec
github.com/markbates/refresh/cmd.RunWithContext(0x1215f2b, 0xb, 0x12ff840, 0xc4200145e8)
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/cmd/run.go:38 +0xe6
github.com/markbates/refresh/cmd.Run(0x1215f2b, 0xb)
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/cmd/run.go:27 +0x4d
github.com/markbates/refresh/cmd.glob..func3(0x1314e40, 0x1331208, 0x0, 0x0)
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/cmd/run.go:21 +0x39
github.com/spf13/cobra.(*Command).execute(0x1314e40, 0x1331208, 0x0, 0x0, 0x1314e40, 0x1331208)
	/Users/jeremyc/develop/GoCode/src/github.com/spf13/cobra/command.go:648 +0x231
github.com/spf13/cobra.(*Command).ExecuteC(0x1314c20, 0xc42006e058, 0x0, 0x1316300)
	/Users/jeremyc/develop/GoCode/src/github.com/spf13/cobra/command.go:734 +0x339
github.com/spf13/cobra.(*Command).Execute(0x1314c20, 0x1314c20, 0xc42004bf50)
	/Users/jeremyc/develop/GoCode/src/github.com/spf13/cobra/command.go:693 +0x2b
github.com/markbates/refresh/cmd.Execute()
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/cmd/root.go:21 +0x31
main.main()
	/Users/jeremyc/develop/GoCode/src/github.com/markbates/refresh/main.go:6 +0x20

If you fix the permissions on the tmp folder does it work for you? I've never seen a permission denied error before for this.

So I realized that I think this may be my fault and I wasn't paying attention to the configuration. I have the following folder structure.
| app/
|-- main.go
|-- cmd/
| http/
| sundial.go
| refresh.yml

Full source : https://github.com/jcloutz/sundial
to run it in dev I would run go run app/main.go serve. Can i do that with refresh? This is my config.
ignored_folders:
- vendor
- logs
- tmp
- bin
included_extensions:
- .go
build_path: tmp/
build_delay: 200ns
binary_name: sundial
command_flags: [serve]
enable_colors: true
log_name: "sundial-log"

I'm still getting the same error though, and permissions on tmp is 755 with proper owner/group

Ok, I was able to reproduce this using your app. The problem is you're running refresh run in the root directory. There isn't a main function there, so it's not executable. If you run it inside your app folder then it builds just fine.

@markbates thank you! I had a feeling it was user error :)


Custom Folder for Images save

Hi, first of all thanks for making this amazon plugin. I am using it along with Ionic  and works fine. Only thing i am looking for is how, to override the image storage path to a custom folder.
The purpose is to show the scanned images from that folder. Any idea help regarding this.
Thanks.

Hey @balvinder294
If you just want to create a new folder you can use the response of the plugin and copy it into a new folder that you create. You might be able to use cordova-plugin-file to create a new folder and copy the scanned images (plugin response) there. There is a base64 return option if copying using URI does not work
Cheers and have a nice day :)
Chris
Neutrinos

Thanks for the help and idea, i was about to do something else. Also, so returning base64url will not save the file there in default folder ?

No it will still save. That is being done by the library part. So if you do it this way you will have 2 copies. If you would like you get your hands dirty and dive into the native code.  For android I would suggest looking at the library code and for ios just the plugin code.
Cheers and have a nice day :)
Chris
Neutrinos

Well thanks, i was going for this idea only. I will try to over ride paths in the plugin itself.


feat: multi arch builds

This for some reason is still building amd64 images, I'll probably just run the actions on a pi


Question about the GP-LCB acquisition function

Dear GPyOpt developers,
First of all, thank you very much for the GPyOpt software.
I would have a question regarding the LCB acquisition function.
In the LCB.py, I saw that you referred this acquisition function as the GP-LCB acquisition function. If I understand the program correctly, the exploration weight is set by default to the constant 2. However, in some articles that I saw (Brochu et al.,  arXiv:1012.2599, 2010 and  Srinivas et al., Proc. International Conference on Machine Learning (ICML), 2010), the GP-UCB (used for maximization purposes) is referred as an alternative acquisition function to the UCB (Upper Confidence Bound) whose the exploration weight depends on the number of function evaluations.
Thus, is the exploration weight constant all along the optimization when using AcquisitionLCB or does it change with the number of iterations ?

Hi @AnthonyLarroque you are totally right! We keep that parameter constant for simplicity but in practice the right thing to do is to change it with the number of iterations.
This may be hard to do in GPyOpt and if you want to do that what I recommend is to use Emukit (that we also develop). In this framework, you can handle the number of iterations within the loop state, so it should be pretty easy to implement.

Hi @javiergonzalezh,
Thank you very much for your answer ! I will then take a look at this software.
Except for the LCB acquisition function, could you please, briefly describe me the main differences with GPyOpt ? Is there something more that Emukit can do but not GPyOpt ?

Emukit is much more general-purpose: it is not specializing in bayes opt, you can also do other active learning type of things there. It is also much more modular. Kind of what ModulareBayesOpt class in GPyOpt attempts to do, but in a easier to use way.
In general, if you'd like to implement your own element of bayes opt, say a new acquisition function, or plug a new model, it would be easier and more straightforward for you to do it in emukit than in gpyopt.
THat's the main difference we see between the two, and also why we shifted our focus on emukit

Thank you very much for your answer, it helps me a lot !
Regards,
Anthony Larroque

to round off this discussion i've updated the docsting in https://github.com/SheffieldML/GPyOpt/blob/master/GPyOpt/acquisitions/LCB.py to highlight constant weights and reference the paper

Hi @apaleyes @AnthonyLarroque , as a coincidence I am also looking into this, good to start from your input. I see the Acquisition base class knows an update_parameters method and while it is parameterless the current iteration may be kept internally and incremented at each invocation. Or are there easier ways? I might give it a try.

Something along these lines might work, I'll get feed on the project git, thanks,


Pinned tabs

It doesn't seem to work with as I would expect with pinned tabs. They are treated as part of the current group and are all closed/reopened when switching between groups. I would prefer pinned tabs to be independent of the tab groups. Switching between groups shouldn't change or reload any of the pinned tabs.

You expect the behavior like the previous tab groups extension.
I didn't implement it now as it is a bit trickier to manage with many windows.
However, I agree with you, this behavior is interesting. I will see how to add this feature soon.

+1
Another use case to illustrate the need of this enhancement:
Open a live music streaming session to your favorite provider, pin this tab, switch group => music session get closed. You won't be able to resume this music session.

Resolve in 0.1.4 ( !! need to change the setting !! )

I ticked the box in the settings but if I add a pinned tab, it still gets closed with the group and is not added to the other groups. (using v0.3)

Box ticked: pinned tabs are closed and kept in the closed group
Box Not ticked: pinned tabs stay in the window and only unpinned tabs are closed/opened
You are looking for the second case isn't it ?

hm... Yes, but if I remember correctly (just switched back to FF56), I had the box ticked and as the description said what you write about the unticked box... Maybe just a translation error? I'm using the German version.

yeah, translation issue:
the German line should be:
"message": "Angeheftete Tabs zu Gruppen hinzufügen (Wenn inaktiv, werden diese beim Wechsel einer Gruppe nicht geschlossen)",
There was a "nicht" missing...


Error when submitting new ticket

Installed tickett. run successfully after created categories, priorities and users
got the following error when test by submit a ticket.

Could you please attach the whole call stack that we can see what calls purifier?

[image: MailTag]Here is the full stack
ErrorException (E_WARNING)
mkdir(): No such file or directory

https://app.mailtag.io/link-event?url=https%3A%2F%2Fgoogle.com%2Fsearch%3Fq%3DErrorException%2Bmkdir()%3A%2BNo%2Bsuch%2Bfile%2Bor%2Bdirectory%26id%3D7a3e8818-e9b5-11e7-8f13-06ccf5eaaee6

https://app.mailtag.io/link-event?url=https%3A%2F%2Fduckduckgo.com%2F%3Fq%3DErrorException%2Bmkdir()%3A%2BNo%2Bsuch%2Bfile%2Bor%2Bdirectory%26id%3D7a3e89f8-e9b5-11e7-b374-06ccf5eaaee6

https://app.mailtag.io/link-event?url=https%3A%2F%2Fstackoverflow.com%2Fsearch%3Fq%3DErrorException%2Bmkdir()%3A%2BNo%2Bsuch%2Bfile%2Bor%2Bdirectory%26id%3D7a3e8b38-e9b5-11e7-8898-06ccf5eaaee6
COPY
Application frames (1)
https://app.mailtag.io/link-event?url=http%3A%2F%2Flocalhost%3A8000%2Ftickets%23%26id%3D7a3e8c50-e9b5-11e7-8cc1-06ccf5eaaee6
All frames (71)
https://app.mailtag.io/link-event?url=http%3A%2F%2Flocalhost%3A8000%2Ftickets%23%26id%3D7a3e8d54-e9b5-11e7-bf44-06ccf5eaaee6
70
ErrorException
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Filesystem
/
Filesystem.php
442
69
mkdir
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Filesystem
/
Filesystem.php
442
68
Illuminate

Filesystem

Filesystem
makeDirectory
…
/
vendor
/
mews
/
purifier
/
src
/
Purifier.php
201
67
Mews

Purifier

Purifier
checkCacheDirectory
…
/
vendor
/
mews
/
purifier
/
src
/
Purifier.php
67
66
Mews

Purifier

Purifier
setUp
…
/
vendor
/
mews
/
purifier
/
src
/
Purifier.php
53
65
Mews

Purifier

Purifier
__construct
…
/
vendor
/
mews
/
purifier
/
src
/
PurifierServiceProvider.php
52
64
Mews

Purifier

PurifierServiceProvider
Mews

Purifier

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Container
/
Container.php
749
63
Illuminate

Container

Container
build
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Container
/
Container.php
631
62
Illuminate

Container

Container
resolve
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Container
/
Container.php
586
61
Illuminate

Container

Container
make
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Application.php
732
60
Illuminate

Foundation

Application
make
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Container
/
Container.php
1195
59
Illuminate

Container

Container
offsetGet
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Support
/
Facades
/
Facade.php
159
58
Illuminate

Support

Facades

Facade
resolveFacadeInstance
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Support
/
Facades
/
Facade.php
128
57
Illuminate

Support

Facades

Facade
getFacadeRoot
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Support
/
Facades
/
Facade.php
215
56
Illuminate

Support

Facades

Facade
__callStatic
…
/
vendor
/
kordy
/
ticketit
/
src
/
Traits
/
Purifiable.php
19
55
Kordy

Ticketit

Models

Ticket
setPurifiedContent
…
/
vendor
/
kordy
/
ticketit
/
src
/
Controllers
/
TicketsController.php
220
54
Kordy

Ticketit

Controllers

TicketsController
store
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Controller.php
54
53
call_user_func_array
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Controller.php
54
52
Illuminate

Routing

Controller
callAction
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
ControllerDispatcher.php
45
51
Illuminate

Routing

ControllerDispatcher
dispatch
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Route.php
212
50
Illuminate

Routing

Route
runController
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Route.php
169
49
Illuminate

Routing

Route
run
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Router.php
658
48
Illuminate

Routing

Router
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
30
47
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Middleware
/
SubstituteBindings.php
41
46
Illuminate

Routing

Middleware

SubstituteBindings
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
45
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
44
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Auth
/
Middleware
/
Authenticate.php
43
43
Illuminate

Auth

Middleware

Authenticate
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
42
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
41
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Middleware
/
VerifyCsrfToken.php
67
40
Illuminate

Foundation

Http

Middleware

VerifyCsrfToken
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
39
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
38
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
View
/
Middleware
/
ShareErrorsFromSession.php
49
37
Illuminate

View

Middleware

ShareErrorsFromSession
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
36
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
35
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Session
/
Middleware
/
StartSession.php
63
34
Illuminate

Session

Middleware

StartSession
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
33
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
32
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Cookie
/
Middleware
/
AddQueuedCookiesToResponse.php
37
31
Illuminate

Cookie

Middleware

AddQueuedCookiesToResponse
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
30
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
29
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Cookie
/
Middleware
/
EncryptCookies.php
59
28
Illuminate

Cookie

Middleware

EncryptCookies
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
27
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
26
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
102
25
Illuminate

Pipeline

Pipeline
then
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Router.php
660
24
Illuminate

Routing

Router
runRouteWithinStack
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Router.php
635
23
Illuminate

Routing

Router
runRoute
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Router.php
601
22
Illuminate

Routing

Router
dispatchToRoute
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Router.php
590
21
Illuminate

Routing

Router
dispatch
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Kernel.php
176
20
Illuminate

Foundation

Http

Kernel
Illuminate

Foundation

Http

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
30
19
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
barryvdh
/
laravel-debugbar
/
src
/
Middleware
/
InjectDebugbar.php
65
18
Barryvdh

Debugbar

Middleware

InjectDebugbar
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
17
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
16
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Middleware
/
TransformsRequest.php
30
15
Illuminate

Foundation

Http

Middleware

TransformsRequest
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
14
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
13
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Middleware
/
TransformsRequest.php
30
12
Illuminate

Foundation

Http

Middleware

TransformsRequest
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
11
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
10
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Middleware
/
ValidatePostSize.php
27
9
Illuminate

Foundation

Http

Middleware

ValidatePostSize
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
8
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
7
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Middleware
/
CheckForMaintenanceMode.php
46
6
Illuminate

Foundation

Http

Middleware

CheckForMaintenanceMode
handle
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
149
5
Illuminate

Pipeline

Pipeline
Illuminate

Pipeline

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Routing
/
Pipeline.php
53
4
Illuminate

Routing

Pipeline
Illuminate

Routing

{closure}
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Pipeline
/
Pipeline.php
102
3
Illuminate

Pipeline

Pipeline
then
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Kernel.php
151
2
Illuminate

Foundation

Http

Kernel
sendRequestThroughRouter
…
/
vendor
/
laravel
/
framework
/
src
/
Illuminate
/
Foundation
/
Http
/
Kernel.php
116
1
Illuminate

Foundation

Http

Kernel
handle
…
/
public
/
index.php
52
0
require_once
[image: MailTag]  Sent with MailTag
On Sat, Dec 23, 2017 at 8:04 PM, Balázs Dura-Kovács <
<EMAIL_ADDRESS>wrote:

Could you please attach the whole call stack that we can see what calls
purifier?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thekordy/ticketit/issues/419#issuecomment-353722727,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAwRSW3byg8TQ0z4x-veMGq36DN5Qjduks5tDOxXgaJpZM4RLkGe
.

Too old ticket


xExchWaitForMailboxDatabase: Rename improper function names and add comment based help

Details of the issue
The following functions in xExchWaitForMailboxDatabase need to be renamed to proper Verb-Noun format. When applicable, functions should also be updated to include comment based help per: https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md
GetMailboxDatabase

Note that a function with name GetMailboxDatabase exists in the following modules. We should investigate whether these can be consolidated into a helper function in xExchangeHelper.
xExchMailboxDatabase
xExchMailboxDatabaseCopy
xExchMaintenanceMode
xExchWaitForMailboxDatabase


bump pin to 1.80.0

if it please you, we can bump to 1.80.0.
there are a couple libraries that deprecate c++11 support, locale deprecated c++03, and GIL (which does not yet have a build rule) is dropping c++11 entirely and will soon require c++17.
so, i'm not seeing any obviously breaking changes. if you have a proper testing environment for this set up that would be great. what few libraries i use seem to still work correctly.

Compile is failing for aarch64. It seems aarch64 does not have utime. Not sure why boost-1.79 works.
external/org_boost_filesystem/src/operations.cpp: In function 'void boost::filesystem::detail::last_write_time(const boost::filesystem::path&, time_t, boost::system::error_code*)':
external/org_boost_filesystem/src/operations.cpp:3867:7: error: '::utimbuf' has not been declared
     ::utimbuf buf;
       ^~~~~~~
external/org_boost_filesystem/src/operations.cpp:3867:7: note: suggested alternative: 'futimens'
     ::utimbuf buf;
       ^~~~~~~
       futimens
external/org_boost_filesystem/src/operations.cpp:3868:5: error: 'buf' was not declared in this scope
     buf.actime = st.st_atime; // utime() updates access time too :-(
     ^~~
In file included from external/org_boost_config/include/boost/config.hpp:39:0,
                 from external/org_boost_filesystem/include/boost/filesystem/config.hpp:19,
                 from external/org_boost_filesystem/src/platform_config.hpp:81,
                 from external/org_boost_filesystem/src/operations.cpp:14:
external/org_boost_filesystem/src/operations.cpp:3870:26: error: '::utime' has not been declared
     if (BOOST_UNLIKELY(::utime(p.c_str(), &buf) < 0))
                          ^

You can use https://github.com/iceboy233/lab to test, e.g.
bazel build -c opt --config=aarch64 net/tools:socks-server

it looks like what happened is boost::filesystem changed a check from the unconfigured _POSIX_C_SOURCE >= 200809L to defined(BOOST_FILESYSTEM_HAS_POSIX_AT_APIS), which is configured in the cmake via a compilation check(?) on config/has_posix_at_apis.cpp. this was apparently part of a fix for CVE-2022-21658.
do we have a way to translate this to a bazel platform condition we can select on?

We can choose to always define BOOST_FILESYSTEM_HAS_POSIX_AT_APIS that should always work on modern platforms. I found aarch64 does not have utime but has utimensat. Meanwhile it seems we may need to define more macros correctly to avoid using obsolete implementations.

yeah i agree, it may be best to just always define these and make a note in the README that we just don't support pre-2009 POSIX apis.
there are a big list of these conditional defines here though which i think are, unfortunately, mostly all compile tests? ...it might even be best to figure out how to actually emulate what check_cxx_source_compiles is doing. that's something i would actually like to have

that aside, it looks like filesystem on 1.80 is just... broken? and isn't fixed in that release at all, only after.
initially i found the root cause of the change to the macro check by looking at the develop branch and was confused to find that it's actually incomplete in 1.80.
probably easier to skip the 1.80 release entirely but it is probably still valuable to look into compile checks.

It is broken because utime is used when BOOST_FILESYSTEM_HAS_POSIX_AT_APIS is not defined but <utime.h> is not included when _POSIX_C_SOURCE < 200809L. Define BOOST_FILESYSTEM_HAS_POSIX_AT_APIS and it will just work. However I'm not sure if it should be defined on Mac, or it can be defined on Windows, and I don't have those environments to test with. My guess is to define it for non-Windows:
defines += select({
    "@platforms//os:windows": [],
    "//conditions:default": ["BOOST_FILESYSTEM_HAS_POSIX_AT_APIS"],
})

there are so many other feature flags in there that should probably also be set...

Closing as already bumped to 1.83.0 . Creating https://github.com/iceboy233/boost/issues/18 for filesystem flags.


Breakpoints ignored at initial "launchE: Need to manually "reload" firefox once

Steps to reproduce:

Have some breakpoints
Start with "Launch index.html" or "Launch localhost"

Expected:
3. VS Code stops at the Breakpoints when Firefox is launched and runs the code.
What actually happens:
I need to manually hit "Reload" () in Firefox first. Then the VS debugger kicks in. It should already kick in when initially loaded.

This is a weakness of the Firefox debug protocol: VSCode can't tell Firefox about breakpoints in a file before the execution of that file starts. When the request for setting breakpoints is processed by Firefox, the line for which the breakpoint is being set has already been executed.
So I can't fix this problem, but I have now documented it in the Troubleshooting section of the Readme file.

This is a weakness of the Firefox debug protocol

Mind opening a bug report at BMO about this?

@hbenl Seriously, I think it would be great if you could file a bug on bugzilla.mozilla.org. I could do it, but I am sure you can better explain the technical background.
I am not assiciated with Mozilla, but filed many, many bugs for the Developer Tools. I found the Mozillians very open towards feedback. Most of the bugs were fixed or at least triaged and then fixed later. So I (as a user of your plugin) would appreciate if the original source could be fixed eventually (in some time). Or at least get the chance of fixing it. But first the upstream developers should have the chance of knowing about this problem.

@hbenl OTOH, I would be curious how the https://github.com/devtools-html/debugger.html solves this "breakpoints can only be added at second run" issue. Wouldn't they have the same problem?

@gerdneuman Well, they have the same limitation (and so does the built-in Firefox debugger), but in their case the limitation is less confusing for the user: the javascript files simply don't show up before they're run (they can't show up earlier because the debugger gets the files from Firefox and Firefox doesn't know about them until they're loaded and run). So the user can't set a breakpoint in a javascript file before it is run and hence the debugger never skips a breakpoint.

@hbenl I see, but afaik debugger.html can also be used from within an editor or as CLI. For instance, at the React Rally there was a presentation (relevant snippet is at https://www.youtube.com/watch?v=Fk--XUEorvc&feature=youtu.be&t=2h40m32s) showing integration into emacs or using debugger.html as CLI tool.
So I wonder how this is possible whereas the VS code debugger here is not able using the Firefox Debugger Protocol at initial start. I guess the debugger.html should have the same problems protocol wise. Pinging @jlongster if he has some insight here? Maybe there's some workaround.

@gerdneuman I'm not familiar enough with VS Code to know what you mean by "initial start", but my editor integration does require an existing connection to a Firefox browser. I have the same limitation. When I connect it gets a list of all the current sources in the page and matches them with local files.
Unfortunately this is a limitation with the Firefox protocol. However, we plan to move the setBreakpoint request to something like the thread and allow it to take many types of patterns (URL, source id, etc). Or do whatever it takes to make this work. It shouldn't take too long, but it'll probably be a little while before we find time to do it.

@jlongster That sounds great (incidentally the documentation of the debugging protocol claims that setBreakpoint requests should be sent to the thread actor - seems like this documentation was beamed here from the future ;) ).
Is there a bug report or some other kind of tracker for this, so I can get notified when this has been implemented?


refactor: use forked xml package for writing

TESTING. DO NOT REVIEW OR MERGE.

Codecov Report
Attention: Patch coverage is 85.37234% with 275 lines in your changes missing coverage. Please review.

Project coverage is 68.51%. Comparing base (9dc3afa) to head (614bf19).

Files with missing lines
Patch %
Lines

internal/thirdparty/xml/marshal.go
79.58%
67 Missing and 51 partials :warning:

internal/thirdparty/xml/xml.go
89.63%
46 Missing and 33 partials :warning:

internal/thirdparty/xml/read.go
82.38%
39 Missing and 23 partials :warning:

internal/thirdparty/xml/typeinfo.go
90.80%
11 Missing and 5 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1223      +/-   ##
==========================================
+ Coverage   65.22%   68.51%   +3.29%
==========================================
  Files         170      174       +4
  Lines       14434    13046    -1388
==========================================
- Hits         9415     8939     -476
+ Misses       4501     3474    -1027
- Partials      518      633     +115

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Typo in bold formatting.

Corrected a bad bold formatting in agents.ipynb.

@reachtarunhere Can you please review this PR?

Thank You for the PR. I am not sure if the commit changing Python version locally is required? Can you please clean that up in a new PR or here itself?

@reachtarunhere You are welcome. I have cleaned up the change.

@reachtarunhere Can you please restart the build?

@sampadsaha5 I feel that the build issue is fixed now. Unfortunately Travis is still using the older config file while running the build for this PR. It should work if you will create a new PR.


Where to find missing bundle dependencies?

Hi,
I am very new to Sling, OSGI. Composum sounded interesting, but when I install the bundle, I see this error in /system/console/bundles:
org.apache.commons.lang3,version=[3.0,4) -- Cannot be resolved

How do I resolve this? Do I need to compile this (and other such dependencies) myself or is there a standard repository that everyone uses?
thanks!

Try downloading the latest version from http://search.maven.org/#search|gav|1|g%3A"org.apache.commons" AND a%3A"commons-lang3" .

@rombert Thanks, that worked!
I was afraid that I will have to manually download many such jars from maven, but it looks like that is the only jar that needs to be downloaded.
I have been playing with composum for sometime now and it looks awesome!


Increase timeout in tests and add missing injection

For #8483

Increased timeout to account for slow CI servers
Added missing @injectable in a class used for testing (this was throwing errors, not sure how tests are working though)

Codecov Report

Merging #8776 into master will decrease coverage by 0.32%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8776      +/-   ##
==========================================
- Coverage   58.37%   58.05%   -0.33%
==========================================
  Files         526      526
  Lines       27071    27071
  Branches     4049     4044       -5
==========================================
- Hits        15803    15716      -87
- Misses      10409    10495      +86
- Partials      859      860       +1

Impacted Files
Coverage Δ

src/client/testing/serviceRegistry.ts
49.09% <0%> (-47.28%)
:arrow_down:

src/client/testing/codeLenses/main.ts
40% <0%> (-30%)
:arrow_down:

src/client/datascience/jupyter/jupyterUtils.ts
64.7% <0%> (-29.42%)
:arrow_down:

...t/datascience/jupyter/jupyterDataRateLimitError.ts
50% <0%> (-25%)
:arrow_down:

src/client/formatters/serviceRegistry.ts
75% <0%> (-25%)
:arrow_down:

...ience/jupyter/jupyterDebuggerRemoteNotSupported.ts
60% <0%> (-20%)
:arrow_down:

...cience/jupyter/jupyterDebuggerNotInstalledError.ts
50% <0%> (-16.67%)
:arrow_down:

src/client/common/utils/icons.ts
83.33% <0%> (-16.67%)
:arrow_down:

src/client/api.ts
80% <0%> (-13.34%)
:arrow_down:

src/client/datascience/cellFactory.ts
58.75% <0%> (-12.5%)
:arrow_down:

... and 8 more

Continue to review full report at Codecov.

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


[INH] Updates for 10.1

Update GSE for 10.1

https://wowpedia.fandom.com/wiki/API_debugstack
https://wowpedia.fandom.com/wiki/API_debugprofilestop

https://github.com/Meorawr/LibDBCompartment

Ive added more transparency to loadin times.  This will allow for more data to be gathered to try to find the bottleneck.  Its not as bad as it looked, its more GSE + huge data apps like Rader.io


Make captured pokemon move to the folder of the trainer that caught them, if any.

Make captured pokemon move to the folder of the trainer that caught them, if any.

Implemented (via PTU API) in https://github.com/caffyn/PTUMoveMaster/commit/d464caecb07c156cc0d358653b63baec9ae6e4e8


Bug: Popup Datepicker

When you select the popup datepicker button in the demo it also selects the year dropdown in the datepicker popup. In order to replicate this you need to tap above "2016" on the button when the view is set to replicate the iPhone 6 Plus. I am using chrome but this also happens when I incorporated into my Ionic based project for a client.

This should not happen. If possible could you please provide me a codepen?

I tried to replicate this issue. But i didn't find this issue. Could you please add a codepen or a video?


Redstone components remain powered/pushed upon landing

Redstone components should possibly be exempted from being floating blocks, unless there's a nice way to solve this issue.

They appear to update to me, is there a way to trigger this?

Oh, repeaters do it.

The issue occurs for redstone dust as well

When I tried it on dust it worked fine.

Break the redstone torch after you float it

I placed the dust on a block, floated it, broke the block, and it updated just fine on landing.

I mean powered-wise. Maybe the bug has been resolved though. Let's speak in dev chat


how can i do for date_time default value of migration

I don't know how do i add default value to type of date_time, eg:
...
.col(ColumnDef::new("op_time").date_time().default(???))
...

thanks

Hey @ringrid, welcome! Got it resolved?

@billy1624 no，I tried this method, but it becomes a fixed value, I have no any idea...
.col(
                        ColumnDef::new("op_time")
                            .date_time()
                            .default({
                                let now = OffsetDateTime::now_utc().to_offset(offset!(+8));
                                PrimitiveDateTime::new(now.date(), now.time()).to_string()
                            }),
                    )

do you have any better ideas?

@billy1624 thank you , I found your answer of sea-query question #346,  I had resolved my question.

Thanks for the updates :)


CI: Hack: try parallel spock

Description
WIP.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
CI is sufficient

/test

/test gke-qa-e2e-tests


Support for bibliography in markdown

Would be nice to be able to support bibliography references in the markdown. Similar to: http://rmarkdown.rstudio.com/authoring_bibliographies_and_citations.html

This issue has been automatically marked as stale because it has not been commented on for at least four months.
The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still valuable, please open a proposal at https://discuss.gohugo.io/.
This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions.

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.
If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.


Possible issue with host server

I have an issue where the iframeresizer works on both a local install, as well as on a mediatemple server, but the same code/database doesn't work at wpengine.
Media Temple: http://brooklynbrew.trainadesign.com/where-to-find-our-beer/
wpengine: https://brooklynbrews.wpengine.com/where-to-find-our-beer/
If you visit the media temple link, and use the zip code 92103, you'll see the iframe resize, and the content of the iframe is scrollable. You will see in the console that the iframeresizer is working correctly.
If you visit the wpengine link, you'll see it doesn't resize, and the console log shows "[iFrameSizer][beer-finder-frame] No change in size detected"
I've been in contact with wpengine support, but they were not able to figure out what the issue might be. They asked if it might require a specific nginx rule to be set up for iframeresizer to work.
Any idea what the issue might be?

Sorry no idea, you just need the JS files to download, it's not an nginx issue


[FEATURE] Auto Trim via recurring job

Is your improvement request related to a feature? Please describe (👍 if you like this request)
First of all, thank you a lot for the hard work you put into 1.4.0, feels like Christmas. One of my favorite features that came was the Trim feature, I had crazy cases where my PVC had 120GB and i trimmed it down to 3GB, a game changer. I've noticed these massive trim's are more noticeable with storage which gain & lose data at high rate. This will mean that I have to "manually" (click a button that is) trim the PVC every few days/weeks.
Describe the solution you'd like
Longhorn has recurring jobs for snaps and backups, why not have one for trimming? Or perhaps have this automated based on how much data went through a PVC (that I imagine is a lot less feasible than the other recurring job option). Another possible alternative is to create an API endpoint/ kubectl command I can automate this with.
Describe alternatives you've considered
Like already mentioned I could do it manually , and for RWX I could automate those too (calling kubectl exec ... on the share pod). I am unsure how I could automate it for RWO.
Additional context
To be clear, the feature you produced is fantastic and I realize me saying "here is an improvement, make it better" doesn't seem to show that but I do really mean it, thank you for your hard work.

+1,
for some reason when i seen volume trimming was released on longhorn i was assuming it was done automatically based in a threshold or something.
With the recurring job i believe we get the flexibility make it to trim before a backup (so 120gb of a volume that actually holds 3gb of data doesn't take a day to backup)
OR after a backup is done (to be better safe than sorry)

+1

Until this is implemented, I wrote up a quick python container to do it. It's very barebones, so I'd recommend tweaking the script a bit if you want to use it, but it should give you the right idea.
https://github.com/LP0101/longhorn-auto-trim
It uses API calls to trim RWO volumes. For RWX volumes, it execs into the respective share-manager pod and runs fstrim manually.

Thank you for your script @LP0101 , much appreciated. You made me realise that <longhorn url>/v1 is a thing, thats a gold mine i am never getting out of.

This is kinda a must have. Just a week of Prometheus running with default parameters and the disk space grow exponentially, fast going double the space it use for real. I can't imagine the amount of disk space wasted by people using Longhorn without trimming.
@LP0101 Thanks for the script. Just pointing out there a space missing in the Dockerfile after ENTRYPOINT otherwise it won't build.
Sample of kubernetes cronJob using it daily (change image registry and secret *** to one with the docker built):
apiVersion: batch/v1
kind: CronJob
metadata:
  name: longhorn-auto-trim
  namespace: default
spec:
  schedule: "0 0 * * *"
  successfulJobsHistoryLimit: 3
  suspend: false
  jobTemplate:
    spec:
      template:
        spec:
          imagePullSecrets:
          - name: ***
          containers:
          - name: longhorn-system
            image: ***/longhorn-auto-trim:1.0
            imagePullPolicy: IfNotPresent
          restartPolicy: Never

Verified pass in longhorn master (longhorn-manager a91c62) with test steps
Auto trim recurring job created by yaml wokred properly.
Wait UI merged to test again then close this ticket

Verified pass in longhorn master (longhorn-manager 023dd3, longhorn-ui 5219e4)
Steps

Create recurring job task/type = filesystem-trim from yaml or UI

apiVersion: longhorn.io/v1beta2
kind: RecurringJob
metadata:
  name: recurring-fs-trim-per-min
  namespace: longhorn-system
spec:
  concurrency: 1
  cron: '5/3 * * * ?'
  groups: []
  labels: {}
  name: recurring-fs-trim-per-min
  retain: 0
  task: filesystem-trim

Create workload with volume, write data into volume mount point
Delete data from volume mount point, volume.status.actualSize did not changed.
volume.status.actualSize changes after trim file system recurring job execute.
Repeat above steps few more times, each round went smoothly without problem

i used your exact same setup:
apiVersion: longhorn.io/v1beta2
kind: RecurringJob
metadata:
  name: fs-trim
  namespace: longhorn
spec:
  concurrency: 1
  cron: '0 1 * * *'
  groups: []
  labels: {}
  name: fs-trim
  retain: 0
  task: filesystem-trim

but in the pod that should do the trimming i get:
time="2023-10-10T01:00:01Z" level=info msg="Setting allow-recurring-job-while-volume-detached is false"
time="2023-10-10T01:00:01Z" level=info msg="Got volumes from label recurring-job.longhorn.io/trim-fs=enabled"
time="2023-10-10T01:00:01Z" level=info msg="Found 0 volumes with recurring job trim-fs"

@szechp I think you need to add "default" to the groups in the RecurringJob. The default group should select all volumes without a specific label.
spec:
  groups:
    - default


Configure circle ci to use flyway

Currently circle ci don't use flyway. It would be nice to change this.

Currently ther are only DBUnit tests, so its not needed to use flyway.


Kotlin and dependencies versions update

Kotlin version upgraded to 1.5.31
jcenter() replaced by mavenCentral()
AGP and Gradle versions upgraded
Dependencies versions updated

@kkuan2011 I think the deprecation warning will happen with and without this PR.
I'd be ok with merging


Fix workers crashing when we're on a filesystem path with spaces

This PR fixes the following situation:
[development@localhost ~/P/no-spaces] (paratest) ./phpunit-parallel.sh

Running phpunit in 10 processes with phpunit

Configuration read from /home/development/Projects/no-spaces/phpunit.xml

................................................................. 65 / 76 ( 85%)
........................

Time: 10.07 seconds, Memory: 7.75Mb

OK (89 tests, 903 assertions)
[development@localhost ~/P/no-spaces] (paratest) cd ..
[development@localhost ~/Projects] mv no-spaces/ "with spaces"
[development@localhost ~/Projects] cd with\ spaces/
[development@localhost ~/P/with spaces] (paratest) ./phpunit-parallel.sh
Running phpunit in 10 processes with phpunit

Configuration read from /home/development/Projects/with spaces/phpunit.xml

  [RuntimeException]
  This worker has crashed. Last executed command:
  Output:
  ----------------------
  ----------------------
  sh: 1: exec: /home/development/Projects/with: not found

paratest [-p|--processes PROCESSES] [-f|--functional] [--no-test-tokens] [-h|--help] [--coverage-clover COVERAGE-CLOVER] [--coverage-html COVERAGE-HTML] [--coverage-php COVERAGE-PHP] [-m|--max-batch-size MAX-BATCH-SIZE] [--filter FILTER] [--phpunit PHPUNIT] [--runner RUNNER] [--bootstrap BOOTSTRAP] [-c|--configuration CONFIGURATION] [-g|--group GROUP] [--exclude-group EXCLUDE-GROUP] [--stop-on-failure] [--log-junit LOG-JUNIT] [--colors] [--testsuite [TESTSUITE]] [--path PATH] [--] [<path>]

Sweet, thanks! And double thanks for the good explanation

No worries and thank you :+1:


Fix variadic args in key path subscript

This patch fixes variadic arguments in KeyPath subscripts. If there is a variadic argument, we just extract the element type from the array type and use that for creating equals and hashable.

Resolves SR-11812.

I'll be adding some FileCheck tests later today.

cc @hamishknight @slavapestov @xedin

Please fix typo „varaidic“ and delete code lines after //

@Tiza59 Can't seem to find either, could you give me a line number?

Sorry for the noise, you fixed booth in later commits.

Am 24.11.2019 um 22:25 schrieb Zoe Carver<EMAIL_ADDRESS>@Tiza59 https://github.com/Tiza59 Can't seem to find either, could you give me a line number?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apple/swift/pull/28465?email_source=notifications&email_token=AD6K7CEFMK2IH42IJU63O2LQVLWMNA5CNFSM4JRAYOQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFAVIZA#issuecomment-557929572, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6K7CDFU5VUSUFQQ3WKDETQVLWMNANCNFSM4JRAYOQQ.

@swift-ci please test

@swift-ci please test


Too eager to pick up unrelated files when determining commit message

somebody at komputer in ~/gentoo/gentoo/games-engines/openmw (osg●●)
$ LC_ALL=C git status
On branch osg
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        modified:   ../../dev-games/openscenegraph-openmw/Manifest
        new file:   ../../dev-games/openscenegraph-openmw/openscenegraph-openmw-3.6_p20221115.ebuild
        renamed:    openmw-0.47.0-r1.ebuild -> openmw-0.47.0-r2.ebuild
        modified:   openmw-9999.ebuild

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   ../../dev-games/openscenegraph-openmw/openscenegraph-openmw-3.6_p20221115.ebuild

pkgdev commit wants to include both packages to the commit, and suggests to start the commit message with */*. I tried pkgdev commit ., and it only tries to include openmw*ebuild without ../../dev-games, but still suggests */* in commit message.
pkgdev 0.2.4

You've already staged them, so is it really in the wrong here?

I didn't intentionally stage them, ebump did it for me. I was just working on both of them in parallel.


get webelemnt at location of mouse click not whole document by event.getcurrentTarget

Welcome! Please use this template for reporting documentation issues on https://developers.google.com/web/.
For questions about Chrome DevTools, checkout the
google-chrome-devtools tag on StackOverflow.
For questions about Chrome, check the google-chrome
tag. If you think you've found a Chrome bug, check out our
feedback page for more details on how to file it.
Page Affected: https://developers.google.com/web/TODO
What needs to be done?
Please provide description of what's needs to be done here. Please be sure to include the link to the original page
and any supporting links/data.

[ ] Appropriate type-something label has been added.
[ ] Appropriate section-something label has been added.
event.toElement gives whole <body></body>
and
event.currentTarget gives whole #document

solved by javascript
document.elementFromPoint(x, y);


[Help]: Fail in downloading Sentinel-1 orbits

Describe the problem you met
Write a brief description of the problem you met, e.g. my intf_tops.csh could not run through
I am trying to run a notebook titled "ASF Downloading 2020 Ardabil, Iran Earthquake Co-Seismic Interferogram and LOS Displacement" in Google Colab. However, I am getting an error in downloading the Sentinel-1 orbits part.
OS and software version
If applicable, what operating system and software version you are using?
OS: I am using Google Colab. OS information is given as follows.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
GMTSAR version:
Reproduce the problem
If applicable, how to reproduce the problem from scratch?
The problem is appearing in the following line of the code:
sbas.download_orbits()
Log file
Attach a log file output from your terminal.
FileNotFoundError                         Traceback (most recent call last)
 in <cell line: 2>()
1 # also, we can place pre-downloaded orbit files to data directory
----> 2 sbas.download_orbits()
6 frames
/usr/lib/python3.10/netrc.py in init(self, file)
28         self.macros = {}
29         try:
---> 30             with open(file, encoding="utf-8") as fp:
31                 self._parse(file, fp, default_netrc)
32         except UnicodeDecodeError:
FileNotFoundError: [Errno 2] No such file or directory: '/root/.netrc'
Screenshot
If applicable, attach a Screenshot to help us understand your case

[Please note that if no new responses are made over six months from users, the issue will get closed]
[Also if this is a general question that's not particlarly related to GMTSAR, such as "how to correct atmospheric noise" or "how to intepret my interferogram", consider using the discussions page]

The open access orbits server is currently unavailable, which affects password-less orbits downloading. To address this issue, I've updated the example notebooks with a workaround, as described below. In the development version of PyGMTSAR, you can use the ASF module to quickly download Sentinel-1 scenes and orbits from the Alaska Satellite Facility (ASF) datastore, although user registration is required.
# Workaround: Public access to orbits is currently unavailable.
username =<EMAIL_ADDRESS>password = 'cnjwdchuwe&e9d0We9'
!echo "machine dataspace.copernicus.eu login {username} password {password}" > ~/.netrc
!chmod 600 ~/.netrc
# also, you can place pre-downloaded orbit files in the data directory
sbas.download_orbits()

I passed that part with your new script. Thank you so much.


cowboy_acceptors will not get updated with OTP relups

An improvement on the previous behaviour was introduced in: https://github.com/extend/cowboy/commit/d9da5334d251c95273fd20475f18d19fd3eb37ef
The problem is that right now, the module tuple for the supervisor is []. When the OTP release handler will try to upgrade code, it will navigate through the OTP supervision tree and ask all of the supervisors to tell them what kind of code their children are running. By leaving it to an empty list, the module will be ignored and not upgraded.
To fix this, the module name must be added to the empty list ([cowboy_acceptor]). However, the acceptors are accepting (a blocking operation) and will be killed after a while if they do not reply to release_handler's requests.
The behaviour of the acceptors should be changed to accept only for a few (milli)seconds at a time, look for new messages (including upgrade ones, coming from the sys module), react to them, and then start accepting over again.

I'm not sure this is an issue anymore. We have them upgrading through listener upgrades now. There's no real state to upgrade, just the code itself.

If that is the case, then it shouldn't be a problem anymore.

Thanks!


Add name param to Clients.openWindow() method

OpenWindow creates a new window which can be accessed through the postMessage of the resulting Client object. It would be nice to add a 'name' param, like window.openWindow in order to allow the caller to communicate with the new window of the same domain using the 'name' instead of having to send a postMessage to the service worker and to the new clientWindow. In that way, we can get a reference to the new window opened in the service worker.

Instead of:

From page, postMessage service worker
From service worker, open window
From page, postMessage service worker
From service worker, postMessage page

Why not just:

From page, open window

We would like to use a window as a way of calling WebApis that cannot run on workers, let's call it WindowWorker.
The sw could be in charge of opening this WindowWorker, if necessary that could be share across different documents (windows) related to the same web app.
A simple way of getting a reference to this WindowWorker could be something like:
var handler = window.open('', 'window_worker');
And from there we could postMessage or anything else.
This also makes openWindow closer to window.open as we could interact with windows opened via SW.

@jakearchibald suppose I'm in a team management software application and I receive a push notification for an incomming chat request. The SW open a client window with the incoming conversation via openWindow(). After chatting, I want to close all the conversation through the main window. To do this, I need a reference of each incoming chat.
A feasible solution is to add the name parameter so the SW could generate and store the name for the open window in such a way the main application could get the list of open chats and close them all.
It makes sense to track new open windows. We have this mechanism for window.open() (the name parameter) and for iframes (the iframe itself) but those window contexts open from current implementation of openWindow() are untraceable.
Does it makes sense for you?

@lodr in that use case, wouldn't a much simpler system be for the SW to be able to close windows?

@jakearchibald but the SW could be terminated by the time you want to close the windows and telling the SW to close these window could only be possible if you have some way to mark the clients which are chat windows (and not other kind of clients). You need some way to relate references with information and we don't have even the references.

The window.name method:

Push message into SW
SW opens window with name 'chat-with-steve'
SW adds 'chat-with-steve' to IDB data store 'chat-window-names'
User clicks 'close all chat windows' in window
Window gathers window names from IDB 'chat-window-names'
For each, calls window.open, then calls .close on the handler
Window empties 'chat-window-names' IDB store

In this model you must keep the IDB store up to date, else window.open is going to open a new window.
The windowClient.close() method:

Push message into SW
SW opens window
SW adds new client.id to IDB data store 'chat-window-ids'
User clicks 'close all chat windows' in window
Window sends postMessage to SW, asking it to close all chat windows
SW gathers client IDs from IDB 'chat-window-ids'
SW gathers clients
For each client, calls .close if ID is in 'chat-window-ids'
SW empties 'chat-window-ids' IDB store

So doing it via the SW is a few more steps, but won't result in windows opening up. Also, by using IDs, the SW can "GC" the list in 'chat-window-ids' easily.

@jakearchibald I see. Though, it is quite a limitation to be forced to use the SW as a proxy for whatever operation you want to do with those window open by the SW. Communicating with the SW has its cost, more expensive than retrieving the window reference via window.open() if you realize the SW could be terminated and the awakening introduces its costs.
Furthermore I'm not really convinced you want the service worker to hold business logic. It makes perfect sense to allow opening a window as it's the common use case for a push or even sync events but forcing the SW to act as an intermediate for the business rules and its window causes one of two things:

Putting code in the service worker itself
Or putting it in another context and make the SW and this context to communicate via new postMessage() invokations.

What do you think?


[FLINK-4276] Fix TextInputFormatTest#testNestedFileRead

The problem with test was a simple formatting mismatch between the paths returned by "file:" + File.getAbsolutePath() and Path#toString(). The orientation of slashes were different, and one slash missing after file:.
The test was changed to make sure that the paths are formatted the same way.

+1 to merge this

merging


Update docker-py to the current 1.3.0 release

The docker-py commit used in the standard Dockerfile is from Feb. 2015
and is out of date with the current API level and since then has included
fixes for items like the new docker cli config location as well as registry
v2 changes/API responses as well.
Docker-DCO-1.1-Signed-off-by: Phil Estes<EMAIL_ADDRESS>(github: estesp)

Additional commentary: there are no specific bugs solved by updating to the latest docker-py release, but given there have been issues recently, it makes sense to use the latest released docker-py so problems that are found can be solved upstream at a similar level to what is in development in the docker-py repo.
ping @shin- in case he has any thoughts/concerns with updating the level used by Docker integration tests.

@estesp failures on CI. Maybe docker-py isn't updated to use it with master now

@LK4D4 hmm..yeah, sure enough.  Two of them are easy--new tests which don't check use DOCKER_HOST when creating a client connection.   Third failure is a bit trickier as syslog facility doesn't exist within the Docker test container.. so pre-req/expectation that isn't met.  I can create PR in docker-py for the first 2 failures.

@estesp would be nice

LGTM

LGTM


[SPARK-45018][PYTHON][CONNECT] Add CalendarIntervalType to Python Client

What changes were proposed in this pull request?
Add CalendarIntervalType to Python Client
Why are the changes needed?
for feature parity
Does this PR introduce any user-facing change?
yes
before this PR:
In [1]: from pyspark.sql import functions as sf

In [2]: spark.range(1).select(sf.make_interval(sf.lit(1))).schema
---------------------------------------------------------------------------
Exception                                 Traceback (most recent call last)
Cell In[2], line 1
----> 1 spark.range(1).select(sf.make_interval(sf.lit(1))).schema

File ~/Dev/spark/python/pyspark/sql/connect/dataframe.py:1687, in DataFrame.schema(self)
   1685     if self._session is None:
   1686         raise Exception("Cannot analyze without SparkSession.")
-> 1687     return self._session.client.schema(query)
   1688 else:
   1689     raise Exception("Empty plan.")

...

Exception: Unsupported data type calendar_interval

after this PR:
Welcome to
      ____              __
     / __/__  ___ _____/ /__
    _\ \/ _ \/ _ `/ __/  '_/
   /__ / .__/\_,_/_/ /_/\_\   version 4.0.0.dev0
      /_/

Using Python version 3.10.11 (main, May 17 2023 14:30:36)
Client connected to the Spark Connect server at localhost
SparkSession available as 'spark'.

In [1]: from pyspark.sql import functions as sf

In [2]: spark.range(1).select(sf.make_interval(sf.lit(1))).schema
Out[2]: StructType([StructField('make_interval(1, 0, 0, 0, 0, 0, 0)', CalendarIntervalType(), True)])

How was this patch tested?
added UT
Was this patch authored or co-authored using generative AI tooling?
NO

CI link: https://github.com/zhengruifeng/spark/actions/runs/6032590329

thanks, merged to master


Akbarism/fix autocomplete

Hey guys! Sorry for late reply.
Does #15 has anything related with this PR? If it does, I recommend you look through it and see the limitations we found. Otherwise, let me know if everything is working properly :)

I guess it does, it solves the same problem (with the autocomplete). The PR from @akbarism does a better job at finding the ref, at the price of hardcoding the name of it ("input"). So I guess the solution in #15 is a bit better.


port lang support from upstream

we need to port https://github.com/MycroftAI/skill-date-time/pull/125

cs-cz got autotranslated


test(examples/syslog): add test and example for syslog

This PR adds the syslog ingest example from the Dynatrace Documentation as well as integration tests for it.

The changes and test looks good to me, but I wonder if it wouldn't be nicer if we move the test to its own folder, like we did for prometheus and k8s? Then you could also add a README file like I did here https://github.com/Dynatrace/dynatrace-otel-collector/tree/main/internal/testbed/integration/prometheus

Hmm, should we actually split up all of them then (jaeger, syslog, histogram-split, and otlp)? :thinking:
If we'd decide to do so I'd do that in a follow-up as a pure refactoring PR to keep the diff manageable.


API for playback/record

Currently, there's not a lot (if any) documentation of the record/playback functionality.
(which is expected for a feature undergoing development...)
Several issues/suggestions concerning this future API from code reading and trial/error:

The URL for recording should be accessible to the application, in order to store it in database for later playback. Either pass the URL to the startRecording(), or introduce a getter for the URL being used
The recording in Erizo is applied per stream instance, but it is the room object that has a  member "recordingUrl". Furthermore, the startRecording function uses another (non member) variable also named  "recordingUrl". Suggestion: Keep "recordingUrl" local to the function, but return its value so that the application can memorize it.
Playback is not documented. Code reading suggests the following procedure:
a. Browser script: Open a new Erizo stream with URL assigned to memorized URL
b. Browser : Publish the stream to the room and wait for the add-stream event
c. Erizo : Creates a new stream from Internal source and signal its addition to room members
d. Browser: Attached the added stream to a video tag as if it was any other peer connection.
The above procedure "almost" works, but ends up with a black window at the browser. The recording files was verified with VLC

Any comments/suggestion are appreciated

@lodoyun Documentation says...
"This file can be played directly or streamed into a Licode room."
I downloaded mkv file and it is not playable with the browser like file:///some.mkv
Could you confirm the resultant recording has no need of transcoding?
Thanks!


[QUESTION] Maybe it's worth calling classes directly during dependencies resolution?

hi. currently one can define class dependency in a conscience way as described in https://fastapi.tiangolo.com/tutorial/dependencies/classes-as-dependencies/
commons: CommonQueryParams = Depends()
while it's perfectly convenient i got a question regarding it's performance. all sync callables are submitted to threadpool https://github.com/tiangolo/fastapi/blob/4e77737a3f7bf2608132ea170e9ff013b5af6732/fastapi/dependencies/utils.py#L510
small obvious test using pytest-benchmark:
from asyncio import AbstractEventLoop
from starlette.concurrency import run_in_threadpool
from starlette.requests import Request

request = Request(scope={"type": "http"})

class Dependancy:
    def __init__(self, request: Request):
        self.request = request
        assert request, "whatever"

def make_dependency(loop: AbstractEventLoop, request: Request):
    loop.run_until_complete(run_in_threadpool(Dependancy, request))

def test_class_init_simple(benchmark):
    benchmark(Dependancy, request)

def test_class_init_threaded(benchmark, loop):
    request = Request(scope={"type": "http"})
    benchmark(make_dependency, loop, request)

results:
=== test session starts ===
platform linux -- Python 3.6.9, pytest-5.3.5, py-1.8.1, pluggy-0.13.1 --
benchmark: 3.2.3 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
collecting ... collected 3 items

test_dep.py PASSED                                                       [ 33%]File is reading: test_dep.py
test_dep.py::test_class_init_simple PASSED                               [ 66%]
test_dep.py::test_class_init_threaded PASSED                             [100%]

--- benchmark: 2 tests ---
Name (time in ns)                     Min                       Max                      Mean                  StdDev                  Median                     IQR            Outliers             OPS            Rounds  Iterations
---
test_class_init_simple           570.9589 (1.0)        101,891.9866 (1.0)            660.3349 (1.0)          617.6962 (1.0)          606.0000 (1.0)           40.9782 (1.0)     1285;6974  1,514,383.1012 (1.0)       85904           1
test_class_init_threaded     868,709.0012 (>1000.0)  1,987,215.0151 (19.50)    1,046,580.6085 (>1000.0)  179,461.0125 (290.53)   993,020.5124 (>1000.0)  181,572.0461 (>1000.0)      17;8        955.4926 (0.00)        146           1
---

Legend:
  Outliers: 1 Standard Deviation from Mean; 1.5 IQR (InterQuartile Range) from 1st Quartile and 3rd Quartile.
  OPS: Operations Per Second, computed as 1 / Mean
=== 3 passed in 1.91s ===

i'd suggest treating classes specially. there's usually no much logic in __init__. @tiangolo what do you think? solution is trivial of course:
...
elif is_coroutine_callable(call):
  solved = await call(**sub_values)
elif inspect.isclass(call):
  solved = call(**sub_values)  # here
else:
  solved = await run_in_threadpool(call, **sub_values)
...

of couse one could wrap constructor in some async function like this:
class Dependancy:
    @classmethod
    def inject(cls):
        from fastapi.params import Depends
        d: cls = Depends(cls.init_async)  # type: ignore
        return d

    @classmethod
    async def init_async(cls, request: Request):
        return cls(request)

    def __init__(self, request: Request):
        self.request = request
        assert request, "whatever"

async def get(d: Dependancy = Dependancy.inject()):
    pass

but i would prefer OOB solution. i can submit PR for isclass check. ideas? critics?

Yeah, @sergiorussia that's a good point, if you need as much performance as possible then it's probably better to not use a simple class as a dependency but an async dependency function that returns some class and a type hint with that class.
But having custom logic for __init__ in classes probably wouldn't be a good idea as many tools expect to be able to block in normal functions, e.g. ORMs, Pydantic in ORM mode, etc.


[TS] Button and Button Base include duplicate props

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
What is the source of truth?
Current Behavior 😯
Button has some similar props types  as the  ButtonBase
https://github.com/mui-org/material-ui/blob/ce65fa2a835f2fc76716584975a134059856dcfc/packages/material-ui/src/ButtonBase/ButtonBase.d.ts#L18-L20
https://github.com/mui-org/material-ui/blob/ce65fa2a835f2fc76716584975a134059856dcfc/packages/material-ui/src/Button/Button.d.ts#L8-L10
Steps to Reproduce 🕹
no matter
Context 🔦
no matter
Your Environment 🌎
no matter

Tech
Version

Material-UI
v4.0.0

Good opportunity to get familiar with the type declarations in our codebase. PRs welcome.

IconButton also has duplicated props:
https://github.com/mui-org/material-ui/blob/89687f38cae750650555772ba4d821c9084d8dfc/packages/material-ui/src/IconButton/IconButton.d.ts#L9-L10


Setup fix

Fixed package_data options in setup.py and added missing file for urls.

other solutions should be used in the long run for the urls.py (dev keys if they are still valid).

Agree. But for the time being, I feel like it is mandatory to have it. One is simply unable to use it (the tool) without that file.
A generic value for urls (which I had not tried because I had not quite understood the format) is necessary as default.


Consider using pathto() instead of manually defining URLs.

pathto() in the Jinja2 context is a function and may be the "right" way to link to other versions/etc.
Sphinx RTD theme uses it in layout.html.

Nevermind about this, pathto() is only for docs known to Sphinx. SCVersioning is about links not known to the local Sphinx instance building docs for one version.

This is a good idea after all. Implement something similar. Something like:
def vhasdoc(self, other_version):
    """Return True if the other version has the current document. Like Sphinx's hasdoc().

    :raise KeyError: If other_version doesn't exist.

    :param str other_version: Version to link to.

    :return: If current document is in the other version.
    :rtype: bool
    """
    if self.context['current_version'] == other_version:
        return True
    other_remote = self[other_version]
    return self.context['pagename'] in other_remote['found_docs']

def vpathto(self, other_version):
    """Return relative path to current document in another version. Like Sphinx's pathto().

    If the current document doesn't exist in the other version its master_doc path is returned instead.

    :raise KeyError: If other_version doesn't exist.

    :param str other_version: Version to link to.

    :return: Relative path.
    :rtype: str
    """
    current_version = self.context['current_version']
    has_doc = self.vhasdoc(other_version)
    is_root_ref = self.context['scv_is_root_ref']
    pagename = self.context['pagename']
    if current_version == other_version and not is_root_ref and has_doc:
        return '{}.html'.format(pagename.split('/')[-1])  # User already in this directory, just link to other file.
    level = pagename.count('/')
    if not has_doc:
        pagename = self[other_version]['master_doc']
    if is_root_ref:
        return '{}.html'.format('/'.join(['..'] * level + [other_version, pagename]))
    return '{}.html'.format('/'.join(['..'] * level + ['..', other_version, pagename]))

Then remove Versions.copy() and Versions.remotes['url']. Have Versions.__iter__() call Versions.vpathto() instead. Also benchmark self.__getitem__() with 20 or so remotes. Since __iter__ will call vpathto much much maybe it's better to give vpathto kwargs to do __getitem__() call once.

⚠ I forgot about collisions. Make sure vpathto() handles versions with different directory names (e.g. a branch called _static).

Mostly done in 941cbf0c3c9514e1445a2db4b066c72bf42c9122.

Pretty much done in that commit.


Adding broadcast_to/broadcast_from to collectives module

unify implementation of collectives
factor out beginnings of communicator functionality
fixing a couple of minor issues in existing collectives
modernized API of gather_here/gather_there (futures are now taken by rvalue ref)
renamed existing broadcast.hpp to broadcast_direct.hpp

This is good to go now. Please review

Merging this now as we need broadcast in Phylanx. Please open a ticket if you have comments or complaints.


colab release

Are you planning to release a colab juypter notebook for examples?

Didn't receive a reply. Closing it.


iDMA: Update SoC DMA to newest version of iDMA

Superseded by https://github.com/pulp-platform/occamy/pull/26.


Allowing env variables to be set without forcing VSTS_TASKVARIABLE_ prefix

I'm currently developing an internal Microsoft ADO task that takes in an output variable from another task. It would be very helpful to be able to insert an output variable within the testing framework as well.

Any update on whether this could be integrated into the library please?