How to use GeoPathContext

Hey, thanks for these packages -really awesome work! 🙌
I'm just playing around and I've managed to get the SVG topojson & projections working but I'm unsure how to utilise the GeoPathContext to create a canvas renderer. I've tried to create a flutter CustomPainter but I'm not having any luck and think I'm approaching it incorrectly. I've looked through the tests so understand what it's doing, but just unsure how I should implement. Any advice would be great.
Thanks again

The GeoPathContext class is an implementation of the GeoStream class that effectively translates GeoStream method calls into a subset of CanvasRenderingContext2D API calls.
To use this class, you have two options:

Implement these methods on top of the dart:ui Path and pass them via the constructor, or
Directly pass the methods of the dart:html CanvasRenderingContext2D.

The downside of the second option is that it only works for web applications. The first option might seem a bit complicated, which is why I'm already developing a library on top of the d4 package to facilitate various drawings using the Flutter SDK.

Hey thanks for the feedback, yes it was the first option I was going for.  The issue I'm having is the Flutter canvas api is so different from the html canvas api. This is the kind of thing I've got so far (not working code)
class D3Painter extends CustomPainter {
  final d4geo.GeoProjection projection;
  final Map<String?, dynamic> land;
  final Map<dynamic, dynamic> graticule;

  const D3Painter({
    required this.projection,
    required this.land,
    required this.graticule,
  });

  @override
  void paint(Canvas canvas, Size size) {
    // Geo Path
    var path = d4.GeoPath(
        d4geo.geoNaturalEarth1(),
        d4.GeoPathContext((x, y) {
          path.moveTo(x as double, y as double);
        }, (x, y) {
          path.lineTo(x as double, y as double);
        }, (x, y, radius, startAngle, endAngle) {
          canvas.drawArc(
              Rect.fromCircle(
                center: Offset(x as double, y as double),
                radius: radius as double,
              ),
              startAngle as double,
              endAngle as double,
              false,
              Paint());
        }, () {
          path.close();
        }));

    // Draw land
    canvas.drawPath(path(land), Paint()..color = Colors.green);
  }

  @override
  bool shouldRepaint(covariant CustomPainter oldDelegate) => true;
}

I'm struggling to wrap my head around how I can make this work with the current GeoPathContext -I'm sure I'm missing something really obvious?
The library you're building on top sounds really interesting, is there anything in the public I could gander at? might help me figure out where I'm going wrong!
Thanks

The GeoPath class instance is called to draw the land on the specified path. The land is then drawn on the path, and the path needs to be drawn on the canvas.
import 'dart:math';

import 'package:d4/d4.dart' as d4;
import 'package:flutter/material.dart';

class GeoPainter extends CustomPainter {
  final d4.GeoProjection projection;
  final Map<String?, dynamic> land;
  final Map<dynamic, dynamic> graticule;

  const GeoPainter({
    required this.projection,
    required this.land,
    required this.graticule,
  });

  @override
  void paint(Canvas canvas, Size size) {
    var path = Path();

    // Geo Path
    var geoPath = d4.GeoPath(
      d4.geoNaturalEarth1(),
      d4.GeoPathContext(
        (x, y) {
          path.moveTo(x as double, y as double);
        },
        (x, y) {
          path.lineTo(x as double, y as double);
        },
        (x, y, radius, startAngle, endAngle) {
          path.addArc(
            Rect.fromCircle(
              center: Offset(x.toDouble(), y.toDouble()),
              radius: radius.toDouble(),
            ),
            0,
            pi * 2,
          );
        },
        () {
          path.close();
        },
      ),
    );

    // Draw the land on the specified path
    geoPath(land);

    // Draw the path on the canvas
    canvas.drawPath(path, Paint()..color = Colors.green);
  }

  @override
  bool shouldRepaint(covariant CustomPainter oldDelegate) => true;
}

Ah thank you for that -I wasn't actually too far off! 😅
That's really helpful. Thanks again for the great work on these packages.


Make the source of Service Metadata configureable

Currently service labels are used. There are people who would rather use annotations instead. See #166.
After a long discussion we have decided to make it configurable.
Since there is not recent activity in the pull request, I will close it and keep this issue for tracking purposes.

Hopefully I'll be able to pick this up this week


localhost seemingly seen as <IP_ADDRESS>

Hi Andreas... I think I either stumbled upon an issue... or I'm doing something wrong but can't figure out what.
When attempting to reach:
http://localhost:8787/something

The extension's output is:
RequestError: connect ECONNREFUSED <IP_ADDRESS>:8787

Indeed <IP_ADDRESS>:8787 is not a valid connection in my case, but localhost is. Not sure why this substitution happens. 🤷♂
FYI I haven't seen any issues with the CLI 🎉.

I have the problem when I want to call a service on the Windows host from the WSL. I think it is an overarching problem of WSL 2. I have not yet found the exact reason when localhost is replaced by <IP_ADDRESS>. I suspect in the NodeJS core after resolution using the local hosts file. The stackoverflow post helped me. Or try https://docs.microsoft.com/en-us/windows/wsl/networking
The solutions could also be helpful for using Docker, since presumably WSL2 is also used here.

Hmmm, I'm not using WSL (I'm running VScode on a Mac), and I'm not sure why the CLI would be immune to this vs the vscode extension. Both are using NodeJS (albeit slightly different versions). Neither (I think) is using WSL in my case. 🤷♂

@boobin Can you possibly help me to create a setup how I can reproduce the error. I believe that it is not a bug of my code but more a general NodeJS or vscode problem. It could be some DNS.resolve issue like https://github.com/nodejs/node/issues/40702. Or I also got some problems with using vscode and the integrated VSCode Proxy override (change http.proxySupport from override to off)

I am closing the issue as the problem here is a DNS resolve.  My extension only takes the standards of the NodeJS environment. It would be possible to implement special logic, but it should not be necessary.


Scheduler blackout time period

I have the need for a scheduler blackout time period in Airflow.
My team, which uses Airflow, has been asked to not query one of my company's data sources between midnight and 7 AM. When we launch big backfills on this data source, it would be nice to have the Scheduler not schedule some TaskInstances during the blackout hours.
We (@r39132 and @ledsusop) brainstormed a few ideas on gitter on how to do this...
(1) Put more state/logic in the TaskInstance and Scheduler like this:
my_task = PythonOperator(
    task_id='my_task',
    python_callable=my_command_that_access_the_datasource,
    provide_context=True,
    dag=dag,
    blackout=my_blackout_logic_for_the_datasource # <---
    )

where my_blackout_logic is some function I provide that the scheduler calls to determine whether or not it is the blackout period.
(2) Pause DAGs on nightly basis. We can do this outside of Airflow with cron or Jenkins already. Maybe this functionality gets incorporated into DAGs?
(3) @ledsusop seems to have some ideas on how to build DAGs that are sensitive to time.
(4) Extend my PythonOperator and implement logic for the blackout time period.
Solution (1) is ideal for me because only some TaskInstances in my DAG should be delayed. I'm probably going to go with (2), make my Jenkins pause/unpause my offending DAG during the blackout period for now.
Onwards. :tada:

@boxysean can you please create a jira for this? thanks!

I'd say this is done via the airflow pause_dag <dag_id> & airflow unpause_dag <dag_id> CLIs added and released in 1.7.0. It can be called by an external cron. If someone would like to add this functionality into the UI as a separate pause-unpause schedule, we would welcome the PR. I'm closing this issue for now, but it can be reopened as a Jira should such a PR be issued in the future.

Yeah I agree that cron can do the pause / unpause.
The connection pools in Airflow are very nice because they allow for the limitation of the number of connections to be made and are some easy way for us to control the connections. This ask is for a feature that gives that capability within the Airflow UI and system, as I could imagine blackouts could be something that enterprise users might have to deal with (at least I do).
Created the issue, AIRFLOW-81.


PyO3 incorrectly converts local to UTC times on FixedOffset conversion

Bug Description
When converting to/from datetime.datetime/DateTime<FixedOffset>, PyO3 is using DateTime::naive_utc and DateTime::from_utc -- I believe these should be naive_local and from_local, respectively.
Steps to Reproduce
    #[test]
    fn pyo3_tz_bug() {
        Python::with_gil(|py| {
            let code = r#"
import datetime
t = datetime.datetime.fromtimestamp(86400).replace(tzinfo=datetime.timezone(datetime.timedelta(hours=-8)))
            "#.trim();

            let globals = PyDict::new(py);
            py.run(code, Some(globals), None).unwrap();

            // Get ISO 8601 string from python
            let t = globals.get_item("t").unwrap();
            let py_iso_str = t.call_method0("isoformat").unwrap();

            // Get ISO 8601 string from rust
            let t = t.extract::<DateTime<FixedOffset>>().unwrap();
            let rust_iso_str = t.to_rfc3339();

            // They should be equal
            assert_eq!(py_iso_str.to_string(), rust_iso_str);
        })
    }

This test fails with
assertion failed: `(left == right)`
  left: `"1970-01-02T00:00:00-08:00"`,
 right: `"1970-01-01T16:00:00-08:00"`

I think the bug probably went unnoticed because it exists on both the IntoPy and FromPy paths so cancels itself out when you go to and from, but you can induce it by creating dates in native python as shown above.
 Did you use a virtualenv?
brew, no
Additional Info
No response

@Psykopear @pickfire Do you have the bandwidth to look into this?

FWIW I think the fix here is to change this naive_utc to naive_local, and this from_utc to from_local, some tests may need to be updated too.

@grantslatton Care to create a pull request?

Hi @grantslatton @adamreichold . So, it's been a long time since that was merged, I need some time to go through the PRs and discussion to remember what was the reasoning behind that, but I think the UTC conversion was not accidental, see this comment (and in general the discussion in the PR. It's a long one, but I think we talked about almost every detail of the code in there):
https://github.com/PyO3/pyo3/pull/2612#issuecomment-1253404654
There might still be a bug in the conversion, but reading that, I'm not sure changing from *_utc to *_local is right.
I might have been wrong then though, so I'd like to take some time to review why I did think that at the time.
Anyway if you are in a rush to merge #3269 , I trust pyo3 maintainers and if they are ok with the fix, I'm ok with it too, and if I find problems with it in the future I'll open a new issue to discuss this.

Anyway if you are in a rush to merge https://github.com/PyO3/pyo3/pull/3269 , I trust pyo3 maintainers and if they are ok with the fix, I'm ok with it too, and if I find problems with it in the future I'll open a new issue to discuss this.

I don't think there is any particular pressure here and I would prefer if we take the time to resolve this properly. More eyes make bugs shallower.

Ok, I just noticed the other issue (#3266 ), and there is some more to extract from the previous discussion to properly answer that too. I'll try to find some time for this between this week and the next, but if I don't, please ping me again. It's important to get this right, and I'd like to share the output of the weeks we spent on the previous PRs because a lot of valuable insights was gathered at the time. Luckily everything's written down, but I understand that trying to find the important info in that discussion might be complicated if you weren't participating. I'd love to see proper timezone info support, but as usual when you deal with timezones (and python's timezones handling), getting it right is always harder than it looks.

Yes, no pressure, as we have already implemented all of these fixes in our code manually, but it would be nice to move that code from our codebase to a fully supported replacement in pyo3 itself :)
I think converting to UTC is not necessarily wrong, but if you do, you need to change the fixed offset timezone to always be UTC (i.e. offset 0) too. 0400+0200 is unambiguously equal to 0200+0000, so converting to UTC is lossless if you convert both the left and right side (time and offset). The code before was just mutating the time but not the offset. The test I provided proves this is a buggy (but was a hidden bug because going IntoPy and then FromPyObject reverses this process, hiding the bug).
That said, there are maybe some philosophical reasons to prefer not always converting to UTC. If a user does 0400+2000 IntoPy, and then does FromPy, they might be surprised to find their data converted to UTC. Provenance information might be important.

Yes, no pressure, as we have already implemented all of these fixes in our code manually, but it would be nice to move that code from our codebase to a fully supported replacement in pyo3 itself :)

Yes that's one of the things I really like about the way PyO3 is organized. I reimplemented the chrono integration in my own codebase after I found a bug in the original crate we were using, before deciding to try to upstream it (and with all the eyes on the review, including the author of the original crate, it did come up way better than my first implementation :smile: ). You need to create several newtypes and reimplement PyO3 traits on them, but you usually end up doing it for other reasons anyway.

I think converting to UTC is not necessarily wrong, but if you do, you need to change the fixed offset timezone to always be UTC (i.e. offset 0) too. 0400+0200 is unambiguously equal to 0200+0000, so converting to UTC is lossless if you convert both the left and right side (time and offset). The code before was just mutating the time but not the offset. The test I provided proves this is a buggy (but was a hidden bug because going IntoPy and then FromPyObject reverses this process, hiding the bug).

Uh, I see now, and yep this looks like a bug. I'll look into the test and comment on the PR when I get to a checkpoint for what I'm working at.

That said, there are maybe some philosophical reasons to prefer not always converting to UTC. If a user does 0400+2000 IntoPy, and then does FromPy, they might be surprised to find their data converted to UTC. Provenance information might be important.

Yep, I'd obviously rather have the exact same representation when passing a datetime object from Python->Rust->Python. I think there was a reason behind this, and it was not accidental. But as I said it's been some time, so I might be confusing this with something we did elsewhere in the integration, that's why I want to double check the discussion before saying more.

Ok, sorry for delaying this, I misinterpreted the problem at first, but I reviewed the PR, and it's good for me, the issue is there and the PR fixes it. I added a comment there, the only concern I have is about the chrono_tz integration (I think we'll need to have a separate feature for chrono_tz, and keep chrono as it is), but that can be discussed in the other issue. Thanks @grantslatton for fixing this


Delete socat dependency on sci

Description
sci is a static compiled binary to be used with any rootfs. When using an app registration for firecracker in resume mode, sci calls socat in VSOCK-CONNECT mode to establish a connection. That socat creates a dependency to socat in the guest. We could prevent that by adding an implementation based on:

https://docs.rs/vsock/latest/vsock/struct.VsockStream.html#method.connect_with_cid_port
https://docs.rs/pty/latest/pty/

To run the command in the same way socat does it
Acceptance Criteria
guestvmtools sci no longer requires socat

VsockStream works similar to TcpStream:

https://github.com/thepacketgeek/rust-tcpstream-demo/tree/master/raw

redirect command stdio/stderr through a socket stream example, helpful

https://stackoverflow.com/questions/64531243/redirect-stdio-over-tls-in-rust

sci is only one half, socat is also used in firecracker-pilot


Adding way to customise tag of "hacky dev image build"

What does this PR do?
It allows you specify the tag to use when building the "hacky dev" image locally.
Motivation
Wanted multiple images without having to retag built images.
Additional Notes
None.
Possible Drawbacks / Trade-offs
None.
Describe how to test/QA your changes
Run invoke agent.hacky-dev-image-build --target-tag <some tag> and check you have an image called agent:<some tag> after it all builds.
Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

So previously --target-image=agent: was supported. Now it seems not any more. The customized tag must be added through --target-tag. If target-image is used, the "latest" tag is automatically appended.


Only analyze audio - without rendering

Is there a simple way to use wavesurfer to get the duration (and possibly other data) of the audio file without rendering the waveform?
In part of my app I use wavesurfer to create the visual rendering of the audio, but in another part of my app I would like to simply get the duration of the track without actually rendering anything.

I know I could just create the wafesurfer container and hide it, but I feel like that is not very elegant.

you can use AudioContext.decodeAudioData() or use something like ffmpeg on the serverside to determine the duration.


added autoeval fields to repocard types

This PR makes the repocard types consistent with the spec that autoeval uses: https://raw.githubusercontent.com/huggingface/hub-docs/main/modelcard.md
It is based on lewis's PR here, but it only includes the necessary changes to repocard_types.py

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

cc @nateraw

Hi @adrinjalali can you please advise us on how to handle the failing codecov test? Is it a question of writing more unit tests for the repocard or something else?

In order to migrate the AutoTrain backend to use #888 instead of #884, we'll actually need the changes in this PR to be available in @SBrandeis' fork/branch. (We rely on the additional metadata fields provided by the current PR)
To unblock @coyotte508 in https://github.com/huggingface/moon-landing/pull/3144 (which disables the upload_file() endpoint we use in AutoTrain) one possibility is to:

Close #901 and open an identical one on @SBrandeis's branch that takes into account the reviewer feedback.
Migrate the AutoTrain backend to use #888 once step (1) is merged

This isn't a pretty solution and it pollutes #888 with changes unrelated to the new API.
An alternative would be to:

Allow https://github.com/huggingface/moon-landing/pull/3144 to disable the upload_file() endpoint we use in AutoTrain. This will disable the evaluation service until #888 is merged
Merge #901
Migrate the AutoTrain backend to the new commit API once #888 is merged

In the interest of releasing a stable evaluation service without lots of hacks, I'm in favour of the second option as long as it doesn't delay the release by too much. @SBrandeis do you have a rough idea how long it will take to get your PR merged?
cc @douwekiela @TristanThrush @abhishekkrthakur

After discussing internally, we'll go for the option to wait until #888 is merged before migrating the AutoTrain backend.
@coyotte508 from my side: feel free to merge https://github.com/huggingface/moon-landing/pull/3144 when you want :)

@lewtun https://github.com/huggingface/moon-landing/pull/3144 is ready to be merged
Nothing's going to burn, right? :sweat_smile:

Nothing's going to burn on your side, right? 😅

Nope, the eval service is still in dev but let's quickly ask @gante for confirmation since I believe he was using my branch in transformers

Don't mind transformers, I'm the sole user of the related functionality and I can hold it for a few days.
I will make the appropriate changes as soon as #888 gets merged 👍


Slnx support

After migrate to slnx solution file, ef core dialog is not opening. Please add support this format.
Thank you.

Hi @trdmitry, I can't reproduce the issue. Please after reproduction submit logs and diagnostic data via Help | Collect logs and attach them to the ticket: https://youtrack.jetbrains.com/issue/RIDER-119867/SLN-SLNX-file-migration-breaks-EF-Core-dialogs
Thanks!

Closing this due to inactivity


Please update it to Latest Vuejs v3 + TypeScript

Please update it to Latest Vuejs v3 + TypeScript

It will be updated soon. I'm rewriting a small part of it first and then I'll release the updated build

Updated 👍🏻


Fix typo in kubevirtci::fetch_kubevirtci

What this PR does / why we need it:
Fix typo in kubevirtci::fetch_kubevirtci
KUEVIRTCI_TAG --> KUBEVIRTCI_TAG
Release notes:

None

/ok-to-test


refactor: use JestMatcherUtils instead of jest.MatcherUtils

closes #7

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


init-qtrpi-minimal.sh can't download qtrpi-sysroot-minimal-latest.zip

Hi there.
init-qtrpi-minimal.sh can't download qtrpi-sysroot-minimal-latest.zip the site qtrpi.com is down.
Where I can find this file?
Thanks

i have the same problem

Yes it's related to the issue #81 and #84


Phase 5: Convert src files to JS and remove bower dependency

TODO (not just for this PR):

[ ] Assorted FIXMEs
[ ] Add branch for Ember 1.11
[ ] Put code back in addon folder where possible
[x] Headers on financial table are messed up
[x] Antiscroll doesn't seem to show up
[ ] Add globals build

Merged.


Possible performance issue during DruidSchema metadata refresh

Druid Broker 0.11.0 with druid.sql.enable=true produces much more garbage than usual, profiling shows a lot of Object[] which are referenced by TreeMap$Entry which eventually leads to io.druid.sql.calcite.schema.DruidSchema#refreshSegments. I speculate it constantly refreshes metadata for every segment. With -Xmx5G and 1mln segments it leads to unresponsive service due to GC. Meanwhile it works fine with druid.sql.enable=false.

Hi @egor-ryashin,
There have been some improvements to the refreshing mechanism in later versions (try 0.12.1?). It doesn't constantly refresh metadata for historical segments, but it does refresh periodically for realtime segments, which is important because new columns can show up at any time. However, the metadata does take up space, so if you were running kind of close to heap max with druid.sql.enable=false before then you'll need more heap in order to enable SQL.


Update iphonesimulator.modulemap

Was set to  iPhoneSimulator9.0.sdk. This should use the symlink instead of the specific simulator version as it will break with iPhoneSimulator9.x.sdk

This is a valid pull request, but why is the build failing?

Must've been some sort of Travis-CI glitch, merging.


Wrong request.content xml generation

Hello!
I've experienced wrong request xml generation for nested hashes/arrays. I don't know if it feature or bug?
Here is sample code for it:
@wsdl = File.read( '/home/leo/Dropbox/Outbox/lolsoap-test-wsdl.xml' ) # actual wsdl: https://www.dropbox.com/s/odxa59vutg8nvpw/lolsoap-test-wsdl.xml

@client = LolSoap::Client.new( @wsdl )
request = @client.request( 'NewOrderCreate' )

request.body { |body|
  body.user_id( '9b6a2514-0af3-11de-9185-001cc02b573f' )
  body.comment( 'Test order' )
  body.wares( [
    { ware_id: 'ware_id-1', count: 1, requested_price: 2, warehouse_id: 'warehouse_id-1' },
    { ware_id: 'ware_id-2', count: 3, requested_price: 4, warehouse_id: 'warehouse_id-2' }
  ] )
}

puts request.content

Actual result:
<?xml version="1.0"?>
<soap:Envelope xmlns:xs1="polam/Order" xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  <soap:Header/>
  <soap:Body>
    <xs1:NewOrderCreate>
      <xs1:user_id>9b6a2514-0af3-11de-9185-001cc02b573f</xs1:user_id>
      <xs1:comment>Test order</xs1:comment>
      <xs1:wares>[{:ware_id=>"ware_id-1", :count=>1, :requested_price=>2, :warehouse_id=>"warehouse_id-1"}, {:ware_id=>"ware_id-2", :count=>3, :requested_price=>4, :warehouse_id=>"warehouse_id-2"}]</xs1:wares>
    </xs1:NewOrderCreate>
  </soap:Body>
</soap:Envelope>

Expected result:
<?xml version="1.0"?>
<soap:Envelope xmlns:xs1="polam/Order" xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
  <soap:Header/>
  <soap:Body>
    <xs1:NewOrderCreate>
      <xs1:OrderData>
        <xs1:user_id>9b6a2514-0af3-11de-9185-001cc02b573f</xs1:user_id>
        <xs1:comment>Test order</xs1:comment>
        <xs1:wares>
          <xs1:ware_id>ware_id-1</xs1:ware_id>
          <xs1:count>1</xs1:count>
          <xs1:requested_price>2</xs1:requested_price>
          <xs1:warehouse_id>warehouse_id-1</xs1:warehouse_id>
        </xs1:wares>
        <xs1:wares>
          <xs1:ware_id>ware_id-2</xs1:ware_id>
          <xs1:count>3</xs1:count>
          <xs1:requested_price>4</xs1:requested_price>
          <xs1:warehouse_id>warehouse_id-2</xs1:warehouse_id>
        </xs1:wares>
      </xs1:OrderData>
    </xs1:NewOrderCreate>
  </soap:Body>
</soap:Envelope>

P.S. Thank you forward for reply, I really love the way lolsoap are implemented.

Hi! @shagabutdinov did you code this up? I sure could use it.  Thanks.

Sorry, I didn't. And I don't use this library right now, so I don't think I'll do it in near future.


VS 2013 does not support default for move constructors

While using sqlite3pp in VS 2013 (yeah, old, but still in widely use) the compiler generates next errors:
2>C:\work\tmclient\common\libs\sqlite3pp\sqlite3pp.h(57): error C2610: 'sqlite3pp::noncopyable::noncopyable(sqlite3pp::noncopyable &&)' : is not a special member function which can be defaulted
2>C:\work\tmclient\common\libs\sqlite3pp\sqlite3pp.h(58): error C2610: 'sqlite3pp::noncopyable &sqlite3pp::noncopyable::operator =(sqlite3pp::noncopyable &&)' : is not a special member function which can be defaulted

Error points to sqlite3pp.h, lines 57 & 58:
    noncopyable(noncopyable&&) = default;
    noncopyable& operator=(noncopyable&&) = default;

See also similar question on stackoverflow
Can you please fix it?

Alternatively, you can use the code in /boost_src. It requires boost library but it can be used pre-c++1x compilers.

Please reopen if the solution didn't fix your problem.


[Question + Custom Backend] Drag doesn't seem to respect camera scaling

As the title suggests, Drag's delta seems off when camera scaling is changed.
When the camera viewport scale is decreased (i.e. zooming in), dragging things become way faster than the cursor:
https://github.com/user-attachments/assets/220e6ee7-619f-49c2-a67d-0babf3bbd336
Normal scaling makes dragging correctly follow the cursor:
https://github.com/user-attachments/assets/e70c3f00-723c-4844-b880-2f3a4b592277
However, I'm not entirely sure if this is on the library or me, because I wrote my own picking backend for Avian (the 3D version exists but not 2D...) in this repository.
Files of interest:

picking.rs (the backend).
collider.rs#185-195 (how I used Drag::delta).
lib.rs#38 (how I manipulated the camera scaling).

The recordings above can be reproduced by altering the aforementioned lib.rs line 38, and probably increasing the scale of the colliders if you have a hard time trying to drag the vertices at such a large camera scale.
Am I doing anything wrong? I can't make anything out of the documentation, not that I'm much of a math guy anyway... :^)
Any help would be appreciated!

Same probrolem here.
I divided by the camera multiplier to get the correct result.

Fixed it too! aevyrie stated in Discord that delta is actually in screenpos, so instead of using the raw delta, I utilized Camera::viewport_to_world_2d and everything works perfectly now.


Swift API Guidelines

Small nitpick here, the Swift API Guidelines state that getters should not begin with get, as it's implicit in the fact that the method returns something.
Maybe change things like:
func getMethods() -> [Selector] { ... }
func getImplementation(selector: Selector) -> IMP?

to
var methods: [Selector] { ... }
func implementation(for selector: Selector) -> IMP?

@harlanhaskins Thank you so much for the issue! My rationale being having get in the getter names was that the original Objective-C Runtime methods such as class_getName, class_getProperty, objc_getClassList etc. all have get too. I was trying to follow the name structure of these runtime methods.
However, I agree that removing the get gives a slightly cleaner API and so I will change to that in the next release. Do let me know if you have any other suggestions or complaints about Lumos. Thank you :)

Doing something like this:
let classes =  Lumos.getAllClasses().filter { b in
      return true
}

print(classes[0].description())

crashes with:
[ description] sent to deallocated instance 0x123195e58
The filtered array wasn't empty, sure thing.  Xcode 9.4.1.


Clarify pubsub IO comment about timestamps

Updated based on the information from https://github.com/apache/beam/blob/cad0333d6e27a9646fb70289bc8d2dde770b55af/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/pubsub/PubsubClient.java#L86

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @rezarokni

Run Java PreCommit

Run Java PreCommit

Build is timing out after 2hrs.

Run Java PreCommit


ARROW-1584: [C++/Python] Support Null type in IPC round trips, fix serialize_pandas on empty DataFrame

cc @TomAugspurger @cpcloud -- this turned out to be caused by the index in the empty DataFrame having null type:
In [3]: arr = pa.array([])

In [4]: arr.type
Out[4]: DataType(null)

In [5]: arr = pa.array([None, None, None])

In [6]: arr
Out[6]:
<pyarrow.lib.NullArray object at 0x7f28d3d205e8>
[
  NA,
  NA,
  NA
]

This type had been unhandled in the IPC machinery, so this resolves ARROW-1637. We need to implement integration tests for this type to make sure such data can be accurately messages between Java and C++/Python

@jakirkham @ocepaf I'm using cmake + git + openssl + curl from conda-forge here and in the last 24 hours we've been gettin failures like
/home/travis/build/apache/arrow/cpp-build/gbenchmark_ep-prefix/src/gbenchmark_ep-stamp/gbenchmark_ep-download
-- downloading...
     src='https://github.com/google/benchmark/archive/v1.1.0.tar.gz'
     dst='/home/travis/build/apache/arrow/cpp-build/gbenchmark_ep-prefix/src/v1.1.0.tar.gz'
     timeout='none'
CMake Error at gbenchmark_ep-stamp/download-gbenchmark_ep.cmake:21 (message):
  error: downloading
  'https://github.com/google/benchmark/archive/v1.1.0.tar.gz' failed
    status_code: 1
    status_string: "Unsupported protocol"
    log: Protocol "https" not supported or disabled in libcurl

any idea what might be causing this? is it a github problem?

I'm using cmake + git + openssl + curl from conda-forge

All I can say is that none of those packages were updated in the past 24 hours. The most recent change was git, 6 days ago.
That does not mean they are not the culprit, but something else may have changed there.

Working on diagnosing this. So miniconda changed, so something is going on with openssl. @ilanschnell or someone from the Anaconda team, could you comment what might have changed?

Python 3.6.1 :: Continuum Analytics, Inc.

and the default env from a recent failing build:
++bash miniconda.sh -b -p /home/travis/miniconda
PREFIX=/home/travis/miniconda
installing: python-3.6.2-hdfe5801_15 ...

The openssl version is the same, but it looks like maybe the ca-certificates from defaults is clashing with conda-forge

The toolchain environment being installed in https://github.com/apache/arrow/blob/master/ci/travis_before_script_cpp.sh#L34 is completely unchanged (version numbers, build numbers from conda-forge), so it looks like the only difference is some intermingling with the root environment

+1


[Bug] [FLINK_STREAM] Many NPEs

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
I execute the real-time task button in the task definition menu, and the background keeps reporting NPE
What you expected to happen
java.lang.NullPointerException: null
	at org.apache.dolphinscheduler.server.master.runner.StreamTaskExecuteRunnable.run(StreamTaskExecuteRunnable.java:155)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

java.lang.NullPointerException: null
	at org.apache.dolphinscheduler.server.master.runner.execute.DefaultTaskExecuteRunnableFactory.createTaskExecuteRunnable(DefaultTaskExecuteRunnableFactory.java:51)

How to reproduce
Creating FLinkstream tasks is enough
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

The first NPE, I solved it through constructor injection.
But for the second NPE, why does the execStreamTaskInstance method not insert data into the command, resulting in no data in the cache. Don't you need it

When will this problem be fixed. @SbloodyS

same problem

same problem


Get worker count and other info from client.

Something like this would be useful. It could count all currently registered workers.
class Client():
    ...
    def get_nworkers():
        # return number of workers.

Another useful method could be Client.count_active_workers which would ping all workers, then return how many responded after 1 second or so.

Would we want to expose the full Scheduler.workers dict?  If so then that would be one protocol back and forth and then lots of simple functions client-side.
Could we use heartbeats (which has other uses) plus sending the workers dict (which might hold "last-seen" values) rather than making a special protocol to ping all workers and see how many respond in a second?
For maintenance concerns I'm trying to find the fewest possible protocols that can cover our needs.

Maybe Client.registered_workers should be a property that gets the Scheduler.workers dict?

Yeah, I think that it would be good to expose getting an updated workers dict.  I can think of a few use cases for this so I think it makes sense to peel this off from Client registration.
I heard once that it's good form to avoid using properties with things that are expensive and use explicit functions like get_registered_workers() instead.  I guess the idea was that properties look like fields which make the promise of cheap access.


Adding specific code owners for easier maintenance

Signed-off-by: Sarat Vemulapalli<EMAIL_ADDRESS>Description
Removing the team alias and adding specific maintainers to keep sanity.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@owaiskazi19 this should solve the problem, newer members of the team cannot be added automatically without a PR.

@owaiskazi19 this should solve the problem, newer members of the team cannot be added automatically without a PR.

Looks like it. Will it also @vibrantvarun not able to edit the issue?

@owaiskazi19 this should solve the problem, newer members of the team cannot be added automatically without a PR.

Looks like it. Will it also @vibrantvarun not able to edit the issue even after adding them to @opensearch-project/triage.

We can add @vibrantvarun to the @opensearch-project/opensearch-sdk-java team, and he should have all the permissions to create/modify/remove/move issues.

I have added @vibrantvarun and @mloufra back to @opensearch-project/opensearch-sdk-java

@owaiskazi19 this should solve the problem, newer members of the team cannot be added automatically without a PR.

Looks like it. Will it also @vibrantvarun not able to edit the issue even after adding them to @opensearch-project/triage.

We can add @vibrantvarun to the @opensearch-project/opensearch-sdk-java team, and he should have all the permissions to create/modify/remove/move issues.

Wouldn't that give them the maintainers permission back or this PR will solve that?

This PR will solve it.


Anchor links sometime do not take you directly to the section it belongs to

I can't reproduce this reliably, but go to https://docs.railway.app/reference/cli-api and click around anchor links and you'll land on a different section than intended after a few clicks.
This seems related to https://github.com/vercel/next.js/issues/44295

@half0wl this is likely unrelated to this specific issue, and the marketing site is likely a different repo...
but worth noting here that the "main career page" links in job pages link to the same job page. reported with screen record in discord. happens on both safari ios and chrome mac for me.

Also, can confirm that the original issue here happens still on my machine. I might take a look and report back.

Hello all, I think this issue has been resolved, or at least I haven't been able to reproduce the issue described above by clicking on the links highlighted in the image below.

This was fixed in #558


Fieldsets not working with multiple decorators

I am fighting with a very strange issue.
To best understand it, you will need to check out the demo app I have made;
https://github.com/mogmog/asfdemo.git
I am trying to create 2 decorators - one read only, and one regular edit style. THese have been created in app.js
https://raw.githubusercontent.com/mogmog/asfdemo/master/app/app.js
When I do this, if my form does not contain a fieldset, everything is fine (View2). Two forms are displayed, one read only, one not.
If however my form contains a fieldset (View 1), then the read only decorator is applied to both forms, which seems very wrong. Any ideas?

@mogmog the form only uses one decorator, can you make a plunker or jsfiddle?

@mogmog, I have to close this for now, if you can provide a gist or plunker, please re-open the issue and I'll do my best to help!


Crush when i try to disable an option

When i open the config and i try to change the option to disable the real furnace or the other options the game crush

When exactly does the game crash? As soon as you change an option or only when you restart the game? Could you provide me with a full crash report, since I cannot reproduce this issue locally.

https://paste.dimdev.org/ebinozewej.mccrash This is a crash report of that very thing. For some odd reason I cannot see the little images on the beacon, so I tried to disable it and this happened.


Unify getitem code between Cube, Coord and CellMeasures.

This is a useful preliminary to replacing lazy/real array data with DataManager in Coords code.
It reduces the indexing code in those 3 areas to suspiciously similar usages, with the bulk of the common code in a new private utility routine iris.utils._slice_data_with_keys :  I think that code can usefully go inside DataManager.__getitem__ in future.
In future, in addition to rebasing all these 3 areas onto DataManager, I would also move the coord points and bounds accessors into Coord as generic methods, and make DimCoord extend the generic calls with its extra checks and tweaks.  The new similarities of handling make this attractive, but it is better left undone because (a) it makes this PR simpler and (b) it will be simpler when the underlying data objects are all DataManager-s.
This PR also contains a strictly temporary hack to remove the special-casing of LazyArray data within AuxCoords, by wrapping them as dask arrays instead (WrappedLazyArray class and _wrap_lazy function in coords.py).
This should be replaced by the result of https://github.com/SciTools/iris/pull/2518 when that is ready.

@bjlittle @dkillick @lbdreyer Please check this out !

the bulk of the common code in a new private utility routine iris.utils._slice_data_with_keys : I think that code can usefully go inside DataManager.__getitem__ in future.

Out of interest, why did you choose to add this new private utils routine rather than add a __getitem__ to the DataManager class in the first instance?

why did you choose to add this new private utils routine ... ?

Oh, is the answer "because the routine already existed"? And, as such, was a useful place to host extended functionality...

why did you choose to add this new private utils routine

I just needed a place for common functionality, but I'm expecting it to go into DataManager.
I guess we'll leave the two existing iris.util routines in place as status quo is simplest, though not exactly ideal.

Rebased.
@dkillick @lbdreyer Please re-check !

I think we should maybe have a test for the new function iris.util._slice_data_with_keys (which I just changed a bit).
I could do that now, or we could wait until we decide whether it lives inside DataManager ?

These simplifications are worthwhile I think @pp-mo. But I'm afraid that I think we do need some testing for the new iris.util._slice_data_with_keys function. Perhaps try and keep the testing quite terse, given that the new function may be only temporary...

But I'm afraid that I think we do need some testing for the new iris.util._slice_data_with_keys function.

Agreed

Perhaps try and keep the testing quite terse, given that the new function may be only temporary...

but the tests you write could be modified so that they become data manager tests once it's moved there

@lbdreyer but the tests you write could be modified so that they become data manager tests once it's moved there

:+1:

Hi @lbdreyer @dkillick
New code with added test.
Hope this addresses all to-date.
More delay --> yet another rebase, I'm afraid.

Following discussion, I added some purely results-based tests.
The existing mock-ist approach is liable to collapse if we need to modify any of the implementation, but the new test should be robust to refactoring.

I was minded to say I was happy with things as they were before the latest commit, so I'm definitely minded to say I'm happy now! I'll wait to see if we can persuade Travis to be happy and then I think I might merge...


update java to 1.8.0_45

http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
http://www.oracle.com/technetwork/java/javase/8u45-relnotes-2494160.html

Looks like this was fixed by @nremond in 4d31a21d7fab2a0e89cb44a326e138327a98efe7 and can be closed when #10644 is merged.

thanks @nremond!

Oh, merged already, closing.

@jab you're welcome ;)


Uncomment check around inclusion of CryptoBuildConfig.h

Problem
Some platforms still do not build with these configs.
Change overview
Remove comment conditional inclusion of CryptoBuildConfig.h removed in prior commit.
Testing
Local build
CI

Covered by https://github.com/project-chip/connectedhomeip/pull/20887


Support job transfer

Coverage remained the same at 34.095% when pulling ac28bab88bde134a21260644ad96e4334a7707e9 on shaiic-pai:support_job_transfer into 5f12ee5f06ec0dd05a6c140a4880a7acf3d3dd53 on microsoft:master.

Test Case (the following items should be tested in both basic auth and AAD mode):

Set webportal.enable-job-transfer = false in services-configuration.yaml. Deploy the cluster, and confirm:

Submit a job. On the job detail page, the clone button should have no Transfer option.
On the user profile page, you cannot see the Bounded Clusters section.

Set webportal.enable-job-transfer = true in services-configuration.yaml. Deploy the cluster.

Confirm:

Submit a job. On the job detail page, the clone button should have a Transfer option.
On other user's job detail page, you cannot see the Transfer option.
Click the transfer button, it should warn you that You should add some bounded clusters.
On the user profile page, you can see the Bounded Clusters section.

on the user profile page:

Add some bounded clusters
Try to delete some bounded clusters

Test job transfer

Submit a job. On the job detail page, click Transfer.
Try to input wrong VC/storage/sku type, then click confirm transfer. The job should not be transferred.
Edit the job config to make it a valid config for the target cluster. Then click Confirm transfer.
Click Stop it
The job should be transferred, and you can see the URL on the job detail page. The previous job should be stopped.


[1pt] PR: dev_bot_fixes (Tornado, aiohttp, Jupyter, JupyterLab)

This PR was triggered by two dep-bot PR's. One for Tornado, one for aiohttp. Upon further research, these two exist only as dependencies for Jupyter and Jupyterlab which were very out of date. Upgrading Jupyter/JupyterLab took care of the other two.
Also fixed a minor warning during docker builds.
Covers PR 1237: Bump aiohttp from 3.10.5 to 3.10.11  and  PR 1348: Bump tornado from 6.4.1 to 6.4.2
Changes

Dockerfile.dev and Dockerfile.prod:  As described above.
Pipfile and Pipefile.lock:   As described above.

Testing
Ran a small fim_pipeline for "07080103 07080208 12040101 12040103 12090301", then ran sythesize_test_cases on it succesfully. Also ran eval_plots on it and it failed but is being written up as a separate issue card and is unrelated. The eval_plots error exists with or without the new dev image.
Deployment Plan (For developer use)
How does the changes affect the product?

[x] Code only?
[ ] If applicable, has a deployment plan be created with the deployment person/team?
[ ] n/a - Require new or adjusted data inputs? Does it have start, end and duration code (in UTC)?
[ ] n/a - If new or updated data sets, has the FIM code been updated and tested with the new/adjusted data (subset is fine, but must be a subset of the new data)?
[ ] n/a - Require new pre-clip set?
[x] Has new or updated python packages?

Issuer Checklist (For developer use)
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.

[ ] Informative and human-readable title, using the format: [_pt] PR: <description>
[ ] Links are provided if this PR resolves an issue, or depends on another other PR
[ ] If submitting a PR to the dev branch (the default branch), you have a descriptive Feature Branch name using the format: dev-<description-of-change> (e.g. dev-revise-levee-masking)
[ ] Changes are limited to a single goal (no scope creep)
[ ] The feature branch you're submitting as a PR is up to date (merged) with the latest dev branch
[ ] pre-commit hooks were run locally
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] CHANGELOG updated with template version number, e.g. 4.x.x.x
[ ] Add yourself as an assignee in the PR  as well as the FIM Technical Lead

Merge Checklist (For Technical Lead use only)

[ ] Update CHANGELOG with latest version number and merge date
[ ] Update the Citation.cff file to reflect the latest version number in the CHANGELOG
[ ] If applicable, update README with major alterations

Did a jupyter test to make sure it was good.


Docker issues.

Not sure why, struggling to dig into it, but resource loader seems to struggle to unpack resources when running within a docker instance.
I'm trying to get the full stack, but it looks like it never unpacks from the jar correctly:
co.libly.resourceloader.ResourceLoaderException at SealedBoxEncryptorKtTest.kt:15
        Caused by: java.io.FileNotFoundException at SealedBoxEncryptorKtTest.kt:15

Works find on windows/osx

Hi @chrisjenx,
Thank you for raising this. So it's struggling to unpack in a docker image 🤔

What is the base docker image you're running? Just so I can replicate this.
What files were unpacked?

Just to clarify, I don't think this is libly's fault, but does worry me, that it could affect some docker containers.
For us we're using a circleci/android container, I'm struggling to get a full stack trace and see what the tmp structure looks like.
It's more of an FYI for other people.

Hi @chrisjenx,
Just realised you're the author of Calligraphy! I've used it so many times in my Android projects so thank you very much for that! 😁
I made myself a very brief docker container and tested it. It does indeed crash inside docker containers. This is not ideal at all and I will try and fix it. Example stacktrace:
Exception in thread "main" co.libly.hydride.utils.LibraryLoadingException: Failed to load the library using /tmp/hydride/libhydrogen.so
        at co.libly.hydride.utils.LibraryLoader.loadLibrary(LibraryLoader.java:182)
        at co.libly.hydride.utils.LibraryLoader.loadBundledLibrary(LibraryLoader.java:152)
        at co.libly.hydride.utils.LibraryLoader.loadLibrary(LibraryLoader.java:116)
        at co.libly.hydride.Hydrogen.<init>(Hydrogen.java:30)

Just found a solution. It seems that if you are using alpine images they don't include glibc. The solution provided here is very helpful.
So to solve this issue you can do one of 3 things it seems:

Use a docker base that does in include it. That is, use FROM openjdk:8-jre-slim.
If you don't want to switch your base image then you can Install glibc via RUN apk update && apk add --no-cache libc6-compat
Or alternatively RUN apk update && apk add --no-cache gcompat

Hope that works 👍

Awesome, thanks for looking into this. That's great to hear! We moved to
Android tests for this specifically but if we do something on the backend
for this I'll give this a go!
Hopefully if anyone else has a similar issue they will see this.
On Sun, Nov 17, 2019, 4:11 PM Gurpreet Paul<EMAIL_ADDRESS>wrote:

Just found a solution. It seems that if you are using alpine images they
don't include glibc. The solution provided here
https://stackoverflow.com/questions/50288034/unsatisfiedlinkerror-tmp-snappy-1-1-4-libsnappyjava-so-error-loading-shared-li/
is very helpful.
So to solve this issue you can do one of 3 things it seems:

Use a docker base that does in include it. That is, use FROM
openjdk:8-jre-slim.
If you don't want to switch your base image then you can Install
glibc via RUN apk update && apk add --no-cache libc6-compat
Or alternatively RUN apk update && apk add --no-cache gcompat

Hope that works 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/libly/resource-loader/issues/2?email_source=notifications&email_token=AAI5DMMJ6IZJB6YUIWCKDS3QUHFTVA5CNFSM4JJ23FLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEIY5UY#issuecomment-554798803,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI5DMOEUGFTVGWZZQSWYQ3QUHFTVANCNFSM4JJ23FLA
.


Bug in Profiler with Postgresql 11.19

Affected module
Does it impact the UI, backend or Ingestion Framework?
Profiler
Describe the bug
A clear and concise description of what the bug is.
Profiler fails
[2023-07-18 08:30:29,437] {metadata_rest.py:111} WARNING - Failed to sink profiler & test data for Datavault Dev Old.postgres.learning.lms_users: Non-standard token 'NaN': enable JsonReadFeature.ALLOW_NON_NUMERIC_NUMBERS to allow
at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 44532] (through reference chain: org.openmetadata.schema.api.data.CreateTableProfile["columnProfile"]->java.util.ArrayList[44])
To Reproduce
Screenshots or steps to reproduce
It fails with this table structure:
CREATE TABLE learning.lms_users (
user_id text NOT NULL,
username text NULL,
first_name text NULL,
last_name text NULL,
email text NULL,
uuid text NULL,
is_manager bool NULL,
fullname text NULL,
lang_code text NULL,
last_access_date timestamp NULL,
last_update timestamp NULL,
creation_date timestamp NULL,
status text NULL,
avatar text NULL,
"language" text NULL,
expiration_date text NULL,
"level" text NULL,
email_validation_status text NULL,
send_notification text NULL,
timezone text NULL,
date_format text NULL,
field_4 text NULL,
field_5 text NULL,
field_8 text NULL,
field_9 text NULL,
field_12 text NULL,
field_13 text NULL,
field_16 text NULL,
field_17 text NULL,
field_20 text NULL,
field_23 text NULL,
field_24 text NULL,
field_25 text NULL,
encoded_username text NULL,
multidomains text NULL,
managers text NULL,
role_id text NULL,
role_title text NULL,
active_subordinates_count int8 NULL,
actions text NULL,
expired bool NULL,
"manager_names.1.manager_title" text NULL,
"manager_names.1.manager_name" text NULL,
"manager_names.1.manager_username" text NULL,
"manager_names.1.manager_id" float8 NULL,
field_26 text NULL,
field_28 text NULL,
field_29 text NULL,
newsletter_optout text NULL,
newsletter_optout_date text NULL,
CONSTRAINT lms_users_pk PRIMARY KEY (user_id)
);
Expected behavior
A clear and concise description of what you expected to happen.
Successful profiler run
Version:

OS: [e.g. iOS] Docker environment <IP_ADDRESS>
Python version:
OpenMetadata version: [e.g. 0.8]
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.

@isoctcolo feel free to contribute for the same as we don't have many requests for the same.
Looks like 11.19 / 11.21 is near EOL support, Thanks.
Let me know if that works for you, or else will be closing the ticket in couple of days. We can reopen it if someone wants to work on it post that based on request.

@ayush-shah please close it - you are right and 11.x is a special version for maintaining


SAK-29665 add user id tracking to google universal analytics

@csev look good?

Does this need a warning to users that they are being tracked?
sent from my mobile device
On 11 Jul 2015 6:14 am, "Sam Ottenhoff"<EMAIL_ADDRESS>wrote:

@csev https://github.com/csev look good?
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/856#issuecomment-120510932.

@steveswinsburg  I believe that just being tracked in general might be something that you'd need to put up a notice about as part of the EU cookie law (and other countries that might have that) done in #624 maybe just modify that? You could probably have a new feature to opt out of GA or userId tracking since it isn't critical to actually using Sakai. To actually have this, the administrator of the system has to enable it in the GA dashboard.

I am almost certain this will breach the Australian Privacy Principles in
terms of unnecessary collection of personal info. However if it's disabled
by default with big warnings when enabling then we are fine and it's up to
the installation to abide by them.
sent from my mobile device
On 11 Jul 2015 11:59 am, "Code Hugger (Matthew Jones)" <
<EMAIL_ADDRESS>wrote:

@steveswinsburg https://github.com/steveswinsburg I believe that just
being tracked in general might be something that you'd need to put up a
notice about as part of the EU cookie law (and other countries that might
have that) done in #624 https://github.com/sakaiproject/sakai/pull/624
maybe just modify that? You could probably have a new feature to opt out of
GA or userId tracking since it isn't critical to actually using Sakai. To
actually have this, the administrator of the system has to enable it in the
GA dashboard.
—
Reply to this email directly or view it on GitHub
https://github.com/sakaiproject/sakai/pull/856#issuecomment-120562654.

Looks good.  We could make a separate property for this (yes I know 20 lines of stuff for a 1 line change) - but that way each could be turned on/off separaterly to make various jurisdictions happy.

I don't think there's any point for a property. An admin turning it on also has to explicitly enable it in GA (by default disabled) nothing happens by default without doing this, the user doesn't know either way if they're using this or not (if they know/care enough to even look for GA javascript). The only usefulness I can see would be as a user preference to avoid being tracked (though I think most people who really didn't want to would run a browser plugin) or as a notification as part of the cookie notification.

I agree with Matt here. Google Analytics support is disabled by default. If your institution or jurisdiction has strict privacy rules, you should not sign up for a Google Analytics account and should not enable it in Sakai.
My intention is to commit this one-line change in the next 24 hours unless there is a compelling case how this change alters expectations of the existing use of GA.


Grammar fixes identified while validating the grammar against the DMD "compilable" test suite

I am using the DMD "compilable" test corpus as one of the steps of validating the D tree-sitter grammar, which is based on the official specification that will be adjusted here.
This validation identified files in this test corpus which compile successfully using DMD, but are currently not valid programs as specified by the grammar in the language's official specification.
As most of these are due to errors and omissions in the grammar specification (as opposed to compiler bugs), this pull request will contain the necessary fixes to sync up the grammar with the compiler behavior.
Note that this pull request is based on, and includes, #3019, which at the time of writing is not yet merged, so all commits in #3019 also appear here.

I am probably going to close this and submit the fixes above as individual PRs, as the lot is too much to review in one go.

Done:

https://github.com/dlang/dlang.org/pull/3033
https://github.com/dlang/dlang.org/pull/3034
https://github.com/dlang/dlang.org/pull/3035
https://github.com/dlang/dlang.org/pull/3036
https://github.com/dlang/dlang.org/pull/3037
https://github.com/dlang/dlang.org/pull/3038
https://github.com/dlang/dlang.org/pull/3039
https://github.com/dlang/dlang.org/pull/3040
https://github.com/dlang/dlang.org/pull/3041
https://github.com/dlang/dlang.org/pull/3042
https://github.com/dlang/dlang.org/pull/3043
https://github.com/dlang/dlang.org/pull/3044
https://github.com/dlang/dlang.org/pull/3045
https://github.com/dlang/dlang.org/pull/3046
https://github.com/dlang/dlang.org/pull/3047
https://github.com/dlang/dlang.org/pull/3048
https://github.com/dlang/dlang.org/pull/3049
https://github.com/dlang/dlang.org/pull/3050
https://github.com/dlang/dlang.org/pull/3051
https://github.com/dlang/dlang.org/pull/3052
https://github.com/dlang/dlang.org/pull/3053
https://github.com/dlang/dlang.org/pull/3054
https://github.com/dlang/dlang.org/pull/3055


Implement serve

Implement a command, serve, which opens a web server for a specified WARC file - automatically rewriting archived URLs to resources to point to any archived resource.
larch serve -p 8080 ./example.net.warc

By default, the originally archived resource will be served. If the archive contains multiple sites or was created externally of Larch, a sitemap should be shown instead.

Potentially create a resource map on ingest using a serialized, human-readable, larch-specific metadata format. Used to signify HTTP resources, their URLs etc. so that a resolver can more easily manage an archive.

I've implemented a basic serve function. I created a "control panel" which can be accessed under /larch (on by default, but toggleable). It lets the user list available records and their headers and payloads.

https://golang.org/pkg/io/fs/#FS

There's been some progress on this with the serve command.
Example:
larch archive --url https://news.ycombinator.com -o data/hackernews.warc
larch serve --site news.ycombinator.com data/hackernews.warc

This will serve any resource under any protocol for the news.ycombinator.com site. It does not yet handle rewriting of the site inside of the response, meaning CSS etc. does not work.
Another issue is how to accurately handle scraped content. For example, say we scrape https://google.com, but it includes content from https://www.google.com. These are technically two different sites, meaning we can't unambiguously serve content from a single site (namely localhost and a port).
One way to solve this would be adding another route under /_/larch/ or the like to handle requests like the following:
http://localhost:8080/_/larch/rewrite/https/www.google.se/443/resource.png
http://localhost:8080/_/larch/rewrite/http/localhost/8080/local.html

Then the --site parameter specifies what site is served under / and all available records mentioned in the response are rewritten to /... if it's the same site as the served one, or /_/larch/rewrite/... otherwise. Non-archived resources are not rewritten.

Further progress made. I went with the direction specified in the previous comment, with resources served under paths such as /larch/resource/http/www.google.se/443/robots.txt.
The last piece of the puzzle should be rewriting served html resources.


Auth Backend in airflow.cfg

[api]
# How to authenticate users of the API
auth_backend = airflow.api.auth.backend.default

the auth_backend should be at WEBSERVER topic not API
Cheers!

@rudmac this file is part of the official Airflow repo default config. You should open a ticket there if you think this setting is misplaced.
I think we can close this one.


reload systemd via handler

Is this reload of systemd still needed here? It should be triggered via the handler? Or is this a race condition where systemd has to be reloaded at least once before proceeding?

Hey !
It has to be reloaded the first time because it is the only way Systemd is going to be aware of the new unit file.
Basically this is needed the first time you create the service file. This is the only way I cna be sure the unit file is loaded before attempting to enable/restart the gitea service

@thomas-maurice I've updated my pr to add this as a comment, so there is no confusion in the future :+1:

please use handler and flush_handlers together:
https://docs.ansible.com/ansible/latest/modules/meta_module.html


Documentation needed for ConditionalSpawnerComponent and RandomSpawnerComponent

Description

There are not comments anywhere.
What does offset do?
How does rare prototypes work?
What is gamerules supposed to do? Spawn a game rule?
Does Chance and rare chance have to sum to 1?
Reproduction

Screenshots

Additional context

Resolved by https://github.com/space-wizards/space-station-14/pull/30506


Delete test_approximation_tests branch

I was unable to mirror this repository due to a large file in a five year old unmerged branch.

remote: error: GH001: Large files detected. You may want to try Git Large File Storage - https://git-lfs.github.com.
remote: error: File examples/polygons/geojson/us-counties.geojson is 161.90 MB; this exceeds GitHub Enterprise's file size limit of 100.00 MB

done.
the work in that branch was superseded by #265 (which uses Jasmine's built-in matcher toBeCloseTo)


New JavaScript Code

I have recently started learning JS, so I am adding a basic code.

Adding a folder in the root folder.
Adding the JS file.

Please assign this issue to me @lovishprabhakar02

Go ahead! @divyamkapoor

@divyamkapoor as a JavaScript folder has already been created by another contributor, you can add your files in that folder

hi @divyamkapoor. We see that their hasn't been any update regarding this issue so we plan on to close this issue for now. In future if you want to contribute regarding the same, you can open the same issue again.

hi @divyamkapoor. We see that their hasn't been any update regarding this issue so we plan on to close this issue for now. In future if you want to contribute regarding the same, you can open the same issue again.


Undulator scanning routines using Sirepo-Bluesky

Based on:

https://github.com/NSLS-II/sirepo-bluesky/pull/70
this notebook by @thomaswmorris

@awalter-bnl, should we merge it and move on with the updates in a separate PR, or do we want to finish it here?

@awalter-bnl, should we merge it and move on with the updates in a separate PR, or do we want to finish it here?

@mrakitin , sorry just seeing this now. I don't have strong opinions so I am happy to do either. MY preferences is always not to merge incomplete work, but as this is early in the development cycle of this perhaps it is fine.


fix: export drawings in export (if persist is true)

Fixes https://github.com/slidevjs/slidev/issues/692
Added a new global variable __USE_SERVER__ and a new "export" mode:

mode="dev" means __DEV__=true and __USE_SERVER__=true
mode="export" means __DEV__=false and __USE_SERVER__=true
mode="build" means __DEV__=false and __USE_SERVER__=false

I didn't forced the export to be in dev mode because in that mod we renders additionnal things like the Monaco editor...etc. we won't use in the export.

We could have it once conflicts are solved

Fixed :)


.swo file inadvertently commited

this file needs to be removed from the repo
lib/Framework/.startApp.php.swo (vim temp file)

#87

corrected with PR #87


chart-testing: 3.5.0 -> 3.5.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/helm/chart-testing/releases.
meta.description for chart-testing is: "A tool for testing Helm charts"
meta.homepage for chart-testing is: "https://github.com/helm/chart-testing"
meta.changelog for chart-testing is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/zffvy2h6ghv4vrqy40q61sr1pa9pg5m2-chart-testing-3.5.1/bin/ct had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 3.5.1 with grep in /nix/store/zffvy2h6ghv4vrqy40q61sr1pa9pg5m2-chart-testing-3.5.1
found 3.5.1 in filename of file in /nix/store/zffvy2h6ghv4vrqy40q61sr1pa9pg5m2-chart-testing-3.5.1

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
chart-testing

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

chart-testing

Maintainer pings
cc @AtkinsChang @kalbasit for testing.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/466


What about transforming values during parsing?

I have certain constrained types that, through their parsing, also transform the input. Two examples:

For most simple one-line string inputs, I don't reject control characters, I just strip them out. This is usually the first step in the parsing (before validation).
For phone numbers, I use a 3rd party library to simultaneously validate and format them correctly. This is usually done after verifying that the string is not null or empty (e.g. after some validation).

This is trivial with custom code, e.g.:
type PhoneNumber = PhoneNumber of string

module PhoneNumber =

  let parse =
    trim  // trim: string -> string
    >> notEmpty  // notEmpty: string -> Result<string, ParseError>
    >> Result.bind validPhoneNumber  // validPhoneNumber: string -> Result<string, ParseError>
    >> Result.map PhoneNumber

Based on the information in the readme, which demonstrates a list of validation functions, I can't immediately see how to accomplish having some validation steps also transform the value. Is there a simple/canonical way to achieve this with this library?

Right now  type definitions don't support custom input processing, so you have to use Block.verbatim next to your own processing function, which can still be defined with the type itself since you can add any member to it as long as it implements the interface. If #9 gets implemented I'm pretty sure this would have to be part of the package.

Right now  type definitions don't support custom input processing, so you have to use Block.verbatim next to your own processing function, which can still be defined with the type itself since you can add any member to it as long as it implements the interface. If #9 gets implemented I'm pretty sure this would have to be part of the package.


Initial merge with xeus-clang-repl - Capture outputs

Hey @alexander-penev could you maybe squash the commits into a couple meaningful ones. Would make it easier for reviewing !

Hey @alexander-penev could you maybe squash the commits into a couple meaningful ones. Would make it easier for reviewing !

Often squashing loses the previous comments. Maybe we can squash on merge. If you click on the “files changed” tab you will see everything squashed.


Padding adjustments

Padding on header:
before -

after -

Timer padding:
before -

after -

in MetadataEditor
before -

after -

before:

after:

I noticed an issue on smaller screens, but otherwise looks good

i think i can fix this with width and min-width

looks good to me like this. fixed the wrap issue.
https://github.com/compute-toys/compute.toys/assets/8731857/ece46726-a107-4376-9cae-6b548ba6edaa


Headless CMS page

https://www.zesty.io/solutions/headless-cms/
Please fix padding on section below:

Approved, thank you!


'dmm.polyphonic_data_loader' has no attribute 'load_data'

When I run hmm.py example, there is an error.
AttributeError: module 'dmm.polyphonic_data_loader' has no attribute 'load_data'
Then I check the polyphonic_data_loader.py, and I cannot find load_data(). Is there anything missing?
Thank you!

Please use the dev branch of Pyro to run the hmm example. You should be able to see load_data in poloyphonic_data_loader on the dev branch. Note that this will be part of the next release in a few weeks.

i like (3). i was actually thinking of adding a README to examples as a short-term remedy, since most people discover them through the github webpage.

Hi, Thank you very much!

I think (3) is best (i.e. each example has an associated minimum version), since examples might build on functionality that require the dev branch and it might not be feasible to port those changes to master always.


Add TLSv1.2 to cipher list

Add TLSv1.2 to cipher list to prevent "no ciphers available" error

Thanks @l0rb I will try to create a new release with the change asap.


Team 28 Review: FMEA

The list of Failure Modes is comprehensive, however all of the recognized Failures Modes (apart from H-011) are described as being related to functional issues with drone performance, rather than harm to human involvement with the system (ie. operator, drivers, maintenance staff, etc). I would suggest there be more consideration of how these malfunctions ultimately harm humans or their property.

The system environment only consists of the product and the Operator, which is the user. Thus, only that case is considered.
Further interactions with the environment, such as with the drivers and the property, are further specified within the SRS and User Manual.


fix(dispatch-service): fix temporary directories for containers

Closes #4281
Closes #4262
Closes #4302
With this change, I was able to run simulations with Smoldyn in UConn HPC.
I now see this in the log, but it doesn't seem to prevent execution
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

Replaces #4282

:tada: This PR is included in version 9.8.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[BUG] Unable to send tx on EVM

Describe the bug
When sending tokens on EVM chains many times the gas limit of 23,000 is not enough, leading to a failed tx. Especially on Arbitrum.
To Reproduce
Steps to reproduce the behavior:

Go to EVM chain
Send tx with standard gas limit
See error

Expected behavior
Able to send txs on EVMs without problem

Version 1.6.0

Additional context
When increasing gas limit to 100,000 it seems to go through consistently.

is it specifically for ARB? I think on ETH 23000 is enough to send ETH , and we use 100K for ERC20

So far I only could duplicate on ARB

QA done.


Fix lang-xml.isElement() function

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues.

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #20848 into next-release will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           next-release   #20848   +/-   ##
=============================================
  Coverage         20.51%   20.51%
=============================================
  Files                52       52
  Lines              1394     1394
  Branches            216      216
=============================================
  Hits                286      286
  Misses             1095     1095
  Partials             13       13

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 45dc658...76439af. Read the comment docs.


Overhaul Hydra.Router

[x] Support all HTTP verbs
[x] Support paths w/ variables (/example/:variable).

Resources:

Plug.Router.Utils
Plug.Router

This was completed as part of #12.


undefined when rendered.

Since switching my aliases to fix the bug in preact-compat / preact where it aims at /src instead of /dist all the sudden my app renders undefined

Any ideas on what i may be doing wrong here?  I confirmed that the call to render is sending a component

'transform-react-constant-elements' was the problem - should have known

Been bitten by this too!

Might be a good idea to put something in the documentation for switching to preact?

Yup, wherever people would normally be looking when doing the preact-compat alias.


Exponential back off & Mask secrets from log

Check if there are clone erros
Add newExponentialBackOff for clone operations (we have observed frequent DNS/network issues with GitHub - easy to recover from with a retry)
Mask the GitHub token from the log

The fail is due to GitHub rate limit and not due to the PR to the best of my understanding.

Hi @svyotov, thanks for opening a PR for this! I would be happy to add the ability to retry on errors and use exponential back-off for this :slightly_smiling_face:
There is only one issue I see with the current state of the PR: The PR introduces a 3rd-party dependency. For now ghbackup didn't need any 3rd-party library. Since exponential back-off is not a complex algorithm I would rather not introduce an external library for this. If you could change that, I would be happy to merge this :)

Hi @svyotov, thanks for opening a PR for this! I would be happy to add the ability to retry on errors and use exponential back-off for this slightly_smiling_face
There is only one issue I see with the current state of the PR: The PR introduces a 3rd-party dependency. For now ghbackup didn't need any 3rd-party library. Since exponential back-off is not a complex algorithm I would rather not introduce an external library for this. If you could change that, I would be happy to merge this :)

:+1: done

I would merge this now if you don't mind :)

ok, there is a new release now including this PR: https://github.com/qvl/ghbackup/releases/tag/v1.13.0


[ENH] Maintainers Guide

addresses https://github.com/bids-standard/bids-specification/issues/288
Converted the maintainers guide gdoc to markdown to push this forward. There is content that references terms defined in the governance structure (e.g. Steering Group). These details can be deleted and brought back in if the governance document is approved.

Just to bring the review discussion to the top-level, the overall feel of this document seems to be pretty hierarchical, which is not my experience of it now, as one of the de facto maintainers. I think pushing toward a hierarchical organization would be a mistake, as it will tend to engender resentment and avoidance from most people, and positions of power attract abusers.
Just to propose an alternative framing:

The maintainers are a group of people with these duties, and who commit to convene periodic meetings to discuss the project.
Additions to and departures from the group should be negotiated collectively between the group and the new/departing member, as they involve redistribution of duties.

If a maintainer wishes to serve for a limited term, that can be arranged at the start. Otherwise, due notice is expected.
Perhaps some rules about accepting nominations, to ensure the group isn't too insular.

One lead maintainer has the task to represent the group to other BIDS groups, mediate disagreements among members, cast deciding votes when needed, and may delegate any of these duties.

I agree that the current proposal has a hierarchical feeling to it and share the concern that it might impede the maintainers' work rather than facilitate/clarify it.
Note the the current definition of "maintainer" that we have is also much broader than what we discussed until now, see the "maintainer" section in our decision making document
One further note is that so far very few people have commented on the maintainer guide, notably @effigies @franklin-feingold @nicholst and @sappelhoff
I feel like this PR was initiated a bit through my nudge in this comment but I was actually aiming at getting more feedback for @franklin-feingold's draft (through setting a deadline and an order) rather than merging it. So it's good that we're having more discussion now :-)

It appears there are some fundamental changes that are in order to this current iteration of this document. Perhaps this will be easier to revert back to the google doc to more dynamically work on and reach a consensus on the language and framing then return back to a PR for minor enhancements. I think there are a number of points (some raised here) to hash out and discuss for this to be an accepted document detailing out the role description and responsibilities of a BIDS Maintainer

Perhaps this will be easier to revert back to the google doc to more dynamically work on and reach a consensus on the language and framing then return back to a PR for minor enhancements.

sounds good, I'll take some time and write up something based on comments by @effigies

sounds good - closing this


[Bug]: Something went wrong

Contact Details
No response
What happened?
i used full cookies but only asked once and next time got error and i followed this https://github.com/danny-avila/LibreChat/issues/727#issuecomment-1659407747 ,but still not working
Steps to Reproduce
Normal conversation.
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Screenshots

Code of Conduct

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

To some people, it works even after the second message, while for others it doesn't. Since no API key is being used, it's difficult to understand the problem. I also have the same issue and if I want to use Bing, I select Sydney (which works even after the second message). Take a look here

To some people, it works even after the second message, while for others it doesn't. Since no API key is being used, it's difficult to understand the problem. I also have the same issue and if I want to use Bing, I select Sydney (which works even after the second message). Take a look here

Thanks for the tips. It helped me a lot!


Added a Contributing.md sample

Open for discussion

This is awesome!

I just read through it.  I think it's an excellent start and unless there's objection, I think this should merged.
I do think that new features should likely start out as issues in the issue tracker; probably with a little template that proposes the change, is it an addition or a change to an existing feature etc.  With a standard period (maybe a week to start with) to allow community comment.  This could be done with a templated PR rather than issues (may be more appropriate)
Having said all that, I don't think too many PRs pulling things in odd directions is a problem right now, so even without setting any of that up, I think this is a good start.
If I don't hear anything to the contrary (and if it hasn't happened yet) I'll go ahead and do the merge on Tuesday evening (my time).
Many thanks for this @mmattes!


Raspberry shuts itself down

Describe the bug
Raspberry Pi4+ runs without any Problems, as long as the Photobooth APP is running, but no camera is connected. As soon as the Camera is connected it takes between 1-3 minutes and the pi is no longer reachable.
To Reproduce
Steps to reproduce the behavior:

Start Photobooth
Connect Camera
Wait for 1-3 Minutes
See error

Expected behavior
Should be reachable without any problems.
I´ve attached the logfile; can someone help me?
photobooth_20240526.log

There is in current version some issue that causes a high cpu load when the connection to the camera breaks.
Maybe this is causing the RPI to be inresponsive because the webserver answers only very very slow then.

hmm - is there a older version that hasn´t had this issue? Or is there a workaround? Do you know why the connection breaks? Is there something we could do about that?

Actually, the high cpu load is a problem that occurs after the connection broke. So if the connection is OK, the cpu won't see high load.
Please ensure the cabling is right and rebooth the whole system as well as restart the camera. Do not enable RAW files in the camera helps also. Do not enable the AUTO mode but just a bit more manual as there seem to be issues with gphoto2 and auto mode.

changes have been made here, but it really only helps if things gone wrong before already: https://github.com/photobooth-app/photobooth-app/commit/9f7e23439f49d1e6138f772c054fdd8c720a9fa9

You could update to the latest version that is released as a beta now: https://pypi.org/project/photobooth-app/3.1b0/

thank you very much for your fast response; I found out that disabling the option "Interrupt liveview for Photo" (or something similar - do not have the exact name in mind) helps; After that everything worked; Anyway, I´ll try to update to the beta version;

ok I´ve justed updated to the version you´ve created - so fare everything works really fine; the camera gets recognized and everything is running stable (at least for the last hour);
the only lasting mistake was that the selfstarting of the service after a reboot; I run the pi headless by the way; I solved it with a cronjob and the following line:
@reboot systemctl --user start photobooth-app.service

too earlie - as soon as i close putty the service ends; does this happen because there is no screen connected to the pi?

No need for a screen. What happens?
There is no need for the cronjob usually it will start automatically on boot.

Maybe the app shuts down because it was opened in the console?
Regular version 3.1.0 is out, so maybe you can update to that version.

I´ve just updated to the latest version. Even got on of the Canon Selphy Printers to work. What I found out:

App is running stable as long as you aren´t connected via any ssh console
App is running stable as long as you are connected to the gui with just one console
App is running stable as long as you use a capable enddevice (used some old tablets and the had a big delay [showed countdwon number 2 from 5 but picture was already taken])

Just one last question - I´m no longer able to login to the admin page [wrong password] - have you changed anything about that? Or ist the password stored somwehere in the config?

Yes, to avoid users accessing the system there is a password now: https://github.com/photobooth-app/photobooth-app/releases/tag/v3.1.0
Default is 0000

There is a setting in backends called livestream_framerate. For old devices you could lower the number , maybe it works for them. Otherwise the device is not capable to run the app.


Issue 97 icons layout

Fix #97
🔗 Test URLs:

Before: https://main--caesars-careers--hlxsites.hlx.page/careers/drafts/khosannah/why-caesars
After: https://issue-97-icons-layout--caesars-careers--hlxsites.hlx.page/careers/drafts/khosannah/why-caesars

📝 Description:
Fixed responsiveness

Seems like the last icon is missing:

(Bottom right)


DNF support

Will DNF support be included soon?  I think there was a DNF workaround included in Chef: https://github.com/chef/chef/pull/3774

Hi. What exactly would be required to support DNF from this cookbook?

From just taking a cursory look, I think it would just be mapping the "yum" commands to "dnf" commands like: https://fedoraproject.org/wiki/Yum_to_DNF_Cheatsheet  They tried to keep a one to one mapping but some are different.  If you want, I can attempt to map out what is your cookbook would have to change.  Assuming we are on the same page, I could then attempt a PR if you are willing.

Ah okay. So this would be in chef/chef against the package resource, not chef-cookbooks/yum.
I'm pretty sure this is already being worked on but you should open an issue there.
Closing this here.
-s
—
Sent from Mailbox
On Tue, Oct 13, 2015 at 11:03 AM, St. Isidore de Seville
<EMAIL_ADDRESS>wrote:

From just taking a cursory look, I think it would just be mapping the "yum" commands to "dnf" commands like: https://fedoraproject.org/wiki/Yum_to_DNF_Cheatsheet  They tried to keep a one to one mapping but some are different.  If you want, I can attempt to map out what is your cookbook would have to change.  Assuming we are on the same page, I could then attempt a PR if you are willing.
Reply to this email directly or view it on GitHub:
https://github.com/chef-cookbooks/yum/issues/132#issuecomment-147797411

What I am referring to here is not the creation or management of a dnf_package resource like a yum_package resource, I am referring to how the repositories are managed.  From what I can tell, the DNF repository configuration is the same as the YUM repository configuration.  The only difference is the main configuration is located at /etc/dnf/dnf.conf.  See http://dnf.readthedocs.org/en/latest/conf_ref.html for an explanation.
I guess the point I am getting to get to is the fact that since DNF is the upgrade to YUM and they are managed in "almost" exactly the same way, should this cookbook support the DNF that is used in the newer Fedora environments?  Otherwise those guys are without repository management in Chef until this gets resolved.

reopening

The latest release makes yum_repository happy on fedora-22, so I'm going to close this for now.

awesome @someara.  just out of curiosity is there something we should probably be doing for a long term fix or should I just raise that issue as it arises?

I believe there's a DNF package provider being worked on, which is
definitely needed.
As for repository configuration, if DNF proves to be different enough than
yum to warrant a separate dnf_repository resource that "provides
:yum_repository" on the appropriate platforms, we can cross that bridge
when we get to it.
-s
On Wed, Oct 28, 2015 at 3:49 PM, St. Isidore de Seville <
<EMAIL_ADDRESS>wrote:

awesome @someara https://github.com/someara. just out of curiosity is
there something we should probably be doing for a long term fix or should I
just raise that issue as it arises?
—
Reply to this email directly or view it on GitHub
https://github.com/chef-cookbooks/yum/issues/132#issuecomment-151969982.


Will do custom Youtube player.

The new repository: https://github.com/PaulHost/youTubeCastomPlayer

is it new task for us?

No, it's not. Thanks for sharing you updates


AWS Swapping Revision Number on Release

A recent release broke email functionality in Doorway briefly because it unexpectadly used a very old set of environment variables (revision number 4). This ticket is to investigate why that occurs and how to prevent releases from taking old revision sets.

@ColinBuyck is this still relevant?

Yes. We've sort of resolved it by deleting all other revision version numbers but that's not the most sustainable approach.

hasn't bitten us recently, but still need a long term fix


added environment variables for dev observatorium and creation timestamp label into metrics

added params as a environment variable for dev observatorium to read value from secret and pass to observability cr.
Added label for creation timestamp into inventory, connection, and instance status metrics, to know when particular object was created.
Description

Verification Steps

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[ ] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

@redhatHameed What about using separate metrics for the creation time stamp itself instead of adding it to each metric (like what kube state metrics does)?  This is because there are multiple metrics for each inventory/instance/connection CR, and in the future, we may want to add additional metrics.

@redhatHameed What about using separate metrics for the creation time stamp itself instead of adding it to each metric (like what kube state metrics does)? This is because there are multiple metrics for each inventory/instance/connection CR, and in the future, we may want to add additional metrics.

At the moment, we have requirements like, when inventory/connection/instance created, what is the status, who is the provider, so with the single metrics we are getting all the required information.
if we need to define extra metrics for creation time, then we have to query multiple metrics to get information.

@redhatHameed Just realized you updated the PR and removed the creation timestamp related changes. Could you update the PR description?

it's there not removed just updated to add timestamp to request duration metrics :)

OK

hey guys, I believe AH has addressed all initial feedback, PTAL? Thanks!

@jianrongzhang89 @jeremyary @tchughesiv @xieshenzh  rebased the PR with main- Please have a another look thanks


有时会出现电线杆和写有英文的房子

Sometimes there are electric line poles on the hill or houses with english words. 有时会出现电线杆和写有英文的房子。

I'm at the PIZZA HUT.
I'm at the TACO BELL.
I'm at the combination Pizza Hut and Taco Bell.

@georgel2020 author itself put the "Pizza Hut" text as a easter egg (supposedly)
if (sto == 1 && Math.random() < 1 / 3) {
          pla = [1, "Pizza Hut"];
        }

where the sto mean number of stories of the building and pla set the text on the roof of that building.
Based on this code, 33% of single-story buildings should have a Pizza Hut text on the roof.


[Bug] WattTime password enconding non-ASCII

See GSF bug: https://github.com/Green-Software-Foundation/carbon-aware-sdk/issues/181


My large world map is throwing an error

I'm trying to run mcmap on my Ubuntu 11.04 32-bit vps server. I have a large map, and it throws an error when renderingd
The error is shown below:
root@server:~/mcmap# ./mcmap /root/Minecraft/world/
mcmap 2.2 by Zahl
McRegion world format detected.
Scanning world...
Min: (-199|-239) Max: (198|262)
Image dimensions are 17994x9258, 32bpp, 635.48MiB
terminate called after throwing an instance of 'std::bad_alloc'
what():  std::bad_alloc
Aborted
The map size is a 3000 block radius circular map.

nvm seems my vps hasn't got the ram :(

Check the help output, there's a way to limit the mem usage ;)
Just run ./mcmap with no parameters to see all the available options.


How to clear or change Badge in iOS / Android locally

It would be nice to have a method that would allow either clearing or changing the Badge.
IE: Once the user has reviewed notification(s) within our app, I want to be able to reset the badge from within our cross platform app.
Currently it seems the badge will change based on the badge value received by the notification, however there doesn't seem to be a way to reset the badge locally.
Is there a way to do this?  If not, is there a relatively easy technique for doing this in Xamarin Forms, and ultimately could this feature be added within the plug-in?

On iOS at the moment I just reset the badge count when the app comes into the foreground:
`        public override void OnActivated(UIApplication uiApplication)
{
UIApplication.SharedApplication.ApplicationIconBadgeNumber = 0;
base.OnActivated(uiApplication);
}
` not the best solution, especially when using badges on the tabs within the app.
Busy with the the android implementation and then back to iOS, if I get something solid worked out for both, will let you know.

Thanks for the interim workaround - I'll give that a whirl.
It would be nice to see this incorporated into the plug in in the near future just to complete the feature set.

@TimesliceTechnologies So I gave up getting this plugin to work properly with Firebase, and especially the iOS side of things. Using OneSignal Xamarin SDK, surprisingly easy to implement and a lot of features on their console, plus it's free(supports unlimited devices and notifications)


CppTest.cpp is stored as UTF16

This is great work!
CppTest.cpp causes error on linux because of its character code. It has BOM so it may be treated correctly on Windows.
iconv -f UTF16 -t UTF8 < CppTest.cpp

Thanks! Not sure how it ended up becoming UTF16.
It's now fixed in 1cf512d.


lxc command to just create a container

From what I see, there is no lxc command to just create a container. The launch command creates and  runs a container.
There isn't the equivalent of a lxc-create only command in lxc client to stay with backwards "compatability".

lxc init

Thanks hallyn, just as you wrote this I saw the init command. Very confusing though. Why not just call it create?

The naming of that particular command was an executive decision which we can't really do much about. Create was one of the proposed alternatives which was then rejected.
Note that with the alias mechanism, you can edit your .config/lxc/config.yml and define an alias for "create: init" which will do what you want.


increased responsiveness of manage workflow

Details
Makes table at manage workflow responsive to mobile devices by adding horizontal scroll to it.
Closes #5
Before

After

Looks good to me - thanks @tanya17-05 :)
@git-anurag-hub: if it's fine with you, please merge


Multiple scans to exploit fermi's concurrent kernel execution feature

Suppose I have multiple scan jobs to do. Each has different length so I can't
use the cudppMultiScan API. Is it possible to add a stream interface so that I
can take advantage of the concurrent kernel execution in fermi? Of course, it
is only beneficial if each scan job is relatively small and can't fully use the
gpu resource.

Your response is highly appreciated!

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 30 Mar 2011 at 6:12

This sounds like a job for cudppSegmentedScan, not cudppMultiScan.

Please post questions like this on the CUDPP Google Group rather than creating
issues.  Closing this.

Original comment by<EMAIL_ADDRESS>on 30 Mar 2011 at 10:01

Changed state: Done
Added labels: Type-Other, Priority-Low
Removed labels: Type-Defect, Priority-Medium