Alarm sound is playing in delay of 5 seconds

Alarm plugin version
latest
Describe the bug
Alarm sound is playing in delay of 5 seconds. I am setting an alarm for DateTime.now() and only after 3 seconds the alarm rings
To Reproduce
Steps to reproduce the behavior:
final alarmSettings = AlarmSettings(
      id: _ringingId,
      dateTime: DateTime.now(),
      assetAudioPath: assetAudioPath,
      loopAudio: false,
      vibrate: LocalMemory.vibrationOnAlarm!.value,
      enableNotificationOnKill: false,
    );
 await Alarm.set(alarmSettings: alarmSettings);

Expected behavior
The alarm needs to go off in the same time it setts. Maybe 1 second delay
What I would do is putting if (dateTime is  close to the time now) in android alarm.dart, so play alarm and not call AndroidAlarmManager.oneShotAt
Screenshots

Device info
Pixel 6, android 13

Hi @dtkdt100,
Thanks for your interest in the plugin.
I must use AndroidAlarmManager.oneShotAt because if I don't, the alarm won't ring if the app is in background. This method creates an isolate to ensure that the code in playAlarm is executed whether app is in foreground or background.
Furthermore, I'm not sure that's the reason of the delay. I think a reason that could explain the delay is if the audio asset is large, because the player has to load it before being able to play it.
Do you have this issue with the example app ? If not, is your audio asset large ?

Hi, @gdelataillade . Thank you so much for replaying so fast!
The whole point of my issue that you don't need to use background alarm, because the datetime is so close (I mean in a metter of milliscronds to one second). Checkout my fork https://github.com/Dolev-Franco/alarm It is working good (you just need to add a if statement - if date is close).
My asset is not to large, I know it because in my fork it working well.

Hi @dtkdt100
OK I understand your request. I'll add it to the plugin as soon as I find the time. I'll let you know when it's done.

@gdelataillade
I am going to make a PR for this

@gdelataillade
PR: https://github.com/gdelataillade/alarm/pull/68


3.0.0 dev persistent session pane

Remove refresh button, settings, and session from appBar in examples

Fixed in: https://github.com/MIT-CAVE/cave_app/commit/5fd5a981e1b2403685919d34c38fb14d8f02e463


Thank you for making this library

This is the best QR code library I've found on the entire internet! It has exactly everything I need and works flawlessly.
Thank you for taking the time to build and open-source this.

@dillionverma thanks a lot for your feedback :)


Upgrade packit.yaml config to have integration tests

This pull request introduces the execution of leapp integration tests as a packit job instead of the current behavior of using a GitHub Actions to trigger the tests by a comment.
Signed-off-by: Rodolfo Olivieri<EMAIL_ADDRESS>

Maybe some targets will fail right now because of:

This is the first time I'm trying this without my demo repository
Packit will deploy the latest changes to production tomorrow, so some workflows will fail until then

/packit test oamg/leapp-repository#master

/packit test oamg/leapp-repository#master

/packit test oamg/leapp-repository#989

/packit test https://github.com/oamg/leapp-repository/pull/989

/packit test https://github.com/oamg/leapp-repository/pull/988

/packit test oamg/leapp-repository#990

/packit test oamg/leapp-repository#990

/packit test

/packit test oamg/leapp-repository#990

/packit test oamg/leapp-repository#990

@fernflower the discovery of the rhel-7.9-rhui tests are failing right now because of this comparison distro == rhel-7.9, I think.
packit is passing the distro name in a slightly differently way --context distro=RHEL-7.9-rhui. If I manually change to  when: distro == RHEL-7.9-rhui it works just fine.
I'm not sure if packit offers a way to pass a different context/distro name in the request. @TomasTomecek could you help us here?
If that's not possible, should we change the condition in the test then, @fernflower?

Hello @r0x0d , I first thought that this is a problem with the -rhui suffix, however it turns out that it is a problem with how fmf/tmt evaluate context. Currently, it is case-sensitive (this is undocumented), consider the following plan:
execute:
    how: tmt
    script: /bin/true
enabled: false
adjust:
    enabled: true
    when: distro == rhel-7.9

With tmt -c distro="rhel-7.9-rhui" run, the plan runs, whereas with tmt -c distro="RHEL-7.9-rhui" run it does not run.
I've filed an issue for fmf: https://github.com/teemtee/fmf/issues/186 and we are going to dicuss this tomorrow at tmt hacking session with other tmt contributors. We may add some form of case-insensitivity to context matching. For packit, we also have https://github.com/packit/packit-service/issues/1797 to provide custom context, however I do not think that passing a custom distro will/should be supported. The distro value depends on what you have in target in your config (and this is passed to Testing Farm as compose), it IMO does not make much sense to override this.
You could try using rhel-7.9-rhui as your target in the config but I am not sure if that will work, it depends on how Testing Farm matches composes (if it is case-sensitive or not). Alternatively, you could use a workaround such as when: distro == rhel-7.9 or distro == RHEL-7.9.

Hello @r0x0d , I first thought that this is a problem with the -rhui suffix, however it turns out that it is a problem with how fmf/tmt evaluate context. Currently, it is case-sensitive (this is undocumented), consider the following plan:
execute:
    how: tmt
    script: /bin/true
enabled: false
adjust:
    enabled: true
    when: distro == rhel-7.9

With tmt -c distro="rhel-7.9-rhui" run, the plan runs, whereas with tmt -c distro="RHEL-7.9-rhui" run it does not run.
I've filed an issue for fmf: teemtee/fmf#186 and we are going to dicuss this tomorrow at tmt hacking session with other tmt contributors. We may add some form of case-insensitivity to context matching. For packit, we also have packit/packit-service#1797 to provide custom context, however I do not think that passing a custom distro will/should be supported. The distro value depends on what you have in target in your config (and this is passed to Testing Farm as compose), it IMO does not make much sense to override this.
You could try using rhel-7.9-rhui as your target in the config but I am not sure if that will work, it depends on how Testing Farm matches composes (if it is case-sensitive or not). Alternatively, you could use a workaround such as when: distro == rhel-7.9 or distro == RHEL-7.9 in the meantime (before fmf is extended).

Hi, @FrNecas! Thank you for your reply and for all that explanation.
I will make sure that I follow both of those issues to keep updated with the current state of them. Also, for the workaround part, I will leave that decision to the @oamg/qe to see if it really fits in their use case or if they would like to go with some other route too. In any case, thanks again, I will wait a bit more for https://github.com/teemtee/fmf/issues/186.

@fernflower the discovery of the rhel-7.9-rhui tests are failing right now because of this comparison distro == rhel-7.9, I think.
packit is passing the distro name in a slightly differently way --context distro=RHEL-7.9-rhui. If I manually change to  when: distro == RHEL-7.9-rhui it works just fine.
I'm not sure if packit offers a way to pass a different context/distro name in the request. @TomasTomecek could you help us here?
If that's not possible, should we change the condition in the test then, @fernflower?

Hi @r0x0d , if we change the condition in the test to 'distro == RHEL-7.9-rhui' then this test won't be run in case of a typical rhel-7.9 upgrade and we will need to duplicate the test, which is not really a favorable outcome because it becomes harder to maintain. It would be great to solve that on packit side imho, but of course if it doesn't work we can go back to discussing changes in the test.

@fernflower the discovery of the rhel-7.9-rhui tests are failing right now because of this comparison distro == rhel-7.9, I think.
packit is passing the distro name in a slightly differently way --context distro=RHEL-7.9-rhui. If I manually change to  when: distro == RHEL-7.9-rhui it works just fine.
I'm not sure if packit offers a way to pass a different context/distro name in the request. @TomasTomecek could you help us here?
If that's not possible, should we change the condition in the test then, @fernflower?

Hi @r0x0d , if we change the condition in the test to 'distro == RHEL-7.9-rhui' then this test won't be run in case of a typical rhel-7.9 upgrade and we will need to duplicate the test, which is not really a favorable outcome because it becomes harder to maintain. It would be great to solve that on packit side imho, but of course if it doesn't work we can go back to discussing changes in the test.

@fernflower just a follow-up on that, me and @FrNecas were talking about this issue today, and we thought that leapp would benefit more from https://github.com/packit/packit-service/issues/1797 as it will let us define custom contexts are you guys have currently in your GitHub actions testing farm workflow.
The main breakdown on all of this is that tmt will stick with being case-sensitive and will document that for future uses. So, looking for alternatives, we realized that waiting and going for https://github.com/packit/packit-service/issues/1797 would be more clean and suitable for leapp right now.

Waiting for https://github.com/packit/packit-service/issues/1797

Hi, @pirat89 and @fernflower if you could take a new look at the errors, it would help so much!

@r0x0d sorry for the late response - deadlines & post-deadlines works...  we are aware of issues in tests intself. Not sure whether they are already fixed.

/packit test

/packit test

@r0x0d I am so sorry I missed your request for review :( I will take a look asap

@r0x0d Okay, there is definitely something fishy going with leapp package installation, it's trying to install {} instead of a valid package - http://artifacts.osci.redhat.com/testing-farm/e95a46df-a29a-48bc-9e79-9d25f619ad05/guest-setup-56657bef-1dc5-489a-b317-397cfc0bc15c/artifact-installation-56657bef-1dc5-489a-b317-397cfc0bc15c/3-Install-packages.txt

Okay, /packit test DOES NOT rebuild anything, it just runs the tests with the previous builds.
/packit build will rebuild and run tests.
So doing it the right way now.

@r0x0d Currently I see that all tests are running with build from epel-7, which is not correct - only 7->8 tests should be using builds from epel7, 8->9 should be using epel-8.

/packit test

Okay, looks like installation of leapp-repository via postinstall script doesn't work - the package gets removed during guest setup artifacts' installation :(
So we are back to figuring out how to build and install specific version (master by default) of leapp-repository.
I am gonna try the /packit test oamg/leapp-repository#master and then maybe reach out to packit team and reopen this discussion.

/packit test oamg/leapp-repository#master

/packit test https://github.com/oamg/leapp-repository/pull/1052

Short summary:
Bad news - leapp packit test runs will be complicated until https://github.com/packit/packit-service/issues/1968 lands. As there is no leapp -> leapp-repository dependency, and /packit test is only capable of installint the-leapp-build-from-pr in the test environment, which is not enough for our tests. It is possible to use /packit test oamg/leapp-repository#SOME_LEAPP_REPOSITORY_PR_THAT_STILL_HAS_BUILD_ALIVE to install both leapp and leapp-repository in the test env, but it has the drawback that you have to verify that the selected leapp-repository build is indeed available as packit won't rebuild anything in case it's not.
When the issue #1968 is resolved, it will be possible to run the tests properly with /packit test oamg/leapp-repository#master.
Good news - the approach in this PR can be used for testing leapp-repository already, as there is a leapp-repository -> leapp dependency.

/packit test https://github.com/oamg/leapp-repository/pull/1052

/packit test oamg/leapp-repository#1052

/packit test oamg/leapp-repository#1052

/packit test https://github.com/oamg/leapp-repository/pull/1052

/packit test oamg/leapp-repository#1052

Moving this to draft not to be accidentally merged until https://github.com/packit/packit-service/issues/1972 is delivered.


not work anything :/

not work for me runned as administrator on windows
how it work?

First, make sure config.json and DnsSafeguard.exe are in the same directory (folder). Then, use this in the config file:
{
	"protocol":"h2",
	"server_name": "dns.google",
	"socket_addrs": "<IP_ADDRESS>:443",
	"udp_socket_addrs": "<IP_ADDRESS>:53",
	"fragmenting": {
		"enable": true,
		"method": "single"
	},
	"ipv6": {
		"enable": false,
		"protocol":"h1",
		"server_name": "dns.google",
		"socket_addrs": "[2001:4860:4860::8888]:443",
		"udp_socket_addrs": "[::1]:53",
		"fragmenting": {
			"enable": true,
			"method": "single"
		}
	},
	"quic":{
		"congestion_controller": "bbr",
		"keep_alive_interval": 5,
		"datagram_receive_buffer_size": 16777216,
		"datagram_send_buffer_size": 8388608
	},
	"connections": 3
}

Then, run DnsSafeguard.exe and wait until you get the H2 Connection Established message. Finally, set up your Windows DNS IP to <IP_ADDRESS>.


Please wrap the dartfmt command from flutter command

In order to reduce occasions where a user runs the wrong version of a utility, I think we can (and should) wrap utilities provided by the Dart SDK with our own flutter command.
For example, I would like our users to try formatting. The instructions to ensure they are using the right version of the formatter are fairly complicated, complete with a bunch of "check this path" and "check this version".
Instead, I would like to say, "Run flutter format foo.dart" and have the flutter command use dartfmt that we bundle.
(we might want to do this for pub, too, but that's probably a different issue)

cc @danrubel something you might be interested in helping with?
It's possible to work around this, but it requires digging into the bin/cache/blah/blah directory of your flutter clone. We've turned on formatting checks on the website, which means our friendly tech writers are now forced to format the samples. So, if we can make it as easy as flutter format ... that would be a win.
Thanks!

Happy to tackle this next.


incorrect currency exchange when minorDigits is 0

Hi, it seems that currency exchange is incorrect when currency's minorDigits is 0.
Example 1, TWD to USD:
Currency twd = Currency.create('TWD', 0, symbol: 'NT\$');
Currency usd = Currency.create('USD', 2);

Money twdM = Money.fromInt(1000, twd);
print(twdM);    // NT$1000.00

Money twdToUsdRate = Money.fromInt(3, usd);    // 1 TWD = 0.035 USD
print(twdToUsdRate);    // $0.03

Money usdM = twdM.exchangeTo(twdToUsdRate);
print(usdM);    // $0.30, but it should be $30

Example 2, TWD to JPY:
Currency jpy = Currency.create('JPY', 0, symbol: '¥');
Currency twd = Currency.create('TWD', 0, symbol: 'NT\$');

Money twdM = Money.fromInt(1000, twd);
print(twdM);    // NT$1000.00

Money twdToJpyRate = Money.fromInt(3, jpy);
print(twdToJpyRate);    // ¥3.00, 1 TWD = 3.68 JPY

Money jpyM = twdM.exchangeTo(twdToJpyRate);
print(jpyM);    // ¥30.00, but it should be ¥3000

There's another question: If we need to set more precise exchange rate, such as 1 TWD to 0.035582 USD, how could we set this rate through Money?
Thank you!

I think the easiest way is to create your own version of the USD currency
with the required no of minor digits.
On Mon, 28 Dec 2020, 2:44 pm cjwind<EMAIL_ADDRESS>wrote:

Hi, it seems that currency exchange is incorrect when currency's
minorDigits is 0.
Example 1, TWD to USD:
Currency twd = Currency.create('TWD', 0, symbol: 'NT$');
Currency usd = Currency.create('USD', 2);
Money twdM = Money.fromInt(1000, twd);
print(twdM);    // NT$1000.00
Money twdToUsdRate = Money.fromInt(3, usd);    // 1 TWD = 0.035 USD
print(twdToUsdRate);    // $0.03
Money usdM = twdM.exchangeTo(twdToUsdRate);
print(usdM);    // $0.30, but it should be $30
Example 2, TWD to JPY:
Currency jpy = Currency.create('JPY', 0, symbol: '¥');
Currency twd = Currency.create('TWD', 0, symbol: 'NT$');
Money twdM = Money.fromInt(1000, twd);
print(twdM);    // NT$1000.00
Money twdToJpyRate = Money.fromInt(3, jpy);
print(twdToJpyRate);    // ¥3.00, 1 TWD = 3.68 JPY
Money jpyM = twdM.exchangeTo(twdToJpyRate);
print(jpyM);    // ¥30.00, but it should be ¥3000
If we need to set more precise exchange rate, such as 1 TWD to 0.035582
USD, how could we set this rate through Money?
Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/noojee/money.dart/issues/25, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG32OF766IZYGBW3L6HQQLSW75LLANCNFSM4VLPHRIQ
.

Using my version currency to be precise exchange rate works. Thanks!
I think the exchange issue may caused by ~/ BigInt.from(100) in exchangeTo().
It seems to assume minorDigit of source currency is 2.

I will check but I think there is a fix for that in the 2.0 version
On Mon, 28 Dec 2020, 4:06 pm cjwind<EMAIL_ADDRESS>wrote:

Using my version currency to be precise exchange rate works. Thanks!
I think the exchange issue may caused by ~/ BigInt.from(100) in
exchangeTo().
It seems to assume minorDigit of source currency is 2.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/noojee/money.dart/issues/25#issuecomment-751576447,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG32OELFLHKXVMEC2AAQG3SXAG6RANCNFSM4VLPHRIQ
.

Closed. exchangeTo fixed in  2.0.1-nullsafety.7

Closed. exchangeTo fixed in  2.0.1-nullsafety.7


pex not in requirements.txt

It is installed as the latest version due to it being a dependency for some component and some paths don't match.
version -0.8.1 works ish need to find the right version used in the past.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29771699-pex-not-in-requirements-txt?utm_campaign=plugin&utm_content=tracker%2F7081451&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F7081451&utm_medium=issues&utm_source=github).

Closing this in favour of #215


Remove table javascript

We don't use any of the javascript that the table organisms require.. this shouldn't be so! This PR removes the table JS and associated wagtail handsontable code (specifically around sorting).
Will have a companion PR in the design-system

How is the Wagtail piece tested?

Open a wagtail page with a table, note that there is no "sortable" option nor any select elements for selecting which header is sortable


Peer to peer code review 14/04/2023

All issues are welcome here

I would recommend you use more responsive measurements such as %, rem, and em as opposed to px, as they scale well with the device width.
Otherwise, the project is fantastic.

Noted Thank you.

Hello @ShaliniNayan,
Congratulations on an outstanding job👏🎉🎉 on creating the popup window using JS.

Keep improving your design layout to match with figma design especially on desktop version specifically on buttons.
Keep growing and Happy coding💪💪


Feature request for React Hooks: Handle Spaces initialization in SpacesProvider

When the <SpacesProvider> React component is used, most of the time, the spaces object needs to be created first.
From the documentation:
const ably = new Realtime.Promise({ key: "VS4Rww.ijkxYg:*****", clientId: 'clemons' });
const spaces = new Spaces(ably);

root.render(
  <SpacesProvider client={spaces}>
    <SpaceProvider name="my-space">
      <App />
    </SpaceProvider>
  </SpacesProvider>
)

It would be nice if, alternatively to the spaces object, the key and the clientId could be passed to the SpacesProvider and the SpacesProvider cares about initializing Ably and Spaces:
  <SpacesProvider key="VS4Rww.ijkxYg:*****" clientId="clemons">
    <SpaceProvider name="my-space">
      <App />
    </SpaceProvider>
  </SpacesProvider>

Or alternatively have an object, which is passed to Realtime.Promise().
This would save some boilerplate code and also would make sure that implementers don't have to remember to put the Spaces initialization into a useMemo()/ useEffect() hook ;)

hey @mms-uret thanks for the suggestion. Did you run into issues with:
const ably = new Realtime.Promise({ key: "VS4Rww.ijkxYg:*****", clientId: 'clemons' });
const spaces = new Spaces(ably);

being called too often? I'll forward your proposal to the product team. An alternative way to share the client is also using the AblyProvider https://ably.com/docs/getting-started/react#ably-provider, did you try that?

Hey @dpiatek ! Yes, we actually raised a support ticket with Ably because we couldn't figure out our own mistake. The solution was pretty simple:
-  const ably = new Realtime.Promise({ key: ablyKey, clientId: user.email });
-  const spaces = new Spaces(ably);
+  const spaces = useMemo(() => {
+    const ably = new Realtime.Promise({ key: ablyKey, clientId: user.email });
+    return new Spaces(ably);
+  }, [ablyKey, user.email]);

Ah, I didn't know about <AblyProvider>. Then maybe it just needs a way to better integrate AblyProvider and SpacesProvider:
<AblyProvider>
  <SpacesProvider>
    <SpaceProvider>
      <App/>
    </SpaceProvider>
  </SpacesProvider>
</AblyProvider>

There is still something needed to initialize the Spaces Variable, I think....
Or maybe integrate AblyProvider into SpacesProvider since Spaces cannot be used without Ably?

@mms-uret you can see how we use the providers in our examples repo https://github.com/ably-labs/realtime-examples/blob/main/examples/vite-component-locking/src/index.tsx. It's useful however to get your feedback here.
The reason the providers are separated is to ensure compatibility with existing apps which already initialise client and future Ably libraries that could share the connection/client. There might be a case, however, as you point out, to just combine that into one component.


Migrate packages to Nuget and Docker Hub

GitHub packages doesn't provide public packages (acknowledged by the product team, but there is no ETA). Migrate to:

Nuget.org for Perper Functions
Docker Hub for Perper Fabric

Update the documentation when done.

Partially completed:

Adjust GitHub Action to submit nuget both to GitHub packages and Nuget.org
Add version to Fabric image in Docker Hub

NuGet deployed in GitHub packages is marked as deprecated and the users are redirected to use nuget.org.


Launch UI locally

Add instructions on how to start locally in the README.md of your UI directory and point to the file when this done @alxschlz98  ?


Images without geolocation

The vast majority of recently created Observations (one year prior to 2024-08-18) that have images also lack lat/lng.
29236 Obss created in the last year
29002 of those have images
21769 lack lat/lng
irb(main):011> Observation.where(Observation[:created_at] > 1.year.ago).count
=> 29236
irb(main):014> Observation.where(Observation[:created_at] > 1.year.ago).where.not(Observation[:thumb_image_id] == nil).count
=> 29002
irb(main):015> Observation.where(Observation[:created_at] > 1.year.ago).where.not(Observation[:thumb_image_id] == nil).where(lat: nil).count
=> 21769

My current guess re no image geoloc:Most (almost all?) were exported from the user's camera or photo app to the user's computer, edited on the computer, then imported to MO.
But they were exported without location data.
What to do? There's nothing we can do directly.

Maybe warn users when there's no location data; suggest that if they edit photos on their computer, be sure that they exported them to the computer with location info.

Maybe a news article on the website.

There are some prolific users who typically omit geoloc. See below (user id's redacted). Maybe contact them directly.

irb(main):002> Observation.where(Observation[:created_at] > 1.year.ago).where.not(Observation[:thumb_image_id] == nil).where(lat: nil).where(user: *****9).count
=> 4906
irb(main):003> Observation.where(Observation[:created_at] > 1.year.ago).where.not(Observation[:thumb_image_id] == nil).where(lat: nil).where(user: *****8).count
=> 4837
irb(main):004> Observation.where(Observation[:created_at] > 1.year.ago).where.not(Observation[:thumb_image_id] == nil).where(lat: nil).where(user: *****2).count
=> 561

I like the idea of contacting the big users directly.
Also - it seems your query is for the last year, but the automatic copying of image geolocation is only a few months old, right?

Good question. I don't remember how that worked.
I looked at thumbnails of recent Observations by the top 3 users (Evica, Huafang, AK) and found that the EXIF headers lacked GPS data.  My guess is that cropped the photos, exported them, and uploaded them.


Client doesn't close/fail automatically when try to send invalid UTF-8 text message unfragmented.

I tried run this client against Autobahn test suite, but it seems failing on one test case. The test detail is
as following:
Case 6.3.1
Up
Case Description

Send invalid UTF-8 text message unfragmented.

MESSAGE:
cebae1bdb9cf83cebcceb5eda080656469746564

Case Expectation

The connection is failed immediately, since the payload is not valid UTF-8.

However, the result I'm getting is, it will hang/block after calling sendText instead of closing. I have not looked into detail of the code implementation. Any insight?

@zxm5010 Do you mean you sent an invalid UTF-8 text message using setText(String) method? How did you create a String instance that holds an invalid UTF-8 sequence?


Added force mode

Used for the engine to make recieved moves without setting side to move.
Also used for cutechess-cli.

Codecov Report

Merging #36 into master will decrease coverage by -0.48%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
- Coverage    90.8%   90.32%   -0.48%
==========================================
  Files           3        3
  Lines         587      589       +2
==========================================
- Hits          533      532       -1
- Misses         48       50       +2
- Partials        6        7       +1

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 acf148d...ac31d52. Read the comment docs.

I think we can ignore @codecov-io here. It's interface code.

Indeed. Merging now.


How best to setup longer timeouts for hubot in development during debugging?

I want to be able to better debug hubot scripts/apps using hubot, but it seems that it times out in development too quickly.  I noticed that it's using connect-timeout middleware and connect middleware but a cursory glance through some code and documentation didn't immediately suggest how I might increase timeouts on hubot itself.
Apologies in advance if this is not the best location for this type of question.

I'm not seeing anywhere we are using the connect timeout middleware, unless some other dependency is pulling it in. Here is what does get setup: https://github.com/github/hubot/blob/7899375f6012b7d3242efa3a9d9847a69528a898/src/robot.coffee#L409-L455
There's not a good way that can think of increase this, but I'm open to ideas.
cc https://github.com/github/hubot/issues/648 for some other conversations around debugging in general in case there's anything of note.


Error on installation

Installing on ubuntu 16.04, docker-compose version 1.8.0.
Followed the guide (https://blog.ambar.cloud/ambar-installation-step-by-step-guide-2/), but after some downloading I get this error:

ERROR: Version in "/home/ddoyle/Ambar/docker-compose.yml" is unsupported. You might be seeing this error because you're using the wrong Compose file version. Either specify a version of "2" (or "2.0") and place your service definitions under the services key, or omit the version key and place your service definitions at the root of the file to use version 1.
For more on the Compose file format versions, see https://docs.docker.com/compose/compose-file/
Traceback (most recent call last):
File "./ambar.py", line 283, in
install(configuration)
File "./ambar.py", line 202, in install
pullImages(configuration)
File "./ambar.py", line 134, in pullImages
runShellCommandStrict("docker-compose -f {0}/docker-compose.yml pull".format(PATH))
File "./ambar.py", line 64, in runShellCommandStrict
subprocess.check_call(command, shell = True)
File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'docker-compose -f /home/me/Ambar/docker-compose.yml pull' returned non-zero exit status 1

Same issue on Ubuntu 17.10
vagrant@vagrant:~$ uname -a
Linux vagrant 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

vagrant@vagrant:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 17.10
Release:	17.10
Codename:	artful

vagrant@vagrant:~$ docker -v
Docker version 17.09.1-ce, build 19e2cf6

vagrant@vagrant:~$ docker-compose -v
docker-compose version 1.8.0, build unknown

@mrdan @groundwater please update your docker to 17.03.0-ce and docker-compose to 1.11.2


specify duckdb does not support python2 in the document

When I run the following example in the website, I got the the segmentation fault
import duckdb
cursor = duckdb.connect(':memory:').cursor()
print(cursor.execute('SELECT 42').fetchall())

[1]    46090 segmentation fault  ipython

this is only in python2.

#188

I have added a clarification to the website


Add "Assignee" to PR Context variables

Is your feature request related to a problem? Please describe.
Currently context variables under PR does not have assignee option.
This is a common piece in our development flow and would like to have some automation on it.
Describe the solution you'd like
Adding that var, probably an easy addition.
Additional context

Thanks for the suggestion @akotek! I think this could have some benefit, but we'd like to understand your situation a little better. Can you describe the use case you're trying to accomplish? That would help us determine the best plan to implement something like this.

I think it's already added and this issue could be closed :)
https://docs.gitstream.cm/context-variables/#pr

Thanks, @azmelanar, for noticing that! I'm closing this issue.
I've added a request for add-assignees actions :)


Obsolete folder structure?

As I understand it, the current folder structure in this repo is obsolete. The Android Studio style folder structure is app/package name/java/. So why does this repo start with src?
Do you not use Android Studio?

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Add flat classification to exports

ColDP and DwC exports are only using the parent-child relation, i.e. via dwc:parentNameUsageID or col:parentID, to setup the classification hierarchy.
For many users it is more readable and convenient to have a flat classification of names at hand for every record.
Add dwc:kingdom-dwc:subgenus and coldp:kingdom-coldp:subgenus terms/columns to exports - consider to make that optional.

I wonder if there is any progress on this issue?
Flat classification is easily human-readable and convenient. I have to get it myself on the taxonomic groups of interest using the igraph library — making a list of reachable nodes from root using depth-first search and then list all simple paths from the source node to another node — manipulations, long and not convenient.

no progress I am afraid as its the same difficulty here and we still have other priorities before we can tackle this one.

Hi there,
at the Danish National Species Portal Arter.dk, users record species occurrences and the dataset is published in GBIF (https://www.gbif.org/dataset/963a6b96-4d22-4428-86e4-afee52cf4a8e). Also, Arter.dk incorporate GBIF occurrences from Denmark by synchronisation.
The taxonomic backbone of Arter.dk is updated manually, But we are also in great need of easily being able to imported selected checklists from GBIF. For this, our system need a flat classification file.
So the Danish GBIF-node were wondering if there might be some good news on progress on this ticket? ;-)

I am afraid no. But I would prioritize this issue once we have reached our milestone to assemble a COL replacement for the GBIF Backbone which we should reach soon.
Internally this heavily depends on another issue to store flat classifications, which unfortunately is some major work. Doing it dynamically is far too slow.


How to make it "non-universal"

What's the best/simplest way to make the demo non-universal (i.e. without server side rendering)? Thanks.

Yep. Set __DISABLE_SSR__ in babel.server.js.
Dupes #20


sampleOutput should be JSON, not Result=

the sampleOutput metadata in install.sh should match the structure of sampleInput, i.e. be a JSON object

observe the poorly formatted sampleOutput

Solved the Sample output JSON issue.


Multiple Cropper Upload same time

Hi,
I have a problem with multiple cropper in same page.
I have variable number of images and I set a cropper for each them , So I want to upload all cropped images in same time but this code does not work for me :
 $images.each(function(ix, ele) {
 var name = $(this).closest('.row').find('[data-role="inputImage"]').prop('name');
  $(this).cropper('getCroppedCanvas').toBlob(function (blob) {
   formdata.append(name, blob);
});
});
var xhr = new XMLHttpRequest();
xhr.open('POST', '@Url.Action("CreateOrUpdate", "Content", new {area = "Content"})');
 xhr.send(formdata);
But not any item pushing to formdata, and formdata is still empty.
I think this is related to async nature of function, How I can use this approach to upload multiple file in same time ?

The cropper initializing is an asynchronous process, you should call the getCroppedCanvas method in the ready hook function.


[FEATURE]  Add isSuccess, isLoading etc to useAction return object

Are you using the latest version of this library?

[X] I verified that the issue exists in the latest next-safe-action release

Is there an existing issue for this?

[X] I have searched the existing issues and found nothing that matches

Suggest an idea
While status already exists, I find myself needing to creating the same additional "boiler-plate" code around the status string value every time I use useAction; specifically creating boolean variables such as isLoading for button state.
While not a high priority, it would be nice if the response object was a more similar to projects like tanstack/react-query that include both the status string and boolean variables like:

isLoading
isSuccess
isError

I imagine any accepted change would need to be applied to useOptimisticAction too.
Additional context
No response

FYI - I'd be happy to raise a PR if there is an appetite for this.

Hi @John-Dennehy, next-safe-action v3 actually returned an object with hasExecuted, isExecuting, hasSucceeded and hasErrored properties, this changed in v4, you can read about it in the v3 to v4 migration guide on the website.
This specific change has been already discussed in this issue, and in this comment I explained why I made it and a possible solution to avoid repeating code, defining simple util functions for the scope.
Please let me know if there's anything else I can help you with, thank you.

Sorry for missing that.  That is a shame really.

No worries! By the way, we could export those utility functions from the library itself, but I'm not sure if this is the right thing to do, not everybody will use them, and defining them in one place is quite simple already. What do you think?

Action status utility functions implemented in 6.1.0 release. Relevant documentation can be found here.


[FIX] Add reports config files to setup.

I was getting the error below when trying to use reports, which I'm guessing is because the config file for reports isn't packaged with the rest of the code. I tried to fix it by adding the config files to setup.py.
The error:
/home/data/nbc/data-analysis/env/lib/python2.7/site-packages/bids/reports/report.pyc in __init__(self, layout, config)
     39
     40         if isinstance(config, str):
---> 41             with open(config) as fobj:
     42                 config = json.load(fobj)
     43

IOError: [Errno 2] No such file or directory: '/home/data/nbc/data-analysis/env/lib/python2.7/site-packages/bids/reports/config/converters.json'

LGTM. Have you tested pip install -e . to make sure it now works?

I did and it does, although I wasn't sure pip install with a local package would cause the same problem since I failed to try it on the old version.

Although I could be wrong, here's my understanding: If you use -e, then any files in the current directory will be available, so it would be a bad test. But using pip install . should perform the bundling.
Probably, it would be better to add a test that will exercise this code on Travis/AppVeyor, which should be making clean installations.

Not sure what you mean about adding tests, but I can drop the -e in the config files for Travis and Appveyor so they fail in the future when there are omissions like this one.

Yes, that's a good idea. To verify that we are actually exercising this code, we should make sure that it fails before your change.
Can you do the following?
git reset --hard upstream/master
# Make your changes to Travis/Appveyor configs
git add .travis.yml appveyor.yml
git commit -m 'CI: Install pybids in non-editable mod'
git push -f
# Wait for tests to finish
git cherry-pick b3fdadf
git push

This will trigger the tests twice, and hopefully will fail on the first and pass on the second.

Hmm. That actually prevented tests from being run. Doing the same thing locally also fails, so I guess testing is only something that can be done in editable mode. (Your b3fdadf commit is still floating around. You can git reset --hard b3fdadf to get back to where you were.)
Not sure how to verify that we install all required files in CI. @tyarkoni ideas?

It failed, but it doesn't look like it was because it couldn't find the config file specifically. It looks to me like it's failing because it couldn't find the actual tests...

I think adding the files to package_data in setup.py should be sufficient. Can you add -e back in? I'm guessing that will fix it.

Alternatively, you could try dropping the --pyargs flag in the py.test invocation; I suspect that may be what prevents the tests from running when installed normally. If not that, fiddling with the pytest call in some other way will probably do it. I confess that I find the pytest docs fairly opaque and usually solve problems like this by trial and error.

Adding -e will fix it, but it won't help catch errors.
Try adding an empty __init__.py in bids/analysis/tests/, bids/grabbids/tests/ and bids/reports/tests/.
This should help catch the issues in #138, as well.

@effigies I did that and now it can't find tests/data. I can add an init file there, but I think I'll also need to add one to all of the subfolders as well. Nipype solves this by including all of the test data paths in package_data. Maybe that's the solution here?

I figured out what was going on... the package_data paths were all messed up, plus the test data weren't being bundled at all. I have a separate branch going that includes your fix, so I'm going to close this and handle it there. Thanks!


Blogging Website Added

I would love to add my website into first good issue site as my website is eligible for that and blogweb is simple website made of html and css. If any changes required please let me know.
ℹ Repository information
The repository has:

[x] At least three issues with the good first issue label.
[x] At least 10 contributors.
[x] Detailed setup instructions for the project.
[x] CONTRIBUTING.md
[x] Actively maintained.

Hey @Sajiyah-Salat  ! I tried to contribute to this repo as well but I haven't seen any activity in the last few months. I decided to fork it to keep it alive. Please see https://github.com/lucavallin/gfi and feel free to open a pull request there. At this time I am setting up the hosting and cleaning up the code. If you're up for it, I could use some help to convert the app from Nuxt.js & Python to Next.js & Typescript.

Hey @lucavallin Yeah sure, I will open new pr there, also I agree with your point about maintainenace. I noticed the same thing and the website is widely used for beginners. Though I dont know anything about next.js, python etc. I will try my best to help you. Thank you.

Nick found i

Nick turnbill seen "everything"


Update User.js

Why do you think this change is needed? For me it breaks the password change function (after changing the password with your PR, there's the plaintext password instead of the hash).


Make flex npm install-able

We should make flex a globally install-able package via npm install
This involves

convert git submodules into a way they can be configured (like media repositories)
adding all files to the files, dictionaries, dictionaries.lib config variables
offering config variables for various elements, such as port, location..
adding inexor as a bin into the package.json

That way we could use Flex (and thereby Inexor) in a really simple matter in the future
npm install @inexor-game/inexor-flex
inexor-flex # <-- this will start flex and the web server, wohoo

# if you like to have a specific version of flex,
npm install @inexor-game/inexor-flex@VERSION

This will also

deprecate the inexor_unix and inexor.bat

How does that deprecate inexor_unix and inexor.bat? We still need one-click files which are executing the start command for users.

well, in that case you can simply inexor-flex instance start 31415 from the command line..

I have thought about your comment again. Providing a desktop shortcut to inexor-flex instance start 31415 will be much easier / more comfortable for the user than a bash script.

Already done for linux: https://github.com/inexorgame/inexor-core/blob/master/dist/linux/inexor.desktop
Who wants to create an ico file for windows?

whats to do on this one? :)

@a-teammate still depends on #450 which was previously assigned to @aschaeffer
I am working on it, however it will take some more time..

Good morning :-)
What's the state of this issue? Successfully implemented?

Yes. Please test wether it works extensively.


Sweep: create small python htmx server module using cognosis/static/.server/statserv.py for a rudimentary example and starting file. in-scope dirs: /static/js/, /static/templates/, /static/css/, /static/.server/ Scope includes r/w/x in the /static/ dir so follow-through with your edits and additions and even create tests in the /cognosis/tests/ dir if you'd like. The server module should be able to serve the markdown editor (htmx is optional) and it's button (button is not optional, implement it even if it doesn't do anything so it can be added to later) using the standard libs.Sweep:

Details
No response

Checklist

[X] Refactor static/.server/statserv.py ✗
[X] Modify static/.server/statserv.py ✓ https://github.com/MOONLAPSED/cognosis/commit/c37e7e283d38380a7e5de78b859c3425cda093a1
[X] Test tests/test_UFS.py ✓ https://github.com/MOONLAPSED/cognosis/commit/d8085e9376305908e6bc32889942b8960640cc34
[X] Ran sandbox for tests/test_UFS.py. ✓ https://github.com/MOONLAPSED/cognosis/commit/8ae71e68c55cf193f66660f3f1bb0be5e0713162

please try again. I'm opening a new issue.


A problem about cisTopic

Hello，
When I use this pipeline, I met a problem, the result of I click cisTopic entering the pipeline code of Cicero.

Thanks for the feedback. It's fixed now.


Use Composer's CA bundle library

Composer has recently extracted their CA bundle logic into a separate library (composer/ca-bundle). Using it fixes #8 as it falls back to a shipped CA file; the point about maintenance still remains, but I imagine if any file is going to be maintained it'd be this one.

@padraic This would solve our problems with Puli (and I know other projects having troubles too). Do you think it could be merged ? I can work on it to fix tests if needed.

Looks like a nice one, but I would prefer to let someone more familiar on this topic :)
/cc @humbug/core

Thanks for the PR @thewilkybarkid, sorry for the delay :)


Fallback to GetFullPathNameW for Windows _canonicalizedPath

If a file is not found, rather than failing, we should use
GetFullPathNameW which doesn't resolve symlinks, but will work on paths
that don't exist.

@swift-ci please test

Updated for feedback :) It does seem nicer to use szPath.count.
@swift-ci please test

@swift-ci please test and merge

@swift-ci please test and merge


[BUG] My Bloxxtrap will not save

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.8.0
What problem did you encounter?
My bloxxtrap does not save, every time i click the save button it gives me the notification that it was saved but it does not go away, and once i launch Roblox none of the changes i applied had been saved so I'm confused if this is just me?
Here is video proof as well.
https://github.com/user-attachments/assets/2edbe982-5d9f-4bbb-aa42-eb568c1f5690
Bloxstrap Log
N/A

Your screen recording quite clearly shows the notification going away. Can you give examples of what options you're trying to change that aren't applying?


Rename the query argument labels and attempt to improve the documentation.

The suggestion here is renaming query to skippingRepeat and skippingNil which are more explicit about the behaviour than the current form.

Great improvements! 👏
I was about to open a PR to use filterMap's inside the init's, but then I saw this PR 😆
One suggestion though, shouldn't the skippingRepeated variant be skippingRepeatedAndNil, since it also skips nil's?

Any outcome out of this PR?

@sergdort addressed your comments.

@p4checo

One suggestion though, shouldn't the skippingRepeated variant be skippingRepeatedAndNil (or skippingNilAndRepeated), since it also skips nil's?

nil is not being skipped over. While it doesn't trigger any new effect on its own, it cancels the outstanding ones.

@andersio

nil is not being skipped over. While it doesn't trigger any new effect on its own, it cancels the outstanding ones.

When I made that comment, the skippingRepeated variant used a filterMap, hence my comment on the nil. It no longer applies on your most recent changes though 😉
For completeness, the old version was:
    public init<Control: Equatable, Effect: SignalProducerConvertible>(
        skippingRepeated transform: @escaping (State) -> Control?,
        effects: @escaping (Control) -> Effect
    ) where Effect.Value == Event, Effect.Error == NoError {
        self.init(deriving: { $0.filterMap(transform).skipRepeats(==) },
                  effects: effects)
    }

Whereas the new one is:
    public init<Control: Equatable, Effect: SignalProducerConvertible>(
        skippingRepeated transform: @escaping (State) -> Control?,
        effects: @escaping (Control) -> Effect
    ) where Effect.Value == Event, Effect.Error == NoError {
        self.init(deriving: { $0.map(transform) },
                  effects: { $0.map(effects)?.producer ?? .empty })
    }

        expected to eventually equal <[initial, initial_a, initial_a_b, initial_a_b_a, initial_a_b_a_b]>, got <[initial, initial_a, initial_a_a, initial_a_a_a, initial_a_a_a_a]>

The same test is failing on develop with Xcode 10 and ReactiveSwift 3.1. It is likely due to the RAS 3.1 constant producer interruption fix, which makes RAF cancel outstanding scheduled work items (effects and events) as expected. 🤔

How are we planning to fix this?

@diegopetrucci The commit had already been pushed before the comment.


docs: replace type mixed in the remaining cache class.

Description
See #6310
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Thank you @ping-yee


Cannot publish to S3

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
I cannot publish to an S3 target. Publish failing with error: Could not find a publish target with the name: true
I've tried the publish command with and without an explicit --target flag and with various formatting. Leaving off the flag defaults to github which I don't have setup or defined in the config JSON. I get the same error every time.

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Checking your system +0ms
  electron-forge:lifecycle Process Succeeded: Checking your system +47ms
  electron-forge:runtime-config setting key: verbose to value: false +9ms
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Resolving Forge Config +0ms
  electron-forge:project-resolver searching for project in: /Users/noah/test-project +3ms
  electron-forge:project-resolver electron-forge compatible package.json found in /Users/noah/test-project/package.json +10ms
  electron-forge:lifecycle Process Succeeded: Resolving Forge Config +9ms
We need to package your application before we can make it
  electron-forge:lifecycle Process Started: Preparing to Package Application for arch: x64 +2ms
  electron-forge:project-resolver searching for project in: /Users/noah/test-project +0ms
  electron-forge:project-resolver electron-forge compatible package.json found in /Users/noah/test-project/package.json +1ms
  electron-forge:packager packaging with options { asar: false,
  overwrite: true,
  afterCopy: [ [Function], [Function], [Function] ],
  afterExtract: [],
  dir: '/Users/noah/test-project',
  arch: 'x64',
  platform: 'darwin',
  out: '/Users/noah/test-project/out',
  electronVersion: '1.4.15',
  quiet: true } +4ms
  electron-forge:lifecycle Process Succeeded: Preparing to Package Application for arch: x64 +17s
  electron-forge:lifecycle Process Started: Compiling Application +3ms
  electron-forge:lifecycle Process Succeeded: Compiling Application +1s
  electron-forge:lifecycle Process Started: Preparing native dependencies +2ms
  electron-forge:lifecycle Process Succeeded: Preparing native dependencies +127ms
  electron-forge:lifecycle Process Started: Packaging Application +1ms
  electron-forge:lifecycle Process Succeeded: Packaging Application +10s
Making for the following targets:
  electron-forge:lifecycle Process Started: Making for target: zip - On platform: darwin - For arch: x64 +5ms
  electron-forge:require-search searching [ '../makers/darwin/zip.js',
  '../makers/generic/zip.js',
  'electron-forge-maker-zip',
  '/usr/local/lib/node_modules/electron-forge/dist/makers/darwin/zip.js',
  '/usr/local/lib/node_modules/electron-forge/dist/makers/generic/zip.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/electron-forge-maker-zip',
  '/usr/local/lib/node_modules/electron-forge/dist/api/makers/darwin/zip.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/makers/generic/zip.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/node_modules/electron-forge-maker-zip' ] relative to /usr/local/lib/node_modules/electron-forge/dist/api +1ms
  electron-forge:require-search testing ../makers/darwin/zip.js +3ms
  electron-forge:require-search testing ../makers/generic/zip.js +0ms
  electron-forge:lifecycle Process Succeeded: Making for target: zip - On platform: darwin - For arch: x64 +12s
  electron-forge:project-resolver searching for project in: /Users/noah/test-project +2ms
  electron-forge:project-resolver electron-forge compatible package.json found in /Users/noah/test-project/package.json +1ms
  electron-forge:lifecycle Process Started: Resolving publish target: true +8ms
  electron-forge:require-search searching [ '../publishers/true.js',
  'electron-forge-publisher-true',
  '/usr/local/lib/node_modules/electron-forge/dist/publishers/true.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/electron-forge-publisher-true',
  '/usr/local/lib/node_modules/electron-forge/dist/api/publishers/true.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/node_modules/electron-forge-publisher-true' ] relative to /usr/local/lib/node_modules/electron-forge/dist/api +1ms
  electron-forge:require-search testing ../publishers/true.js +0ms
  electron-forge:require-search testing electron-forge-publisher-true +1ms
  electron-forge:require-search testing /usr/local/lib/node_modules/electron-forge/dist/publishers/true.js +0ms
  electron-forge:require-search testing /usr/local/lib/node_modules/electron-forge/dist/api/electron-forge-publisher-true +0ms
  electron-forge:require-search testing /usr/local/lib/node_modules/electron-forge/dist/api/publishers/true.js +0ms
  electron-forge:require-search testing /usr/local/lib/node_modules/electron-forge/dist/api/node_modules/electron-forge-publisher-true +0ms
  electron-forge:require-search failed to find a module in [ '../publishers/true.js',
  'electron-forge-publisher-true',
  '/usr/local/lib/node_modules/electron-forge/dist/publishers/true.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/electron-forge-publisher-true',
  '/usr/local/lib/node_modules/electron-forge/dist/api/publishers/true.js',
  '/usr/local/lib/node_modules/electron-forge/dist/api/node_modules/electron-forge-publisher-true' ] +1ms
  electron-forge:lifecycle Process Failed: Resolving publish target: true +3ms

Electron forge was terminated:
Could not find a publish target with the name: true

What command line arguments are you passing?
electron-forge publish --target=s3
electron-forge publish --target s3
electron-forge publish --target="s3"

What does your config.forge data in package.json look like?
{
      "make_targets": {
        "win32": [
          "squirrel"
        ],
        "darwin": [
          "zip"
        ],
        "linux": [
          "deb",
          "rpm"
        ]
      },
      "electronPackagerConfig": {},
      "electronWinstallerConfig": {
        "name": "test_project"
      },
      "electronInstallerDebian": {},
      "electronInstallerRedhat": {},
      "windowsStoreConfig": {
        "packageName": "",
        "name": "testproject"
      },
      "publish_targets": {
        "s3": {
          "accessKey": "AKIAIZQRPHMZZYTGK6NQ",
          "bucket": "mq-apps",
          "folder": "Releases",
          "public": true
        }
      },
      "s3": {
        "accessKey": "AKIAIZQRPHMZZYTGK6NQ",
        "bucket": "mq-apps",
        "folder": "Releases",
        "public": true
      }
    }

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.
$ electron-forge init
remove github_repository object and add in to forge config:
"publish_targets": {
"s3": {
"accessKey": "XXXX",
"bucket": "XXXX",
"folder": "Releases",
"public": true
}
},
"s3": {
"accessKey": "XXXX",
"bucket": "XXXX",
"folder": "Releases",
"public": true
}
$ electron-forge publish --target=s3

@noahott You're config object is a little bit off I think
{
  "make_targets": {
    "win32": [
      "squirrel"
    ],
    "darwin": [
      "zip"
    ],
    "linux": [
      "deb",
      "rpm"
    ]
  },
  "electronPackagerConfig": {},
  "electronWinstallerConfig": {
    "name": "test_project"
  },
  "electronInstallerDebian": {},
  "electronInstallerRedhat": {},
  "windowsStoreConfig": {
    "packageName": "",
    "name": "testproject"
  },
  "publish_targets": {
    "linux": ["s3"],
    "darwin" ["s3"],
    "win32": ["s3"],
  },
  "s3": {
    "accessKey": "AKIAIZQRPHMZZYTGK6NQ",
    "bucket": "mq-apps",
    "folder": "Releases",
    "public": true
  }
}

Then simply run electron-forge publish

I've updated the config as you suggested, but I am still getting the same errors. Running "electron-forge publish" tries to publish to github and fails with an error that the owner and name properties are not defined. Running "electron-forge publish --target=s3" results in the same error "Could not find a publish target with the name: true"

@noahott What is your electron forge version?
electron-forge --version

@MarshallOfSound it is 2.8.0. I installed through npm

Oh, this hasn't been merged yet
https://github.com/electron-userland/electron-forge/commit/8572cad63eab91a5d090970a0133c4800723b5fd

@noahott Just published 2.8.1, can you try that out please 👍

I updated to 2.8.1, but now i'm running into a different error during the "preparing native dependencies" stage:
An unhandled error has occurred inside Forge: Could locate node-gyp Error: Could locate node-gyp     at _callee6$ (/usr/local/lib/node_modules/electron-forge/node_modules/electron-rebuild/lib/rebuild.js:164:19)     at tryCatch (/usr/local/lib/node_modules/electron-forge/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:63:40)     at GeneratorFunctionPrototype.invoke [as _invoke] (/usr/local/lib/node_modules/electron-forge/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:337:22)     at GeneratorFunctionPrototype.prototype.(anonymous function) [as next] (/usr/local/lib/node_modules/electron-forge/node_modules/electron-rebuild/node_modules/regenerator-runtime/runtime.js:96:21)     at GeneratorFunctionPrototype.tryCatcher (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/util.js:16:23)     at PromiseSpawn._promiseFulfilled (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/generators.js:97:49)     at Promise._settlePromise (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:572:26)     at Promise._settlePromise0 (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:612:10)     at Promise._settlePromises (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/promise.js:691:18)     at Async._drainQueue (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:133:16)     at Async._drainQueues (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:143:10)     at Immediate.Async.drainQueues (/usr/local/lib/node_modules/electron-forge/node_modules/bluebird/js/release/async.js:17:14)     at runCallback (timers.js:637:20)     at tryOnImmediate (timers.js:610:5)     at processImmediate [as _immediateCallback] (timers.js:582:5)
not sure if this is related, but I can't test publishing now without getting this.

It's unrelated and a very strange error.

I can't reproduce the node-gyp error on Linux (64-bit) on a project with a native module.

I was able to solve the node-gyp related error by uninstalling electron-forge and reinstalling using npm.
I was able to get publishing setup to S3 with a few caveats. Publishing fails with the folowing error when only the ELECTRON_FORGE_S3_SECRET_ACCESS_KEY environment variable is set:
Electron forge was terminated: In order to publish to s3 you must set the "s3.accessKeyId", "process.env.ELECTRON_FORGE_S3_SECRET_ACCESS_KEY" and "s3.bucket" properties in your forge config. See the docs for more info
Publishing only succeeds when BOTH the "secretAccessKey" and "secret" properties are defined in the forge.s3 config. This is not documented anywhere, and doesn't match the instructions in the error message.

That's strange, because there's no reference to a secret property in the code.

I found it here: https://github.com/electron-userland/electron-forge/blob/master/src/publishers/s3.js#L19

Stupid GitHub search, why didn't it find that??
Looks like a typo :cry:

I noticed that using Electron 6 that uses Node.js v12 has a conflict with<EMAIL_ADDRESS> The S3 publisher has a dependency on "s3" which uses<EMAIL_ADDRESS> The master branch of the "s3" module has a reference to the version of graceful-fs that works, but they have not published the fix to NPM.  Issue: https://github.com/andrewrk/node-s3-client/issues/197

@gitsome The version of node that Electron uses is entirely unrelated to the version of node you have on your system (and run electron-forge with).  They don't need to match in any way

@gitsome The version of node that Electron uses is entirely unrelated to the version of node you have on your system (and run electron-forge with). They don't need to match in any way

Thanks for the response @MarshallOfSound! That's a good point. I could switch versions during publish and avoid the error. I do have nodegit as a dependency in my Electron project though and am trying to build it while on NodeJS 12 in my local system. I'll try to downgrade to NodeJS 10 and see if I can get both nodegit to build succesfully and also avoid the s3 publish issue. Thanks for all your great work!

Electron Forge v6 no longer uses the s3 node module, it uses aws-sdk directly.


Getting "Segmentation fault: 11" on MacOS Catalina

Hello, I've tried using iodine on MacOS Catalina and I'm getting a segfault error:
kbs@touchbar:~/git/iodine$ /usr/local/sbin/iodine -f -P pelado tunnel.peladonerd.com
iodine: Run as root and you'll be happy.
kbs@touchbar:~/git/iodine$ sudo /usr/local/sbin/iodine -f -P pelado tunnel.peladonerd.com
Segmentation fault: 11

The installation steps went well:
kbs@touchbar:~/git/iodine$ make
OS is DARWIN, arch is x86_64
kbs@touchbar:~/git/iodine$ make install
OS is DARWIN, arch is x86_64
mkdir -p /usr/local/sbin
install  bin/iodine /usr/local/sbin/iodine
chmod 755 /usr/local/sbin/iodine
install  bin/iodined /usr/local/sbin/iodined
chmod 755 /usr/local/sbin/iodined
mkdir -p /usr/local/share/man/man8
install  man/iodine.8 /usr/local/share/man/man8/iodine.8
chmod 644 /usr/local/share/man/man8/iodine.8
mkdir -p /usr/local/share/doc/iodine
install  README.md /usr/local/share/doc/iodine/README.md
chmod 644 /usr/local/share/doc/iodine/README.md

Any ideas?

Recompiling with address sanitizer enabled reveals that the segfault happens in the strncmp on line 420:
https://github.com/yarrick/iodine/blob/814a1fd7b0a6cf376f38bfc01056084c301d0873/src/tun.c#L412-L431
Passing -d utun2 as a flag to iodine seems to make it work (very unreliably).

Thanks for the help, so I remember trying that and getting the following error:
$ iodine -f -r -d utun5 <IP_ADDRESS> test.com
Enter password:
iodine: open_utun: connect: Resource busy
iodine: open_tun: /dev/utun5: No such file or directory

After your comment, I gave it another try and I realized I don't have those files: /dev/utun* ... but I do have /dev/tun* ones, so I ran it with tun2 instead and it worked:
$ iodine -f -P pelado -d tun2 tunnel.peladonerd.com
Opened /dev/tun2
Opened IPv4 UDP socket
Sending DNS queries for tunnel.peladonerd.com to <IP_ADDRESS>

Maybe Apple changed the name to tun* from utun*?

I moved the utun check to inside where we know a device name was passed. Does it work now without setting a device name?

Yes it does. Thank you very much for the quick fix!


restructure diretory , seperate headers from src

directory restructure, move headers to include

Please review

Anand, got this pull request. However, we are now on ASF git repo, so will need to apply patch on that.


Head Components Needed on Pages

titles meta tags etc needed

Titles added, but it's not an intuitive process. Needs further work.

Need to develop default social media share image. Perhaps Canva or Adobe Express

defaultSiteImage is now in place in local code. Will push soon.


Backport 2.7: Add output of make, cmake and python3 versions

Backport to 2.7 of #3351

head TLS testing failed due to intermittent test instance failure. Assuming it's OK since the merge TLS testing succeeded and this change is low risk

head TLS testing failed due to intermittent test instance failure. Assuming it's OK since the merge TLS testing succeeded and this change is low risk

Yes. The pr-merge job runs everything the pr-head job does, so if pr-merge succeeds, we don't really care about what pr-head did. The reason we have pr-head is that it's fairly common that pr-merge fails or can't run due to a merge conflict, but running on head still gives useful feedback.


[Feature] Allow users to change the unit of Internet speed from Mb/s to MB/s

Description of the feature
Out of different habits, I feel more comfortable displaying it as MB/s. Mind if adding it as a new environment variable? Thank you!
Additional context
No response

Agree, need MB/s!

I also agree to convert Mb/s to MB/s.

Would be nice, yesi

You can now switch to MB/s by passing DASHDOT_NETWORK_SPEED_AS_BYTES="true" to your dashdot instance.


CI: Do not fail the build if the PR comment fails

Description
This will no longer fail the build if a comment cannot be added to the PR. As the build is a required job and commenting on the PR is a non critical feature. This is motivated by recent github API limits but is a better approach in any case.
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
CI is sufficient

/test ui-unit-tests

I jumped to the wrong conclusion pursuing this PR. The failure to add a comment to a PR will cause ci/prow/stackrox_branding-push-images images to be marked as failed (the images are still pushed) and that is not a required job. (ci/prow/stackrox_branding-images being the required job). But this is still a useful change to diminish noise and confusion.


Brief explanation of input data format

Could you include just a brief explanation of the input data format in your readme? I've dug down into the MotionData class and found that it should represent a pose of the form
[root position, root orientation, joint poses (e.g. rotations)], but I'm still a bit confused what that entails.  I don't understand why they would each be of length 19.
Is there some documentation on this format for a pose.

I've dug a little deeper and I see that the first 3 datapoints per frame are position and the 4 after are rotation.  I imagine the remaining 12 data-points are joint poses, but I'm still unsure what format they take.

Indeed, the mocap data represents the pose of the robot,
root_position, x,y,z in world space
root_orientation, a quaternion x,y,z,w, in world space
then the joint poses (joint angles), since there are 4 legs, each leg has 3 motors (shoulder, hip and knee) you get 12 dofs for the legs, so 19 in total.
Do you have more specific question about above?

Ah thank you, the reference to the DeepMimic docs was what I was needing. Thank you. I threw out a quick PR to add it for others https://github.com/google-research/motion_imitation/pull/5.

Thanks, done.


Add Flow NFT Catalog To The Docs.

Closes: N/A
Description
The NFT Catalog is live, and we want to expose this information to developers on the doc site.  This particular page seems like a good fit - https://developers.flow.com/flow/core-contracts/nft-metadata.
Feel free to propose different verbiage, or a different page altogether.

For contributor use:

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

@prpatel05 Sorry about the delay. This is merged now.


Kill transposes 2

This adds a couple more tweaks to tensordot2 and also, perhaps more controversially, adds an output_edge_ordering argument to contract_between().
The latter allows contract_between() to flip the argument ordering in the call to tensordot() in case this would minimize transposition of the output tensor. For this to be possible, it must know the desired output ordering. This is used in ncon().
Probably I should add some explicit tests for this is tensornetwork_test. Am happy to do that.

perhaps more controversially, adds an output_edge_ordering argument to contract_between().

Doesn't seem controversial at all to me.

Probably I should add some explicit tests for this is tensornetwork_test. Am happy to do that.

Yes, always add tests. :)

Doesn't seem controversial at all to me.

Good :) It irked me a little to add a second way of achieving an output ordering, but I guess it's not like we're adhering to "TOOWTDI"* elsewhere.
Tests are in.
*just found out there's an acronym for this...

Well, the reason it doesn't break TOOWTDI is because you only do it if you have to. It's a necessary optimization.

So, I've been trying to keep the tensordot2 code close to the TF tensordot code so that it can be pushed upstream at some point. I could add typing, but the TF code does not use it. This also affects the assumptions I can make about input arguments. For example, tensordot supports axes being a single Tensor, but TensorNetwork never uses this.
I can certainly still add typing to tensordot2 if you deem it necessary.

Go ahead and add the typing. Removing it when you make an upstream PR should be pretty easy.
If you want to include tf.Tensor as one of the types to axes, I would be ok with that.

Oh no a flaky test.
Why did I use np.random. let me fix that


feat: Multiselect defaultValue Validation Check for ServerSide Filtering(On/Off)

Description
Checks for multiSelect widget Default Value
Fixes #13665
Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Unit test

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=f4d403f

/ok-to-test sha=51dff2c

/ok-to-test sha=714145e

/ok-to-test sha=5178624

/ok-to-test sha=6a97716

Note to QA: Please refer the note while testing.

/ok-to-test sha=133a0fd

Tested and verified.


Update DAWG token coingeckoId

I'm submitting a ...
[ ] bug report
[ ] feature request

Please approve my PR to add the coingeckoId field https://github.com/solana-labs/token-list/pull/5396

the field is coingeckoId
please squash your commits

coingeckoId thats what i typed. check again please

weird, ok yeah thats a false alarm
merged


TensorFlow 2D encoding added

Hey, thanks for the code. I have most of my code in TensorFlow/Keras already so I converted your 2D encoding from torch to TensorFlow. I think other might also find this useful.
Cheers

Hey @IRiViI! Thanks for the contribution!
I agree, i think that others might find this useful as well. Ill make a quick change to this pr as well (mainly cleanups and more changes to the readme), and then I'll merge it.

Cool, let me know when you are ready. I already found a bug in my code (which I just fixed).

Oke cool, I only added a small part to the readme.
Well spotted the import redundancy. I guess that is what you get when copy pasting your code.

Cool, thank you! I'll merge this.

Awesome!
I could probably also do the same for 1D and 3D but I didn't need it though.
There is one small difference in the outcome between the TensorFlow en PyTorch version. the outcome has a difference in the order of e-8 when I tested it. So I think it it due to rounding when the data was in 8 bit format or something. I don't care enough to track down where it happens but let me know if you think this should also be addressed.
Cheers,

Nah, I think thats fine. Actually, I can try myself to see if i can do the 1 and 3d version as a learning experience.
Also, i think that this small rounding error is fine, as it is not so much.


image promoter should set a useragent

What would you like to be added:
Ideally, the image promoter would have a unique useragent so we can identify what requests it's sending to the registry (in particular, to debug why you're getting 429s).
Why is this needed:
See https://github.com/kubernetes-sigs/promo-tools/issues/637#issuecomment-1286180731

/assign


zoxide切换目录报错

Version confirmation

[X] Confirm

Following prerequisites

[X] Confirm

Neovim version
NVIM v0.9.1 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3
Operating system/version
Windows 10
Terminal name/version
Alacritty
$TERM environment variable
No response
Branch info
main (Default/Latest)
Fetch Preferences
HTTPS (use_ssh = false)
How to reproduce the issue
使用zoxide切换目录报错
Expected behavior
正确显示目录
Actual behavior
No response
Additional information

Seems like either u have a very big zoxide database or your computer is too slow to finish the task?

好象是db.zo的问题，删除后没问题了


[4.3.0] Add ICP userstore doc

Purpose
$subject
This will fix https://github.com/wso2/docs-mi/issues/825.

A screen capture of the rendered page is attached below:
setting-up-a-userstore-in-icp.pdf


samples: net: wifi: enable time checking for mbedtls cert files

enable time checking for mbedtls certificate files, return failed if certificate files expired.

Should we enable that for all the boards in this sample, or just for this one board, what people think?

Enable this feature depend on the requirement of vendor and specific application, for NXP Wi-Fi applications, only need enable this one.

Hi @jukkar @krish2718
Could you help approve and merge PR if no other comment?


Fix bug with mixed case packages

Description
Mixed cases in packages can cause them to not show up in the call to get_installed_packages.
An example of a package with this naming is WeasyPrint.

Coverage increased (+0.009%) to 73.697% when pulling 2040e73d60255892a73211dc35b85e4b184cfb4c on mathom:packagecase into c2bc9b0e1dd55d7c67176f4ae7fa380a82235cb5 on Miserlou:master.

Coverage increased (+0.009%) to 73.697% when pulling 73f6fe437b51da8ec046826aa3b1281105ee390a on mathom:packagecase into c2bc9b0e1dd55d7c67176f4ae7fa380a82235cb5 on Miserlou:master.

Coverage increased (+0.009%) to 73.697% when pulling 73f6fe437b51da8ec046826aa3b1281105ee390a on mathom:packagecase into c2bc9b0e1dd55d7c67176f4ae7fa380a82235cb5 on Miserlou:master.


azds.yaml where is the documentation for this file?

I'm trying to figure out how I can attach my pod to persistent storage.
In my solution I have an azds.yaml file and I can hit f5 with dev spaces selected and see my app running.
I am familiar with docker and the DOCKERFILE.
However I am not familiar with azds.yaml or helm (completely new to me) - in fact kubernetes in general is new to me, but I have some docker swarm experience.
I have read this: https://docs.microsoft.com/en-us/azure/aks/azure-files-volume which describes how to spin up a POD manually using kubectl directly, and a yaml file which has the spec for the POD including it's storage options.
However as I rely on hitting F5 in VS to build my container and spin up my POD/s, I need to find the appropriate config file to amend so that I can supply POD storage options.
The azds.yaml file looks like it might be a promising candidate but I can't find any documentation that describes its format / this file. Is there anything you can point me at?
Thanks

The format for this file is described quite well here, but this is not the right place to re-configure the yaml for your workloads, e.g. to add an Azure file volume. You should do that by modifying the Helm chart directly. The azds.yaml file exists to help configure how your code should run for development purposes only, while the Helm chart describes your workload as it is intended to be configured for production.

@stepro thank you. Helm charts are new to me, but I have discovered the charts directory that the client side tooling has created for me. It looks like it's some sort of template system but I cant see any files in there relating to POD storage options. Are you able to point me on a sensible direction for example to extend what has been created by default to include pod storage options?

The place to look is in the templates/deployment.yaml file. In Kubernetes, pods are typically managed by a controller of some type, the most common being a deployment object. In the spec for that object you'll find a template for pods that the deployment object creates and manages. That's where you will want to be putting settings regarding volumes etc.

Thanks that was what I was after, sorry for discussing this across two issues :-).


Update comment to match update version

According to the readme

Widget API releases have the format "Version X, Update Y". Equivalent tags are created in this repository as v.

Thanks for the PR. We're just going to remove the string; see #36


BDS-575 Deprecate itemAlignment parameter in button component

Jira
http://vjira2:8080/browse/BDS-575
Summary
Deprecates itemAlignment property of button component.  Use align instead.
Details
More important than this specific deprecation is that we're defining the workflow for deprecation.  The steps in this PR create the deprecation; after it's merged, I'll create an additional PR against 2.x to remove support for the deprecated parameter.
I've created this page in the wiki to describe the whole process: https://github.com/bolt-design-system/bolt/wiki/Deprecating-component-properties
How to test

Confirm schema shows as invalid if there's any usage of itemAlignment

Check out this branch
Add itemAlignment: "start" to button (anywhere it is removed in this PR)
Run cd apps/pattern-lab and npm run start.  The build should fail due to schema errors

Confirm the deprecated parameter can still be used

Stop pattern lab
In apps/pattern-lab/.boltrc.js, set schemaErrorReporting to console
Run cd apps/pattern-lab and npm run start.  The build should work, deprecated parameters should function as they have in the past, and schema validation errors should be shown in the browser console when viewing pattern lab pages that use the deprecated parameter.

I agree that start and end are preferable to right and left.
This deprecation was first introduced in 74da8ee.  Before that, I believe itemAlignment did accept start and end (hard to say for sure just by looking at that commit though).  @sghoweri, was that an intentional choice?

Cool, thanks guys.  I'll go ahead and deprecate the newer properties then as well 😅

@mikemai2awesome, I've updated the buttons to use "start" and "end" for alignment.  Two important notes:

I did not actually change text-align: left; in the CSS, because there are some rules that apply left and right margins as well which would not work with start and end.  Should we be updating the bolt-margin-right() mixin to be bolt-margin-start() as well?  I think that's beyond the scope of this PR, but an important decision to make for the future.

I discovered that passing in either align or style does nothing to buttons included in contentItems within cards.  That's because the code in card.twig will always force set them to hard coded values (namely, "start" and "text").  This may be intentional (@sghoweri?), and is probably best left as-is anyway since changing it could break things.  In any case, the bigger problem is that our docs show usage examples that are actually wrong, so I fixed that at least.


Two Pointers: Determine if a triplet exists in an array which sums up to a target in C++

Given an array of integers, nums, and an integer value, target,
determine if there are any three integers in nums whose sum equals the target.
Return TRUE if three such integers are found in the array. Otherwise, return FALSE.
Sample Input : 3, 7, 1, 2, 8, 4, 5 Target : 18
Output : True
Sample Input : 0 -1 1 Target : 2
Output : False

I would like to work on this issue.

I would like to work on this issue.

Sure, I've assigned it to you


Implement filter expression and evaluation

close #114

Codecov Report

Merging #117 (7ece805) into main (d81cc2b) will increase coverage by 0.19%.
The diff coverage is 88.54%.

@@            Coverage Diff             @@
##             main     #117      +/-   ##
==========================================
+ Coverage   87.01%   87.21%   +0.19%
==========================================
  Files          84       86       +2
  Lines       14473    16067    +1594
==========================================
+ Hits        12594    14013    +1419
- Misses       1879     2054     +175

Impacted Files
Coverage Δ

xngin-compute/src/error.rs
0.00% <0.00%> (ø)

xngin-storage/src/error.rs
0.00% <ø> (ø)

xngin-storage/src/repr.rs
71.42% <ø> (ø)

xngin-storage/src/slice_ext.rs
89.58% <ø> (ø)

xngin-compute/src/cmp.rs
84.30% <83.52%> (-5.09%)
:arrow_down:

xngin-storage/src/sel.rs
83.63% <83.63%> (ø)

xngin-compute/src/arith.rs
85.56% <84.21%> (-3.15%)
:arrow_down:

xngin-compute/src/eval/plan.rs
87.50% <87.50%> (ø)

xngin-storage/src/bitmap.rs
85.77% <88.35%> (ø)

xngin-compute/src/logic.rs
88.70% <88.70%> (+88.70%)
:arrow_up:

... and 19 more

Continue to review full report at Codecov.

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


Use specific version of volcengine.

The version 1.0.140 came from docker image infiniflow/ragflow:v0.7.0
What problem does this PR solve?
Briefly describe what this PR aims to solve. Include background context that will help reviewers understand the purpose of the PR.
Type of change

[ ] Bug Fix (non-breaking change which fixes an issue)
[ ] New Feature (non-breaking change which adds functionality)
[ ] Documentation Update
[ ] Refactoring
[ ] Performance Improvement
[ ] Other (please describe):

Cannot install -r requirements_dev.txt (line 64), pytz==2024.1 and volcengine==1.0.140 because these package versions have conflicting dependencies.


Show nested object examples inline

This might be a pain to implement, discuss before picking up.

Alternative is to link to another example of the response

Doesn't work for many objects that don't have a response.

prereq: https://github.com/linode/manager/issues/1615


Add crashlytics-ndk support

I'm getting a SIGSEGV in libflutter.so that flutter_crashlytics doesn't catch.
All that's needed to also catch Android native crashes is to add the gradle dependency com.crashlytics.sdk.android:crashlytics-ndk
And then import com.crashlytics.android.ndk.CrashlyticsNdk, and call Fabric.with(context, Crashlytics(), CrashlyticsNdk())
For now I'll fork flutter_crashlytics and add it myself.  Hopefully resulting in fixing whatever bug is causing a native crash.

Created https://github.com/kiwi-bop/flutter_crashlytics/pull/63 for discussion.


action:subaction and related actions' times

Let's say we have the following graph, depicting an action that starts at 3AM (UTC) and ends at 4AM UTC, and has a recorded sub-action:
{
    "@context": {
        "kb": "http://example.org/kb/",
        "action": "https://ontology.unifiedcyberontology.org/uco/action/",
        "xsd": "http://www.w3.org/2001/XMLSchema#"
    },
    "@graph": [
        {
            "@id": "kb:Action-1",
            "@type": "action:Action",
            "action:subaction": {
                "@id": "kb:Action-2",
                "@type": "action:Action"
            },
            "action:startTime": {
                "@type": "xsd:dateTime",
                "@value": "2020-01-02T03:00:00Z"
            },
            "action:endTime": {
                "@type": "xsd:dateTime",
                "@value": "2020-01-02T04:00:00Z"
            }
        }
    ]
}

Do we know the following about kb:Action-2:

Its start time is at or after 2020-01-02T03:00:00Z.
Its end time is before or at 2020-01-02T04:00:00Z.

Generally speaking, would a subaction always be time-bounded?
(Edited to fix JSON-LD typos, and clarify sentence 1.)

As far as I can determine from the Action ontology, there are no constraints that limit a subaction to start before or end after its parent action. This is in conflict with the definition for the subaction: "[a subaction] References to other actions that make up part of a larger more complex action." that suggests that the parent (larger more complex) action cannot start after the first, nor end before the last, subaction.
In conclusion: whether or not it is the intention for the parts to be proper subparts of the whole, the intention of the textual definition of the parts do not match the logical construction of the whole by its parts. If anything, this conflict should be resolved one way or another.

@plbt5 - Does it it look like action:subaction could be a specialization of isPerdurantProperPartOf from Issue 544?

Indeed it seems to look that way. We need to assure, though, that by introducing this we do not imply that isPerdurantProperPartOf is an InverseFunctionalProperty. With that I mean that while an action:subaction could be considered to be a sub-action of only one super-action, this is not the case with the proper-part relation.
At least, that is what I conclude from the supplemental principles in mereology.

@plbt5 The concern on owl: InverseFunctionalProperty in subproperties is fair.  My understanding is that if a property is not defined as inverse-functional, but a subproperty is, then the parent property does not become inverse-functional.
I just did a test[^1] with Protege and Robot, which both provide access to some Java-based reasoners.  I confirmed my understanding with the following ontology.  Protege complains of inconsistency when a reasoner is turned on, appropriately, until the commented lines are adjusted like suggested.  The inconsistency is that kb:Thing-2 and kb:Thing-3 are inferred to be the same individual via an owl:FunctionalProperty, and that individual inherits both of the different ex:name values, becoming inconsistent with ex:ThingWithOneName's restriction of just one name value.  kb:Thing-5 and kb:Thing-6 trigger the same kind of inconsistency via an owl:InverseFunctionalProperty.  The example works if the other subproperty, ex:op2, is used instead, because the subproperties ex:op3 and ex:op4 do not induce their shared superproperty ex:op1 to become a functional or inverse-functional property.
ROBOT (1.9.5) complains appropriately[^2] with either of the following commands:
java -jar robot.jar \
	  reason \
	  --input asserted.ttl \
	  --output reasoned-hermit.ttl \
	  --reasoner HermiT
java -jar robot.jar \
	  reason \
	  --input asserted.ttl \
	  --output reasoned-jfact.ttl \
	  --reasoner JFact

@prefix ex: <http://example.org/ontology/> .
@prefix kb: <http://example.org/kb/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

ex:ThingWithOneName
	a owl:Class ;
	rdfs:subClassOf [
		a owl:Restriction ;
		owl:onProperty ex:name ;
		owl:cardinality "1"^^xsd:nonNegativeInteger ;
	] ;
	.

ex:name
	a owl:DatatypeProperty ;
	rdfs:range xsd:string ;
	.

ex:op1
	a owl:ObjectProperty ;
	rdfs:domain ex:ThingWithOneName ;
	rdfs:range ex:ThingWithOneName ;
	.

ex:op2
	a owl:ObjectProperty ;
	rdfs:subPropertyOf ex:op1 ;
	.

ex:op3
	a
		owl:ObjectProperty ,
		owl:FunctionalProperty
		;
	rdfs:subPropertyOf ex:op1 ;
	.

ex:op4
	a
		owl:ObjectProperty ,
		owl:InverseFunctionalProperty
		;
	rdfs:subPropertyOf ex:op1 ;
	.

kb:Thing-1
	a owl:Thing ;
	.

kb:Thing-2
	a owl:Thing ;
	ex:name "2" ;
	.

kb:Thing-3
	a owl:Thing ;
	ex:name "3" ;
	.

kb:Thing-4
	a owl:Thing ;
	.

kb:Thing-5
	a owl:Thing ;
	ex:name "5" ;
	.

kb:Thing-6
	a owl:Thing ;
	ex:name "6" ;
	.

########################################################################
# Below this line, if the ex:op3 and ex:op4 predicates are replaced with
# ex:op2, the ontology is consistent.
########################################################################

kb:Thing-1
	ex:op3
		kb:Thing-2 ,
		kb:Thing-3
		;
	.

kb:Thing-5
	ex:op4 kb:Thing-4 ;
	.

kb:Thing-6
	ex:op4 kb:Thing-4 ;
	.

#kb:Thing-1
#	ex:op2
#		kb:Thing-2 ,
#		kb:Thing-3
#		;
#	.
#
#kb:Thing-5
#	ex:op2 kb:Thing-4 ;
#	.
#
#kb:Thing-6
#	ex:op2 kb:Thing-4 ;
#	.

Protege provides the following explanation dialogue:

[^1]: Participation by NIST in the creation of the documentation of mentioned software is not intended to imply a recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that any specific software is necessarily the best available for the purpose.
[^2]: The default reasoner in ROBOT, ELK, does not raise notice of any inconsistencies.  It reviews according to the OWL 2 EL Profile, which does not support owl:FunctionalProperty or owl:InverseFunctionalProperty, so this attempted use of ELK is out of scope of its functionality.

I'd be comfortable proposing (separately) that action:subaction become an owl:InverseFunctionalProperty, and seeing if counter-examples come up in discussion.
Meanwhile, there is still the original question on this Issue, of subaction times relative to the superaction.  For now, I'm interested in a yes or no response on whether the superaction's and subaction's times behave in a manner analagous to, or exactly like, time:intervalIn (distinct from time:intervalDuring).

Yes, I would assert that the intent of the design of Action and subaction is that the time bounds of any sub Action would fall within the time bounds of the super Action.

Thank you, @sbarnum .
This Issue will remain open while awaiting an implementation that can encode that constraint.  At the present time, it is not possible to encode, because of some un-constrainable details on action:endTime and action:startTime as literals of datatype xsd:dateTime.  As xsd:dateTimes, they are not required to have a time zone, and if they have one, they are not required to have any particular time zone.  So the only comparison mechanism available currently, lexical (string) comparison, would only work when the time values are confirmed to have the same time zone.  This is not a test-functionality available in SHACL.  It is available in SPARQL with the TZ() function, but it would take some runtime inferencing and SHACL-SPARQL testing to make work---and it would likely cease to work once user data reaches several common complexities (e.g., data from two time zones, data spelling UTC as Z vs -00:00).
There are other ways to test the superaction-subaction time bounding, but they would require reified time instants.  Any of the following could work, but each would be predicated on another not-yet-filed proposal:
# Assuming adoption of OWL-Time: https://www.w3.org/TR/owl-time/
action:subaction rdfs:subPropertyOf time:intervalIn .

# Assuming an outcome of Issue 544.
action:subaction rdfs:subPropertyOf core:isPerdurantProperPartOf .

(Issue 544.)


fix: breaking update v2.11.1

Current Behavior
Project doesn't compile.
Expected Behavior
To compile correctly.
Steps to Reproduce

Compile with version 2.11.1
Boom

Other Information
Trace:
./node_modules/react-player/es6/ReactPlayer.jsx
--
19:45:31.464 | Module parse failed: Unexpected token (140:8)
19:45:31.464 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:45:31.464 | \|       const { light, playIcon, previewTabIndex, oEmbedUrl } = this.props
19:45:31.464 | \|       return (
19:45:31.464 | >         <Preview
19:45:31.464 | \|           url={url}
19:45:31.464 | \|           light={light}
19:45:31.464 |
19:45:31.464 | Import trace for requested module:
19:45:31.464 | ./node_modules/react-player/es6/ReactPlayer.jsx
19:45:31.464 | ./node_modules/react-player/es6/index.js
19:45:31.464 | ./components/chats/FloatingVideoPlayer.tsx
19:45:31.465 | ./components/chats/DisplayFloatingVideoPlayer.tsx
19:45:31.465 |
19:45:31.465 | ./node_modules/react-player/es6/players/DailyMotion.jsx
19:45:31.465 | Module parse failed: Unexpected token (116:6)
19:45:31.465 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:45:31.465 | \|     }
19:45:31.465 | \|     return (
19:45:31.465 | >

19:45:31.465 | \|

19:45:31.465 | \|

19:45:31.465 |
19:45:31.466 | Import trace for requested module:
19:45:31.466 | ./node_modules/react-player/es6/players/DailyMotion.jsx
19:45:31.466 | ./node_modules/react-player/es6/players/index.js
19:45:31.466 | ./node_modules/react-player/es6/index.js
19:45:31.466 | ./components/chats/FloatingVideoPlayer.tsx
19:45:31.466 | ./components/chats/DisplayFloatingVideoPlayer.tsx
19:45:31.466 |
19:45:31.466 | ./node_modules/react-player/es6/players/Facebook.jsx
19:45:31.466 | Module parse failed: Unexpected token (109:6)
19:45:31.466 | You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
19:45:31.467 | \|     }
19:45:31.467 | \|     return (
19:45:31.467 | >       <div
19:45:31.467 | \|         style={style}
19:45:31.467 | \|         id={this.playerID}

Same error here

same

Same here

Same for me, the app wouldn't compile, but the error was related to not being able to find a DailyMotion dependency

same here
you may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export default class Kaltura extends Component {

static displayName = 'Kaltura'
|   static canPlay = canPlay.kaltura
|   callPlayer = callPlayer

I know this isn't ideal but I just rolled it back in package.json from ^2.11.0 to 2.11.0 and it works

@ralcant that's what I did as well to get it working

same

Stream Chat React using this Library, So I can't lower the version.
It seems they are using the latest version.

same here,
found a workaround using resolutions in yarn.
This may help if some other library of yours is using this library, in other words this is the dependency of a dependency.
https://classic.yarnpkg.com/lang/en/docs/selective-version-resolutions/

If you have a dependency that relias on this dependency, you can solve this with npm overrides.
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides
Thanks @peterpangpeter for sharing the yarn solution.

same issue, i am facing.

same with ^2.10.1. it happens after i up my webpack to 5

+1, facing the same issue:
Failed to compile.

./node_modules/react-player/es6/players/Kaltura.jsx 10:21
Module parse failed: Unexpected token (10:21)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export default class Kaltura extends Component {
>   static displayName = 'Kaltura'
|   static canPlay = canPlay.kaltura
|   callPlayer = callPlayernpm ERR! code ELIFECYCLE
npm ERR! errno 1`

2.11.0 works fine

Not working for us either. Was thinking it was us...

Not working for us either. Was thinking it was us...

Yes, I understand, I too faced difficulties for over two hours, believing that the error was on our end.

Not working for us either. Was thinking it was us...

Yes, I understand, I too faced difficulties for over two hours, believing that the error was on our end.

I am also facing this issue with v2.9.0 (few days back, it was fine).

Replacing ^2.9.0 with 2.9.0 in package.json worked.

Same problem here. The new unbundled JSX distribution breaks our Webpack 5 builds.
https://github.com/cookpete/react-player/pull/1537

Same problem.

Same problem here

+1, facing the same issue:
Failed to compile.

./node_modules/react-player/es6/players/Kaltura.jsx 10:21
Module parse failed: Unexpected token (10:21)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|
| export default class Kaltura extends Component {
>   static displayName = 'Kaltura'
|   static canPlay = canPlay.kaltura
|   callPlayer = callPlayernpm ERR! code ELIFECYCLE
npm ERR! errno 1`

I added a resolution to solve it:
"resolutions": {
    "react-player": "2.11.0"
}

@cookpete please look into this issue urgently for all of us

If you’re building a NextJS app (we are) you might need to add react-player to transpilePackages in order to transpile the new JSX distribution to JS.
https://nextjs.org/blog/next-13-1#built-in-module-transpilation-stable

Looks like I should have tested this suggestion more thoroughly. Apologies all. I’ll remove "module": "es6/index.js" from package.json and publish v2.11.2. People using vite etc can still import from react-player/es6 for the time being.
@wallw-teal any suggestions?


Can the datepicker can only show the year and the month?

This version is deprecated: use ActionSheetPicker-3.0 instead.
https://github.com/skywinder/ActionSheetPicker-3.0


Installing the last Laravel version I get an 404 error

Laravel Version: 5.8.17
PHP Version: 7.2.9
Database Driver & Version:

Description:
Running the command composer create-project --prefer-dist laravel/laravel folder-name
I get the following message error:
[Composer\Downloader\TransportException]
  The "https://packagist.org/p/provider-2019-01%24c9e1e5ae0ec533b5a64a9e7a5dd2df5870b351f4e523c5e7186832d08c452cb7.json" file could not b
  e downloaded (HTTP/1.1 404 Not Found)

So I can't continue with the installation.
Steps To Reproduce:
Just create a laravel project using composer.

The url is working now, thank's for fixed!
https://packagist.org/p/provider-2019-01%24c9e1e5ae0ec533b5a64a9e7a5dd2df5870b351f4e523c5e7186832d08c452cb7.json