Error installing in Meteor 1.3.3

As soon as I did a "meteor update" to upgrade to 1.3.3, I got an error C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:165
throw error;
Error: ENOENT, open 'C:\Users\Airedale\AppData\Local\Temp\mt-1n5omma\os\remcoder:chronos.js'
I then removed the remcoder:chronos package and reinstall "meteor update remcoder:chronos" and got the same error again.
Now I cannot install at all. Looks like promise_server.js from meteor-tool 1.3.3 has problem with remcoder:chronos.

Weird. I don't see any Chronos specifics in the stack trace other than that
the main file could not be loaded. Could you verify this problem is
specific to Chronos?
On Thu, Jun 16, 2016, 09:58 airedale302<EMAIL_ADDRESS>wrote:

As soon as I did a "meteor update" to upgrade to 1.3.3, I got an error
C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:165
throw error;
Error: ENOENT, open
'C:\Users\Airedale\AppData\Local\Temp\mt-1n5omma\os\remcoder:chronos.js'
I then removed the remcoder:chronos package and reinstall "meteor update
remcoder:chronos" and got the same error again.
Now I cannot install at all. Looks like promise_server.js from meteor-tool
1.3.3 has problem with remcoder:chronos.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11, or mute the thread
https://github.com/notifications/unsubscribe/AAcLUqxyWxrZSGRsc5v-3lAXbZ3RgRCJks5qMQIagaJpZM4I3HnJ
.

Hi,
I don't actually know. I just know that after I "meteor update" to Meteor
1.3.3, I cannot install remcoder:chronos.
I am able to install a similar package on Meteor 1.3.3 with "meteor update
panter:moment-reactive".
Strangely, I try to add remcoder:chronos to a different app that is still
under Meteor 1.3.2, and I got the same error:
C:\Meteor\tcm2>meteor add remcoder:chronos
C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.2_4\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:116
throw error;
^
Error: ENOENT, open
'C:\Users\Airedale\AppData\Local\Temp\mt-18qb0td\os\remcoder:chronos.js'
I don't know if the problem is specific with Chronos or with my particular
setup.
On Thu, Jun 16, 2016 at 1:11 AM, Remco Veldkamp<EMAIL_ADDRESS>wrote:

Weird. I don't see any Chronos specifics in the stack trace other than that
the main file could not be loaded. Could you verify this problem is
specific to Chronos?
On Thu, Jun 16, 2016, 09:58 airedale302<EMAIL_ADDRESS>wrote:

As soon as I did a "meteor update" to upgrade to 1.3.3, I got an error

C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:165

throw error;
Error: ENOENT, open
'C:\Users\Airedale\AppData\Local\Temp\mt-1n5omma\os\remcoder:chronos.js'
I then removed the remcoder:chronos package and reinstall "meteor update
remcoder:chronos" and got the same error again.
Now I cannot install at all. Looks like promise_server.js from
meteor-tool
1.3.3 has problem with remcoder:chronos.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11, or mute the thread
<
https://github.com/notifications/unsubscribe/AAcLUqxyWxrZSGRsc5v-3lAXbZ3RgRCJks5qMQIagaJpZM4I3HnJ
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226417237,
or mute the thread
https://github.com/notifications/unsubscribe/AOqXX77gV17K8Xjx9xc8JeW3HbPPUO68ks5qMQUYgaJpZM4I3HnJ
.

Which Chronos version did you try to install in the 1.3.2 project?
On Fri, Jun 17, 2016, 03:16 airedale302<EMAIL_ADDRESS>wrote:

Hi,
I don't actually know. I just know that after I "meteor update" to Meteor
1.3.3, I cannot install remcoder:chronos.
I am able to install a similar package on Meteor 1.3.3 with "meteor update
panter:moment-reactive".
Strangely, I try to add remcoder:chronos to a different app that is still
under Meteor 1.3.2, and I got the same error:
C:\Meteor\tcm2>meteor add remcoder:chronos
C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.2_4\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:116
throw error;
^
Error: ENOENT, open
'C:\Users\Airedale\AppData\Local\Temp\mt-18qb0td\os\remcoder:chronos.js'
I don't know if the problem is specific with Chronos or with my particular
setup.
On Thu, Jun 16, 2016 at 1:11 AM, Remco Veldkamp<EMAIL_ADDRESS>wrote:

Weird. I don't see any Chronos specifics in the stack trace other than
that
the main file could not be loaded. Could you verify this problem is
specific to Chronos?
On Thu, Jun 16, 2016, 09:58 airedale302<EMAIL_ADDRESS>wrote:

As soon as I did a "meteor update" to upgrade to 1.3.3, I got an error

C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:165

throw error;
Error: ENOENT, open

'C:\Users\Airedale\AppData\Local\Temp\mt-1n5omma\os\remcoder:chronos.js'

I then removed the remcoder:chronos package and reinstall "meteor
update
remcoder:chronos" and got the same error again.
Now I cannot install at all. Looks like promise_server.js from
meteor-tool
1.3.3 has problem with remcoder:chronos.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11, or mute the thread
<

https://github.com/notifications/unsubscribe/AAcLUqxyWxrZSGRsc5v-3lAXbZ3RgRCJks5qMQIagaJpZM4I3HnJ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226417237,
or mute the thread
<
https://github.com/notifications/unsubscribe/AOqXX77gV17K8Xjx9xc8JeW3HbPPUO68ks5qMQUYgaJpZM4I3HnJ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226657296,
or mute the thread
https://github.com/notifications/unsubscribe/AAcLUs6HEmXwd0eTDphOXWbeWgvHRSKkks5qMfVcgaJpZM4I3HnJ
.

Did the error actually occur when running meteor install remcoder:chronos
or when running your application after the installation?
On Fri, Jun 17, 2016, 08:36 Remco Veldkamp<EMAIL_ADDRESS>wrote:

Which Chronos version did you try to install in the 1.3.2 project?
On Fri, Jun 17, 2016, 03:16 airedale302<EMAIL_ADDRESS>wrote:

Hi,
I don't actually know. I just know that after I "meteor update" to Meteor
1.3.3, I cannot install remcoder:chronos.
I am able to install a similar package on Meteor 1.3.3 with "meteor update
panter:moment-reactive".
Strangely, I try to add remcoder:chronos to a different app that is still
under Meteor 1.3.2, and I got the same error:
C:\Meteor\tcm2>meteor add remcoder:chronos
C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.2_4\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:116
throw error;
^
Error: ENOENT, open
'C:\Users\Airedale\AppData\Local\Temp\mt-18qb0td\os\remcoder:chronos.js'
I don't know if the problem is specific with Chronos or with my particular
setup.
On Thu, Jun 16, 2016 at 1:11 AM, Remco Veldkamp<EMAIL_ADDRESS>
wrote:

Weird. I don't see any Chronos specifics in the stack trace other than
that
the main file could not be loaded. Could you verify this problem is
specific to Chronos?
On Thu, Jun 16, 2016, 09:58 airedale302<EMAIL_ADDRESS>wrote:

As soon as I did a "meteor update" to upgrade to 1.3.3, I got an error

C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:165

throw error;
Error: ENOENT, open

'C:\Users\Airedale\AppData\Local\Temp\mt-1n5omma\os\remcoder:chronos.js'

I then removed the remcoder:chronos package and reinstall "meteor
update
remcoder:chronos" and got the same error again.
Now I cannot install at all. Looks like promise_server.js from
meteor-tool
1.3.3 has problem with remcoder:chronos.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11, or mute the thread
<

https://github.com/notifications/unsubscribe/AAcLUqxyWxrZSGRsc5v-3lAXbZ3RgRCJks5qMQIagaJpZM4I3HnJ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226417237,
or mute the thread
<
https://github.com/notifications/unsubscribe/AOqXX77gV17K8Xjx9xc8JeW3HbPPUO68ks5qMQUYgaJpZM4I3HnJ
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226657296,
or mute the thread
https://github.com/notifications/unsubscribe/AAcLUs6HEmXwd0eTDphOXWbeWgvHRSKkks5qMfVcgaJpZM4I3HnJ
.

The error occurred when I tried to install with "meteor add
remcoder:chronos". The package never get installed.
Before I updated Meteor to 1.3.3, I was able to install remcoder:chronos.
The version of Chronos I tried to install was 0.4.2, which is what gets
delivered by atmospherejs.com when I run "meteor add remcoder:chronos". The
version number momentarily flashed on the screen just before the error
message popped up.
On Thu, Jun 16, 2016 at 11:39 PM, Remco Veldkamp<EMAIL_ADDRESS>wrote:

Did the error actually occur when running meteor install remcoder:chronos
or when running your application after the installation?
On Fri, Jun 17, 2016, 08:36 Remco Veldkamp<EMAIL_ADDRESS>wrote:

Which Chronos version did you try to install in the 1.3.2 project?

On Fri, Jun 17, 2016, 03:16 airedale302<EMAIL_ADDRESS>wrote:

Hi,
I don't actually know. I just know that after I "meteor update" to
Meteor
1.3.3, I cannot install remcoder:chronos.
I am able to install a similar package on Meteor 1.3.3 with "meteor
update
panter:moment-reactive".
Strangely, I try to add remcoder:chronos to a different app that is
still
under Meteor 1.3.2, and I got the same error:
C:\Meteor\tcm2>meteor add remcoder:chronos

C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.2_4\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:116

throw error;
^
Error: ENOENT, open
'C:\Users\Airedale\AppData\Local\Temp\mt-18qb0td\os\remcoder:chronos.js'
I don't know if the problem is specific with Chronos or with my
particular
setup.
On Thu, Jun 16, 2016 at 1:11 AM, Remco Veldkamp <
<EMAIL_ADDRESS>
wrote:

Weird. I don't see any Chronos specifics in the stack trace other than
that
the main file could not be loaded. Could you verify this problem is
specific to Chronos?
On Thu, Jun 16, 2016, 09:58 airedale302<EMAIL_ADDRESS>wrote:

As soon as I did a "meteor update" to upgrade to 1.3.3, I got an
error

C:\Users\Airedale\AppData\Local.meteor\packages\meteor-tool\1.3.3\mt-os.windows.x86_32\isopackets\ddp\npm\node_modules\meteor\promise\node_modules\meteor-promise\promise_server.js:165

throw error;
Error: ENOENT, open

'C:\Users\Airedale\AppData\Local\Temp\mt-1n5omma\os\remcoder:chronos.js'

I then removed the remcoder:chronos package and reinstall "meteor
update
remcoder:chronos" and got the same error again.
Now I cannot install at all. Looks like promise_server.js from
meteor-tool
1.3.3 has problem with remcoder:chronos.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11, or mute the thread
<

https://github.com/notifications/unsubscribe/AAcLUqxyWxrZSGRsc5v-3lAXbZ3RgRCJks5qMQIagaJpZM4I3HnJ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/remcoder/chronos/issues/11#issuecomment-226417237
,
or mute the thread
<

https://github.com/notifications/unsubscribe/AOqXX77gV17K8Xjx9xc8JeW3HbPPUO68ks5qMQUYgaJpZM4I3HnJ

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226657296,
or mute the thread
<
https://github.com/notifications/unsubscribe/AAcLUs6HEmXwd0eTDphOXWbeWgvHRSKkks5qMfVcgaJpZM4I3HnJ

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/remcoder/chronos/issues/11#issuecomment-226692101,
or mute the thread
https://github.com/notifications/unsubscribe/AOqXX-fhRKhXtYneEDs6RaKZ7al-deX_ks5qMkESgaJpZM4I3HnJ
.

Sorry about the delay. I can reproduce the issue on Windows 10 but not on my Mac, so I think it it Windows specific. Meteor tries to load the file remcoder:chronos.js from a temporary directory but the directory does not exist at all.

Currently I have no idea how to approach this issue, unfortunately. Help would be appreciated, any suggestion or brain fart will do...

I updated to latest meteor and get same error - using Windows 7. I'm not real familiar with meteor packages but I'm thinking it relates to the naming of your remcoder:chronos.js file. And how it's added via api.addFiles('remcoder:chronos.js');
Perhaps rename to remcoder-chronos.js ?

thx @slevr! Indeed the colon was the culprit. I've fixed it in the v0.5.x branch which I will deploy asap.

v0.5.0 was just published, which fixes this issue. Sorry it took so long (apparently this issue was present from the very first version of Chronos) and thx to @slevr for suggesting a solution :D


execute_read does not preserve stream

I have two questions about the code below:

isn't max_count an option for read_stream/3 and not stream!/3?
on line 274, Enum.map is used, how does this not cause a call to this function to hang forever? Shouldn't it be Stream.map?

https://github.com/fabriziosestito/commanded-spear-adapter/blob/main/lib/commanded/event_store/spear.ex#L262-L279

from https://hexdocs.pm/spear/Spear.html#read_stream/3 I read

:max_count - (default: 42) the maximum number of events to read from the EventStoreDB stream. Any positive integer is valid. Even if the stream is longer than this :max_count option, only :max_count events will be returned from this function. :infinity is not a valid value for :max_count. Use stream!/3 for an enumerable which reads an EventStoreDB stream in its entirety in chunked network requests.

So it seems stream! is the correct call but max_count should be chunk_size instead? Commanded calls this parameter read_batch_size, so I guess this is how it's intended. The stream should be infinite, but the read_batch_size parameter controls how many are fetched at a time?

Hey @dvic, I took the liberty to modify your comment to point it to the main branch.

So it seems stream! is the correct call but max_count should be chunk_size instead?

I will investigate thanks. It seems that chunk_size is indeed what is intended by Commanded.

isn't max_count an option for read_stream/3 and not stream!/3?

It is not. I guess we are returning the default chunk size (128).

on line 274, Enum.map is used, how does this not cause a call to this function to hang forever? Shouldn't it be Stream.map?

We need an Enum function to run the enumeration. Stream.map will return another stream (lazy) and not a list of events.

execute_read does not preserve stream

Sorry I did not understand the title, could you please elaborate what is that you are experiencing?

Hey @dvic, I took the liberty to modify your comment to point it to the main branch.

So it seems to stream! is the correct call but max_count should be chunk_size instead?

I think stream!/3 here is not correct because Commanded here wants to read batches of events. stream!/3 returns the whole stream instead, but you can control how the network requests are chunked. So probably this is wrong and read_stream/3 seems what we should use.

Not sure about this, in the documentation of commanded read_batch_size is described as the number of events to read at a time from storage. The at a time part for me indicates that it should return all events at the point in time when this function was called. This is also what Spear.stream! does, so it is correct, but instead we should pass the chunk_size parameter, the max_count parameter is not mentioned in the docs and source code: https://hexdocs.pm/spear/Spear.html#stream!/3

isn't max_count an option for read_stream/3 and not stream!/3?

I meant to say here: this is a typo, like mentioned above, max_count is not an option for stream!/3, see https://hexdocs.pm/spear/Spear.html#stream!/3

on line 274, Enum.map is used, how does this not cause a call to this function to hang forever? Shouldn't it be Stream.map?

We need an Enum function to run the enumeration. Stream.map will return another stream (lazy) and not a list of events. By using stream!/3 we simply return the whole stream. See: https://hexdocs.pm/spear/Spear.html#stream!/3-enumeration-characteristics

But we do need to return here a (lazy) stream right? the docs https://hexdocs.pm/commanded/Commanded.EventStore.Adapter.html#c:stream_forward/4 say the return type should be an Enumerable.t(), not per se a list.

execute_read does not preserve stream

Sorry, I did not understand the title, could you please elaborate on what is you are experiencing?

I meant to say here that the current implementation eagerly consumes the stream (by using Enum.map/2), which is not what you want here.

So for example, this assertion in test/event_store/serialization_test.exs
assert [%RecordedEvent{data: ^data, metadata: ^metadata}] =
             Spear.stream_forward(event_store_meta, stream)

should actually be
    assert [%RecordedEvent{data: ^data, metadata: ^metadata}] =
             Spear.stream_forward(event_store_meta, stream) |> Enum.to_list()

Thanks! I was investigating this and you are indeed right.
We also to change how the Snapshotting, because it assumes execute_read returns an enumerable.

Yes, I'm looking into this now but I'm running into trouble with the 'stream exists' check, currently what is done by checking the empty list is also not correct, see  https://github.com/NFIBrokerage/spear/pull/68/files. TLDR: the stream! function returns an empty list also when from is larger than the last event number.


Istio OSS Release Process Doc

This is the Istio OSS release process that we have reviewed in the working group meeting yesterday.
https://docs.google.com/document/d/1r36tGVhH9R7VhQT9q_nltRMjUjUA02ntpKMi8Bl7vyA/edit?ts=5a750deb#
Lin, please review and also approve the Google Doc (i.e. add a "X" next to your name) if you approve the process.

@hklai: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
94ff56a694abbcb9d52af3e97349723df2b7db73
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks Lin.
It was partially documented in Martin's doc (https://goo.gl/dcSBxF
https://goo.gl/dcSBxF) about LTS releases.
There will be discussion around whether we make 0.7 an LTS (or quarterly,
fully supported release). It is mainly a manual process on top of the
regular scheduled release process as documented here. We can amend this doc
later if needed. WDYT?
On Mon, Feb 12, 2018 at 6:00 PM, Lin Sun<EMAIL_ADDRESS>wrote:

@linsun commented on this pull request.
This looks good. My only comment is for monthly release and quarterly
release... How are we differentiating those?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/3369#pullrequestreview-96006305, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkNbbPfeyybg_eDa-rA28XpmBdF_dks5tUOzZgaJpZM4SAaUj
.

Yes, it is ok to append.  I just think that is an important thing to put out in the website as our monthly release and unstableness has caused many concerns.

Agreed. And I added some basic info in
https://docs.google.com/document/d/1r36tGVhH9R7VhQT9q_nltRMjUjUA02ntpKMi8Bl7vyA/edit#heading=h.zapoyhjl32gq
until we have a more established process around it.
If that looks fine, please explicitly approve the doc as well. I will also
copy the addition to the README.md in this PR.
Thanks!
On Mon, Feb 12, 2018 at 6:26 PM, Lin Sun<EMAIL_ADDRESS>wrote:

Yes, it is ok to append. I just think that is an important thing to put
out in the website as our monthly release and unstableness has caused many
concerns.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/pull/3369#issuecomment-365130857, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AeRtkGv-oJMjocYrh34cdBMhBSnqD5sHks5tUPLBgaJpZM4SAaUj
.

I have added information about quarterly release in https://docs.google.com/document/d/1r36tGVhH9R7VhQT9q_nltRMjUjUA02ntpKMi8Bl7vyA/edit#, and also updated README.md accordingly.
Thanks Lin for the approval!

@hklai: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
611e3faccee159da7b1a27ba2483c8b024b180c4
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Method to restore session manually instead of just on page refresh

My authentication service (AWS Cognito) expires its token every 30 minutes. This doesn't mean the user is logged out, it just means I need to get a new token.
Currently I have this implemented in my ESA authenticator's restore method, which only runs on page load. If the user sits idle, without refreshing the page, my API calls fail because their Access token is no longer valid.
I'd like to repeatedly restore my session at some  interval to ensure my access token is fresh. Is it possible to expose a method on the session service to achieve this?
this.get('session').restore()

Shoot, just realized #1263  is related and possibly a duplicate. This issue/feature-request would be a general case that could probably help those guys out as well.

The OAuth 2.0 authenticator refreshes tokens periodically as well. I guess a similar mechanism would work for you as well?

Hmm. so put the polling inside the actual custom authenticator. Can you help me understand how this code works? How does the new token that is retrieved at some future time get set to the session? It seems like this code spawns a scheduled promise from within the restore method, but I don't understand how the new token gets set back to  session.data

Whenever the token is refreshed, the authenticator triggers the sessionDataUpdated event that the session is subscribed to automatically.

Closing this as a (solved) question.


Should publish the JAR files as well for collector...

There are still some compile/build issues with the Maven build due to protected / private access of certain methods...

@softwareklinic can you post the build error log?

I just left comment on this issue where another user had exact same issue with protected vs private access of same method.
https://github.com/capitalone/Hygieia/issues/206

@softwareklinic this should be fine now. If you agree, lets close it.

Yes closing


Automated Migration for Breaking Changes to the Type System

Automated Migration for Breaking Changes to the Type System
Search Terms
codemod, migration, upgrade
Suggestion
semi-automated migration when there are breaking changes in the type system
One way of implementing this would be via codemods (could use the TS Compiler API) that do trivial update tasks as described in https://github.com/microsoft/TypeScript/issues/33272
Use Cases

Would make it easier for users to upgrade to the latest TypeScript
Would make it easier for the TS team to upgrade TypeScript
Might enable TS to evolve faster, as the pain from these "breaking" changes will be smaller

The changes described in https://github.com/microsoft/TypeScript/issues/33272, for example, were mostly trivial, and ideally would not need much human intervention.
Type-only changes are especially amenable to this kind of treatment, because no one's app will misbehave at runtime if there is a bug in the transformation.
I say 'semi-automated' because in cases where the tool can't figure out the problem, the tool could yield to human judgment. Tooling for this doesn't have to be perfect, but a small amount of automation could go a long way.
Examples
example.ts
const myPromise: Promise<{}> = dontCarePromise();

tsc --upgrade --from=3.5 --to=3.6 example.ts
const myPromise: Promise<unknown> = dontCarePromise();

The example is from https://github.com/microsoft/TypeScript/issues/33272.
In a case where the conversion would lead to a new type error, I'd expect the tool to bail out, explain the situation, and let the human decide what to do.
Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

This is cool, I'd also like to see the same on a per-flag basis, e.g. tsc --upgrade-flag strictFunctionTypes  example.ts

If we think it's possible and useful, we do build quickfixes for the editor for these kinds of things (though we still don't have a tool to run fixes from the command line @DanielRosenwasser ). We just don't always bother - the unknown default change only needed around 20 packages on DT updated (each in one or two places), so didn't seem all that bad.

To throw this out there: I think #13195 would be something that needs automated migration.

Should I close this issue, given that this sort of thing is in the works already per Wes' comment? https://github.com/microsoft/TypeScript/issues/33345#issuecomment-530123819

I mean, I'd leave that to @DanielRosenwasser, as he's been looking for a reason to build out the quickfixes-on-the-commandline feature for forever.

Broadly speaking there are two distinct categories of things to consider here:

Breaks for which the root cause is tractably identifiable by the type system (Type I)
Breaks for which the root cause is not tractably identifiable by the type system (Type II)

An example Type I break would be strictClassPropertyInitialization - by the construction of the error itself, it's trivial for TS to identify that "I am issuing an error because of a rule that was added in a breaking manner".
An example Type II break would be the Set constructor change identified in #33272 - this was caused by a subtle change in inference rules, and the exact error occurring later in the code isn't something TS could plausibly trace back to a change in behavior.
We can create Quick Fixes for Type I errors, and typically do. These also tend to be very well-documented and well-thought-out changes because they're typically the "We are breaking you on purpose" kind of breaking change. Many Type I breaks are also associated with a commandline flag to turn them off.
For a Type II error, even if we could figure out what happened, often there's no "quick fix" because it depends on what the code was trying to do in the first place, and the change that does need to occur might be very lexically far away from where the first actual type error is issued.
We can provide tooling all day long for Type I breaks, but I would argue that this is a bit of a low-value activity. These breaks are often not particularly painful, are signaled well in advance, and usually have a simple commandline fix or can be bulk-addressed by a sufficiently clever RegExp. Adopting something like Facebook's codemod tool for offering a CLI experience for these fixes is something we might look in to.
Type II breaks are vexing. Often we don't even really know we're making them - the filter(Boolean) break again from #33272 is an example. And even if we did fully realize this was going to be a break, it's not clear what we'd do about it. There's no obvious quickfix to issue for "This expression is going to change to an arguably more-accurate type in a way that might break downstream code that makes certain other assumptions".
For example, let's say you wrote some code
const arr = [1, 2, 3, "four", "five"];
const arr2 = arr.filter(x => +x === x);
arr2.push("six");

Maybe in the future, TS gets smarter and says +x === x is a type-guarding expression for x is number, and also gets smarter by identifying that array.filter(type guard function) returns a more-specific array type. At first glance, this isn't a breaking change... but it is: the arr2.push("ok") line is now an error because arr.filter returned number[] instead of (string | number)[].
In even the most trivial example, the error is very causally disconnected from the original change, and it's not even clear what the right "fix" to issue is.
What it seems like you want for Type II errors is just a tool that runs tsc, takes the errors, and inserts either assertions or // @ts-ignore comments depending. For example, I'd probably want one of two outputs depending on error density:
const arr = [1, 2, 3, "four", "five"];
const arr2 = arr.filter(x => +x === x);
// @ts-ignore Error 'cannot convert "six" to 'number'" introduced in TS 4.2
arr2.push("six");

vs
const arr = [1, 2, 3, "four", "five"];
// TODO: Multiple errors involving 'arr2' introduced in TS 4.2
const arr2: any = arr.filter(x => +x === x);
arr2.push("six");
arr2.push("seven");
arr2.push("eight");

We can provide tooling all day long for Type I breaks, but I would argue that this is a bit of a low-value activity. These breaks are often not particularly painful, are signaled well in advance, and usually have a simple commandline fix or can be bulk-addressed by a sufficiently clever RegExp.

I feel that quick fixes, more often than not, are often fairly low-effort and help educate users more about the breaks themselves and how to fix them. So I don't believe it's low-value, and even if it is, the effort isn't unreasonable in the first place.


is this repository accepting for hacktober fest ??

I wish to contribute a small frontend project to this repository, are you guys accepting for hacktober fest 2022 ?

Yes!


Do not run elevated by default

Summary of the Pull Request
Make the runner not run as elevated by default. Add a setting for "run PowerToys as elevated" and buttons to restart the process with different elevation level.

PR Checklist

[x] Needed for #413
[x] CLA signed. If not, go over here and sign the CLA

Validation Steps Performed
Manual

It looks great.
We may need to change a little bit the text in the settings to clarify the difference between the option to start PT elevated and the button to restart PT elevated.

Regarding the ShotcutGuide running non-elevated: when the current active window is elevated, the guide will not show up. Is that caused by not being able to become the top most window or by failing to generate the preview? In the second case can we just not show the preview?

I think it is because keyboard hook not working when the active window is elevated, but I should double check this.

When both Start at login and Run PowerToys with elevated privileges are on, at login you get the UAC dialog. We need to make sure there is no way to avoid this.

Can we reduce the space between the two controls?

Run PowerToys with elevated privileges -> By default, run PowerToys with elevated privileges
Not sure if it sounds better PowerToys are... or PowerToys is... in the first case it refers to the modules, in the second case it refers to the application. I'm more for is.
Instead of changing the button text that looks fine, I suggest to add the explanation in the description:
PowerToys is currently running without elevated privileges. You can restart it to run elevated only for this session, without changing the default setting.

Feel free to suggest different wording.

lets hold here.
It is unclear why someone needs to run with the elevated permissions.  That is what must clearly be articulated to the end user.
Is it to be on top of everything for Shortcut Guide, that requires admin?

@crutkas
any module that needs to interact with elevated windows needs to run elevated.
For example FZ can't resize any elevated window if it's not running elevated.

I think we need to be crisp and clear and document which modules need what. Can we detect if a window is at elevated privilege then elevate us?  Or warn the users we detected an app and require to be launched elevated?

@crutkas
any PowerToy that interacts with other applications may need elevated privileges, but it's not something we can enable on a per-module base, it has to be the runner to be elevated and make all modules elevated.
Currently the ShortcutGuide and FancyZones, but also AlwaysOnTop, MaximizeToNewDesktop would require it. Only PowerRename doesn't need it since it's not running the PowerToys process.
I'm not sure we can reliably detect if a window is running elevated without running elevated ourselves.
I suggest that for now we improve the documentation, to let users know that PowerToys needs to run elevated to interact with elevated windows and see the feedback.

why does shortcut guide need it?

I'm ok checking this in now.  I added a .15 item to review language and a .16 item to document the items @enricogior described here

why does shortcut guide need it?

Because if the active window is elevated, the keyboards events can't be received unless PowerToys also runs elevated.


Does not work with cmake 3.1 compatibility level

Hello,
I added an example (08a33206c336c22fe3e39027643c737f15a6cc46) as proposed by the Readme.md but set the cmake compatibility to 3.1. Then I get:
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
CMake Warning at /Users/gjasny/src/CMakePCHCompiler/CMakePCHCompiler.cmake:39 (message):
  Precompiled headers not supported for AppleClang
Call Stack (most recent call first):
  CMakeLists.txt:8 (target_precompiled_header)

CMake Warning at /Users/gjasny/src/CMakePCHCompiler/CMakePCHCompiler.cmake:39 (message):
  Precompiled headers not supported for AppleClang
Call Stack (most recent call first):
  CMakeLists.txt:12 (target_precompiled_header)

-- Configuring done
-- Generating done
-- Build files have been written to: /Users/gjasny/src/CMakePCHCompiler/example

I'm using CMake 3.1.3 with Xcode 6.1.1 on OSX Yosemite.
Thanks,
Gregor

Fixed in eef4f07eceff21e469829b27c6d094e98be22c62. Thank you.


luci-theme-openwrt-2020: fix readability issues

Context
I've started using this theme (which I really like it) and I've spotted two issues:
Issue 1: iface badges cuts the iface name because it overflows
This is how it looks currently:

Fix by setting white-space: normal and text-align: center:

Issue 2: iface boxes (Network and Wireless sections in Status->Overview) cuts text in small resolutions and center content with too much space in big resolutions with different margins/paddings.
This is how it looks currently:

Fix by setting .ifacebox-body width: 100% and changing .network-status-table > .ifacebox flex settings to flex-grow: 1 and .ifacebox width to min-width, this way there is no more weird margins on high resolutions or cut test in small resolutions:

@skgsergio What happened?

Woops. I've deleted my fork, I've been doing some cleaning and I forgot about this PR, so it auto closed.

Woops. I've deleted my fork, I've been doing some cleaning and I forgot about this PR, so it auto closed.

@skgsergio your commits still available by a direct link and you can restore them from patches:

https://github.com/openwrt/luci/pull/6358/commits/31043803d80419eaf75977c3ca0dc475ca0385df.patch
https://github.com/openwrt/luci/commit/2c50112adadb6969e396342b8e2933ad70efb203.patch
https://github.com/openwrt/luci/commit/ff3b2097eccb363fd27a4fe2ecd73345427bdc73.patch

If the PR still valuable please reopen it. UI and themes are a week part of the whole OpenWrt project


Update index.md

This change would break the article, so I'm going to close this up. Take a look at the contributing.md to learn how to contribute in this repo. You can open a discussion if you have any questions ✨

@bruce


Missing Peak Performance Buff (World)

The Peak Performance skill gives a bonus buff when at full health. None of the tabs in the abnormality widget has Peak Performance, even though other skill buffs (like Latent Power, Offensive Guard, and Affinity Sliding) are available in the Armor Skills tab.

Peak Performance does not have a timer

Neither does Mega Demondrug/Armorskin and yet they are available for the tray.


proposal: dl/gotip: enable configuring install path

Proposal Details
Currently, gotip installs to ~/sdk on macOS. This is fine for one-off uses, where I delete gotip and ~/sdk afterward, but if I want to keep gotip around, it can't stay there. I have a particular organization to things, and I don't put arbitrary stuff in ~.
How about having an environment variable like GOTIP_PATH or a flag like -gotip-path (or both, one overriding the other) that you can set however you like, defaulting to ~/sdk (or ~ or ~/Library/Application Support/gotip (on macOS))?

CC @golang/release

I believe this is exactly the same as issue #26520. In that issue, one of the suggested names for a environment variable to control this was GOSDK.

Duplicate of #26520

@seankhliao Can you put gotip in the title of the other one so people can find it?


Add dynamic artifacts naming, documentation and tests

Describe changes
I implemented the dynamic artifacts naming for output artifacts to support the following use cases:

Static naming (as it was before)
Dynamic via placeholder - {time} and {date} are supported out of the box + any custom placeholder can be passed via substitutions

@step(substitutions={"my_time":"value"})
def ret_42()->Annotated[float,"dummy_{my_time}"]:
    return time.time()

@pipeline
def my_pipeline(substitutions={"my_time":"some_pipe_defenition"}):
    ret_42()
    ret_42(substitutions={"my_time":"another_value"})()

The same applies to ArtifactConfig(name=...) pattern.
There are breaking changes for frontend since now the user can see something like this:

The actual substitutes of the step can be acquired from the PipelineRunResponse, but on frontend the evaluation of the templated names from DeploymentResponse should happen anyways to map those "pre-defined" outputs once they are created on backend.
DO NOT MERGE BEFORE FE CHANGES ARE READY
Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[x] If my change requires a change to docs, I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[x] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@Cahllagerfeld let me know what would be the most efficient way to prepare the data for you, as now substitutes are quite distributed:
There are breaking changes for frontend since now the user can see something like this:

The current way of thinking to approach this is the following:

We know the templated names from the deployment (e.g. my_name_{time}_{ck_pipe}_{ck_step)
We know the pipeline level substitutes from the PipelineRunResponse (ck_pipe is here)
We know the step level substitutes from the StepRunResponse (ck_step is here + overrides for ck_pipe may be here, same applies to overrides of the time and date)
We know date and time substitutes from the start_time of the PipelineRunResponse (time and date can be derived from it)

It seems logical to populate StepRunResponse properly on the backend with all needed substitutes, so we do not compute on the FE. Would this do? Any contras @schustmi @Cahllagerfeld ?

One more general question: From what I can see, you now removed the PipelineRunResponse.metadata.substitutions, which previously contained the substitutions for all the steps.
If I remember correctly that was so the frontend has these substitutions available in the DAG visualizer without querying hydrated versions of all steps. Did you think of an alternative solution to make the matching work in the frontend?

You are right here - I removed it ignoring the fact that steps ar not hydrated there. I brought it back as steps_substitutions


Add enhanced training script

Address #8

Sure, I can update those. I'm not sure what the formatting issue is in the last bullet though.

" - Export ..." looks like it was supposed to be a new item on the bulleted list?

Oh thanks for catching. The markdown preview on my editor displays it fine. I'll look into it.


new production system is twitchy about running the monitor status job

Normal process
See Monitoring Connections to Authorities to understand the normal processing.
Current problem
This process is being twitchy.  It runs sometimes and not others.  We were not able to pin down why.  It worked great in the previous production system for years.
Potential future work

Production is currently configured to run jobs :async.  If you set up sidekiq or some other job system, you can update production environment to run in background.
If you switch to background jobs, the Pingdom process should still work.  Instead of getting a time out, the page will return an error on the 4:10 am load if one of the authorities is failing.  The slight change is that you will no longer see the down/up pattern.  You will only see a down when an authority is failing.

I tried the following for debugging.

Redeploy the system - This seemed to work sometimes and have no affect other times.  And redeploying has its own issues where the system doesn't come back up sometimes.

Turn off performance calculations by turning off performance related displays in the production env file in S3.  The calculations are very processor intensive.

DISPLAY_PERFORMANCE_GRAPH=false
DISPLAY_PERFORMANCE_DATATABLE=false

NOTE: I've never gotten Graph generation to work in Elastic Beanstalk even though they run fine on my laptop.  I wasn't able to test them in the new setup because of this issue.

I reset the preferred time zone to a time that expired the cache during the day when I could watch it fail.  Only it never failed when I did that.  This could mean there is something unique happening during the night that is causing the failure.


Backport "Allow export statements in AnyVal" to LTS

Backports #21653 to the 3.3.5.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to backport-lts-3.3-22148.
Reference


Lack of unique constraints on Sponsorship model

With no unique constraint on the Sponsorship model, there can exist duplicates on repeated imports.
I propose adding a unique_together constraint.
class Meta:
    unique_together = ('organization', 'event', 'amount')

Proposal accepted :-)


Online playground crashes when calling Float64#**(Int32)

This code:
{% p Crystal::LLVM_VERSION %} # => "13.0.1"

lib Foo
  fun powi_f64 = "llvm.powi.f64.i32"(value : Float64, power : Int32) : Float64
end

struct Float64
  def foo(other : Int32)
    Foo.powi_f64(self, other)
  end
end

3.0.foo(2)

crashes on the online playground with:
collect2: fatal error: ld terminated with signal 31 [Bad system call], core dumped
compilation terminated.
Error: execution of command failed with code: 1: `cc "${@}" -o /home/crystal/.cache/crystal/crystal-run-eval.tmp  -rdynamic -L/usr/bin/../lib/crystal -lpcre -lm -lgc -lpthread -levent  -lrt -ldl`

However for some reason calling Foo.powi_f64(3.0, 2) directly works. I am unable to reproduce this locally.
This only happens on 1.4.0 and 1.4.1. Using the old llvm.powi.f64 doesn't help as LLVM reports Intrinsic name not mangled correctly for type arguments instead.

Might be more relevant for https://github.com/jhass/carc.in, not sure if it's the compiler, LLVM, or the host's fault here

Might be old Linux version? Is it possible to get the Linux version out of carc.in?

Ah or there could be an allowlist of calls and this is not in it

puts File.read("/etc/os-release")
# =>
# NAME="Arch Linux"
# PRETTY_NAME="Arch Linux"
# ID=arch
# BUILD_ID=rolling
# ANSI_COLOR="38;2;23;147;209"
# HOME_URL="https://archlinux.org/"
# DOCUMENTATION_URL="https://wiki.archlinux.org/"
# SUPPORT_URL="https://bbs.archlinux.org/"
# BUG_REPORT_URL="https://bugs.archlinux.org/"
# LOGO=archlinux-logo

lib LibC
  struct UTSName
    sysname : Char[65]
    nodename : Char[65]
    release : Char[65]
    version : Char[65]
    machine : Char[65]
    domainname : Char[65]
  end

  fun uname(buf : UTSName*) : Int
end

buf = uninitialized LibC::UTSName
LibC.uname(pointerof(buf))
String.new(buf.sysname.to_unsafe)    # => "Linux"
String.new(buf.nodename.to_unsafe)   # => "playpen"
String.new(buf.release.to_unsafe)    # => "5.17.9-arch1-1"
String.new(buf.version.to_unsafe)    # => "#1 SMP PREEMPT Wed, 18 May 2022 17:30:11 +0000"
String.new(buf.machine.to_unsafe)    # => "x86_64"
String.new(buf.domainname.to_unsafe) # => "(none)"

This looks fairly new so OS version doesn't seem to be the culprit here.

Adjusted the filter, should work now.
For whatever reason this ends up calling dup(2) which for whatever other reason none of the existing training programs put on the allow list :shrug:

So should we dig into why this called dup(2)? It seems very odd.


Start running tests on AppVeyor

Fix #91

So It seems the tests fail the first time they are ran, but succeed the second time. The cause is the run_for command, upping the time from 0.5s to 10 makes it always succeed (which I'm not sure why, maybe the python libraries don't send signals if the sub-process has gone away).
Further looking into it, CTRL+C looks like it gets sent to everything, so python seems to also get a ctrl+c event.

@btrepp yeah, apparently you can use that CTRL_C signal only with os.kill. There's an excellent Stack Overflow answer about this, where there is at least one solution that works, so we might want to try that.
Feel free to push to this branch if you want to give it a shot :)
More context on this test: here we are testing that Spago cleans after itself when downloading stuff.
When installing it will, in parallel, create folders for the deps and run some git commands. If something goes wrong before the git commands are completed, it should remove the folder it created (because we assume that if the folder is there then the package is properly installed).
Now, we are simulating the "something goes wrong" condition with a ^C on Linux (this is an actual use case, as you might wish to stop the install while it runs), and we have to do it in such a short time that Spago has the time to create the directories but not to complete the git commands, and 0.5s is a good value for that.


Maven dockerfile plugin does not respect DOCKER_HOST 's ssh capabilities

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
Description
java.net.UnknownHostException when DOCKER_HOST is set to an ssh endpoint, making use of aliases in ~/.ssh/config
[Add feature/bug description here]
How to reproduce

Create a maven project that uses dockerfile-maven 1.4.10
configure docker to make use of a remote host for example by
** Adding this to ~/.ssh/config
Host devc
HostName <IP_ADDRESS>
IdentityFile ~/Box/keys/id_ecdsa
Port 22
User jonesn
** In environment export DOCKER_HOST=ssh://devc
** checking docker commands work - build, run an image

Now try and build the maven project with mvn clean deploy
An error will occur similar to:

[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (default) on project open-metadata-docker: Could not build image: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: java.net.UnknownHostException: devc: Unknown host devc -> [Help 1]

12:10 $ env | grep DOCKER
DOCKER_HOST=ssh://devc

[Add steps on how to reproduce this issue]
What do you expect
The docker build to work correctly.
[Describe what do you expect to happen]
What happened instead
Network/host not found error
[Describe the actual results]
See transcript above
Software:

docker version: [Add the output of docker version here, both client and server]

15:31 $ docker version
Client: Docker Engine - Community
 Version:           18.09.2
 API version:       1.39
 Go version:        go1.10.8
 Git commit:        6247962
 Built:             Sun Feb 10 04:12:39 2019
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          18.09.0
  API version:      1.39 (minimum version 1.12)
  Go version:       go1.10.4
  Git commit:       4d60db4
  Built:            Wed Nov  7 00:16:44 2018
  OS/Arch:          linux/amd64
  Experimental:     false
 Kubernetes:
  Version:          Unknown
  StackAPI:         Unknown

Spotify's dockerfile-maven version: [Add dockerfile-maven version here]
1.4.10

Full backtrace
[Paste full backtrace here]

NOTE. If DOCKER_HOST is unset - ie to use local docker daemon - no errors occur
I then tried changing ~/.ssh/config so that the name of the entry was the IP address
The result then was
[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (default) on project open-metadata-docker: Could not build image: java.util.concurrent.ExecutionException: com.spotify.docker.client.shaded.javax.ws.rs.ProcessingException: com.spotify.docker.client.shaded.org.apache.http.conn.HttpHostConnectException: Connect to <IP_ADDRESS>:2375 [/<IP_ADDRESS>] failed: Connection refused (Connection refused) -> [Help 1]
(and another similar full stack trace)
The implication is that the docker plugin is not respecting the functionality of DOCKER_HOST with respect to ssh configuration - which in my case I'm using primarily due to resource constraint to offload the IO/cpu intensive docker steps to a cloud based machine.

Posted more complete stack trace from original error at https://gist.github.com/1059280431d2c3f43dc92acb226b0a39

Not working yet

not working, can we reopen?

As an alternative I made a little script to work around this: https://github.com/bcoughlan/docker-ssh-bridge/
docker-ssh-bridge user@host -- mvn install


Migrate EXPORT to 7.3-preview

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of “no breaking changes
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Breaking Changes: the PR modifies an existing Preview protocol version to move capabilities that will not be finalized until a later version. As a result, the check identify these moves as breaking changes but the original protocol version was never final.

@herveyw-msft we can certainly override the breaking change flag from the CI based on that circumstance, but it looks like there are other failing CI checks that need to be addressed first.

@herveyw-msft we can certainly override the breaking change flag from the CI based on that circumstance, but it looks like there are other failing CI checks that need to be addressed first.

/azp run

/azp run

Please address the Required CI failures.

Please address the Required CI failures.

I realized that you also need to remove the export key operation.
/cc @Lusitanian

Fixed in the changes from a rebase and model validation updates.

I realized that you also need to remove the export key operation.
/cc @Lusitanian

Fixed in the changes from a rebase and model validation updates.


Support line breaks

Currently line breaks ("\") are not supported. Implementing that feature would strongly enhance django-latexify.

There is still nothing

The new release (v.0.3) now supports line breaks.
You can now add a new line by adding \newline.  For example:
{% latexify 'x = a + b \newline a = 1 \newline b = 2' math_block=True %}


Start adding zero-copy docs

Draft since this isn't yet complete - need to update examples and finish documenting new items, currently

Unrelated note: After this PR, definitely think it might be a good idea to pull Container, Seq, etc into their own module, to track these common 'container helpers'.

Currently recover_with fails, and two docs are TODO. On the other hand, I think it may be worth to merge now and fix those things later, since this change is very prone to bitrot

Do you think it's ready for merge?

I'm going to add at least basic documentation to the two TODO ones quick, then I think so

I'd call this PR ready to merge - there are one or two rough spots, but overall I think this improves the current state of zero-copy documentation.

Thanks! This is a big step forward :)


Templates for forms are not working

I saw someone previously asked how to use templates but when I tried to use myself to add a class to the error messages it didn't work.
The example given was:
public $helpers = [
    'Form' => [
        'className' => 'Bootstrap3.BootstrapFormHelper',
            'templates' => [
                'dateWidget' => '{{day}}{{month}}{{year}}{{hour}}{{minute}}{{second}}{{meridian}}'
            ]
    ]
];

so in my code:
public $helpers = [
    'Form' => [
        'className' => 'Bootstrap.BootstrapForm',
        'templates' => [
            'error' => '{{content}}'
        ],
    ],
];

but my error messages did not change. I still only have the class .help-block (which is not helpful for styling if you plan to use .help-block for information purposes in your form)

Hi,
It is currently not possible to have custom templates for formGroup, checkboxContainer, radioContainer submitContainer, label, and error.
I have just push an update where I added error-message class form the errors. I will try to correct the template problem in a future update but I think it will not be that easy because of the automatic management of horizontal forms...

This should be solved with https://github.com/Holt59/cakephp3-bootstrap-helpers/commit/e4fad5e81b64f4e6438ca5ef5a3245e77df1f77e, but be careful if you modify one of the mentioned template since they contained additional template variables that may break the helper if you forget them!


Google limits access to 7 days.

So every week i have to do the process over agen to get access to my calender.
Google limits token for 7 days, then you have to do it all over agen witch is frustrating.
I've googled about this issue, and no one seems to know anything about it.
why cant i have permanent access to my calender with gcalcli without having to reauthenticate every week?

Per https://github.com/insanum/gcalcli/issues/611 , if we can figure out how to get gcalcli to pass a redirect_uri parameter to the Python Google OAuth2 module, it should be possible to publish the app without Google review and have longer-lasting tokens. I also filed an Ubuntu bug report at https://bugs.launchpad.net/ubuntu/+source/python-oauth2client/+bug/1983216 since it appears upstream is no longer maintaining the relevant library https://github.com/googleapis/oauth2client/issues/317

For what it's worth, here is a fork where the deprecated oauth2client library has been replaced with google-auth. I just threw this at the problem.
I'm refraining from making it a PR for now, as it is untested, redirect_uri is hardcoded to localhost (which I don't like, and I'm not even sure if it is needed). This still doesn't fully solve the 7-day expiration issue, but hopefully paves the way to try the redirect_uri approach.

Went with this instead
to run
python3 timer.py 2023 09 15 19 25
#! /usr/bin/env python3
import time
import os
import sys
from datetime import date
import subprocess
import datetime
import threading
import requests
chat_id=       #Enter Telegramchat_id
TOKEN=       #Token
def start_timer():
year = int(sys.argv[1])
month = int(sys.argv[2])
day = int(sys.argv[3])
hour = int(sys.argv[4])
minute = int(sys.argv[5])
description = str(sys.argv[6]) #Currency
des2 = str(sys.argv[7]) #16x or 19x or 23x
date1 = str(sys.argv[8]) #date when occured
startTime = datetime.datetime(year, month, day, hour, minute)
print (" ~~> Telegram Alert is set for:{}".format(startTime))
while datetime.datetime.now() < startTime:
time.sleep(1)
print('Time's up')
url = f"
https://api.telegram.org/bot{TOKEN}/sendMessage?chat_id={chat_id}&text={description}
"
print(requests.get(url).json())
myTimerThread=threading.Thread(
target=start_timer,
name='myTimerThread')
myTimerThread.daemon = True
myTimerThread.start()
myTimerThread.join()
On Sun, Apr 9, 2023 at 7:32 PM Nephiel @.***> wrote:

For what it's worth, here is a fork https://github.com/Nephiel/gcalcli
where the deprecated oauth2client library has been replaced with
google-auth. I just threw this https://stackoverflow.com/a/52101480 at
the problem.
I'm refraining from making it a PR for now, as it is untested,
redirect_uri is hardcoded to localhost (which I don't like, and I'm not
even sure if it is needed). This still doesn't fully solve the 7-day
expiration issue, but hopefully paves the way to try the redirect_uri
approach.
—
Reply to this email directly, view it on GitHub
https://github.com/insanum/gcalcli/issues/634#issuecomment-1501177007,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIGQDF5LHB5T6EMTM7UMUOLXALXDLANCNFSM54TFBINQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

For what it's worth, here is a fork where the deprecated oauth2client library has been replaced with google-auth. I just threw this at the problem.

It does not seem to work:
Traceback (most recent call last):
  File "/usr/bin/gcalcli", line 11, in <module>
    load_entry_point('gcalcli==4.3.0', 'console_scripts', 'gcalcli')()
  File "/usr/lib/python3.6/site-packages/gcalcli/cli.py", line 152, in main
    gcal.AgendaQuery(start=parsed_args.start, end=parsed_args.end)
  File "/usr/lib/python3.6/site-packages/gcalcli/gcal.py", line 1212, in AgendaQuery
    return self._display_queried_events(start, end)
  File "/usr/lib/python3.6/site-packages/gcalcli/gcal.py", line 1156, in _display_queried_events
    event_list = self._search_for_events(start, end, search)
  File "/usr/lib/python3.6/site-packages/gcalcli/gcal.py", line 1105, in _search_for_events
    self.get_events()
  File "/usr/lib/python3.6/site-packages/gcalcli/gcal.py", line 179, in get_events
    return self.get_cal_service().events()
  File "/usr/lib/python3.6/site-packages/gcalcli/gcal.py", line 174, in get_cal_service
    credentials=self._google_auth())
  File "/usr/lib/python3.6/site-packages/gcalcli/gcal.py", line 143, in _google_auth
    credentials = pickle.load(gcalcli_oauth)
_pickle.UnpicklingError: invalid load key, '{'.

Also it seems to be using the no longer supported oob authentication type

Apparently the local server that is commented out needs to be used instead of the console flow

Thanks for the patch. It is not complete as is but with a little cleanup it does work well enough - see #677

Here is a PR which makes it work with the current code base.

PR is merged now. Hopefully that fixes it for you!


Harvest Festival's Food Trough and RFPR crash

I'm using Realistic First-Person Renderer 8.1.1, which is the last version.
When I'm trying to take in my hand the Food Trough, the game crashes.
The log refers to the RFPR, so it may not your problem, but if you know what's the difference between the trough and your other items, you'll may know what caused this.
http://paste.ee/p/nudtE
I had no problems any other items, and without RFPR it works right.

https://github.com/PenguinSquad/Harvest-Festival/issues/110

Sorry. :D


Add missed EAV pattern to readme.md file

title auto descriptive.

:+1: thank you! It'll be nice if you squash your commits to a single one for this minor change

thanks :+1:

Merged, thanks for the fix!


Error on init project

I trying to initialize new project with web manifest and get an error.
This is the command:
bubblewrap init --manifest=https://zuzu.prat.idf.il/manifest.json
Do you want Bubblewrap to install JDK?  Y
This is the error:
cli ERROR Server responded illegally with a redirect code but missing 'location' header
Thank you

Same issue for me

Can you provide details on the version? Is that on the version installed from NPM or from master on the repo?

Duplicate to #653

This should be fixed in v1.16.0. Please, re-open if the issue persists.


upgrade to docusaurus 2.1 and fix version mismatch

What type of PR is this:
/kind documentation
What does this PR do / why we need it:
There was a mismatch in docusaurus component versions, this can lead to unexpected errors.
While fixing this, I updated Docusaurus to the latest stable version.
Which issue(s) this PR fixes:

Fixes #
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

/lgtm

/approve


Only render "link account" dialogue for untrusted clients

for trusted clients keep previous behavior (always render standard
login screen)

Looks great! +1


Docker compose version is too old: 2.1

single kafka yml
version: '2.1'

It's only old if you're trying to use the new features of the Compose spec, which the file does not


Update 1.18 config.toml for release 1.21

Updated config.toml for release v1.21
Versions were updated based on latest patch releases
/hold until 1.21 release day

verify the patch versions
/lgtm


when i use weed scaffold -config=security      seaweedfs_2.77_linux

security.toml
when i use weed scaffold -config=security
It doesn't appear in  this
./security.toml
$HOME/.seaweedfs/security.toml
/etc/seaweedfs/security.toml
So I selected it and copied and pasted it
just like
[jwt.signing]
key = "blahblahblahblah"
expires_after_seconds = 300           # seconds

# jwt for read is only supported with master+volume setup. Filer does not support this mode.
[jwt.signing.read]
key = "chiputaobutuputaopi"
expires_after_seconds = 300           # seconds

# all grpc tls authentications are mutual
# the values for the following ca, cert, and key are paths to the PERM files.
# the host name is not checked, so the PERM files can be shared.
[grpc]
ca = "/usr/local/seaweedfs/SeaweedFSCA.crt"
# Set wildcard domain for enable TLS authentication by common names
allowed_wildcard_domain = "" # .mycompany.com

[grpc.volume]
cert = "/usr/local/seaweedfs/volume01.crt"
key = "/usr/local/seaweedfs/volume01.key"
allowed_commonNames = ""    # comma-separated SSL certificate common names

[grpc.master]
cert = "/usr/local/seaweedfs/master01.crt"
key = "/usr/local/seaweedfs/master01.key"
allowed_commonNames = ""    # comma-separated SSL certificate common names

[grpc.filer]
cert = "/usr/local/seaweedfs/filer01.crt"
key = "/usr/local/seaweedfs/filer01.key"
allowed_commonNames = ""    # comma-separated SSL certificate common names

[grpc.msg_broker]
cert = ""
key = ""
allowed_commonNames = ""    # comma-separated SSL certificate common names

# use this for any place needs a grpc client
# i.e., "weed backup|benchmark|filer.copy|filer.replicate|mount|s3|upload"
[grpc.client]
cert = "/usr/local/seaweedfs/client01.crt"
key = "/usr/local/seaweedfs/client01.key"

# volume server https options
# Note: work in progress!
#     this does not work with other clients, e.g., "weed filer|mount" etc, yet.
[https.client]
enabled = true
[https.volume]
cert = ""
key = ""

question
get   host:port/dir/assign
Whether I add a jwt.signing.key or not，the Authorization generated by its response can always successfully upload and download operations
SO,What is the meaning and operation of jwt.signing.key

see https://github.com/chrislusf/seaweedfs/wiki/Security-Overview#how-jwt-based-access-control-works

see https://github.com/chrislusf/seaweedfs/wiki/Security-Overview#how-jwt-based-access-control-works

the master will use the jwt.signing.key to generate and sign a JWT, and set it to response header Authorization.
So I can use it without setting a key in the header. Then, can anyone know the service address to generate a token and upload and download files？

the volume server will check the signing key.


removed extraneous stylesheet from formEmail, formPassword, formZipCode

Description of changes
Removed stylesheet from fromEmail, formPassword, and formZipCode component directory since they were not being imported from respected component.
Issue Resolved
Fixes #303

Thanks!


Full upsert to partial upsert

When using the upsert functionality, it is possible to change the table config from full upsert to partial upsert. But when you make this change, the partial upsert config isn't picked up until you restart the server.
I think this is deliberate as we only create a new TableDataManager if one isn't already designed, otherwise, it uses one that was created for the first segment added/replaced on that server.
To me, this behaviour doesn't seem intuitive. I would expect one of the following to apply:

We aren't allowed to change the upsert functionality in this way and table validation should reject our attempts to do so.
We should create a new TableDataManager when a new segment is being added/replaced if we detect a change has been made to the table config.

But which of these should it be, or is there another option?

Thanks @mneedham for putting it here.
Related discussion: https://apache-pinot.slack.com/archives/C01H1S9J5BJ/p1685437705110729

Similar to segment reload, we should introduce the table reload operation, which re-create the TableDataManager and replace the existing one atomically


Is it possible to retrieve "Registration Name" and "Resource Group" from this command?

Hello,
We are looking to leverage this command to retrieve the registration name from multiple scale units. Registration Name is found on the Properties page of the region on the Azure Stack Admin Portal. This command seems to retrieve that information except for Registration Name or the corresponding Resource Group which should be "azurestack" found on the Billing Tenant.
Thanks,
Chris

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6470df55-c1d6-d5d7-86f8-84bdd4fc9091
Version Independent ID: b0e87e42-5957-2b7f-ecee-56f5998836db
Content: Get-AzsInfrastructureLocation (Azs.Fabric.Admin)
Content Source: azurestackps-1.8.0/Azs.Fabric.Admin/Get-AzsInfrastructureLocation.md
Service: azure-powershell
GitHub Login: @mattbriggs
Microsoft Alias: mattbriggs

@mahoncj Thank you for the feedback!  We are investigating this and will get back to you shortly.

@mahoncj Thanks. I have a question to the technical team about the place cmdlet to find the info in your context. Thanks! Matt

The customer can get the azureRegistrationResourceIdentifier by logging into Azure Stack:
$envName = "AzureStackAdminReg"
Add-AzureRmEnvironment -Name $envName -ARMEndpoint $AdminResourceManager | Out-Null
$loginParams = @{
Environment     = $envName
Tenant          = $aadTenantID
Subscription    = 'Default Provider Subscription'
Credential      = $AzureStackAdminCredential
}
Login-AzureRMAccount @loginParams
$subscription = (Get-AzureRmContext).Subscription.Id
$regPropertiesAzureStack = (Get-AzureRmResource -ResourceId "/subscriptions/${subscription}/resourceGroups/azurestack-activation/providers/Microsoft.AzureBridge.Admin/activations/default").Properties
$azureRegResIden = $regPropertiesAzureStack.azureRegistrationResourceIdentifier
$strArr = $azureRegResIden.Split('/')
$azureSubscription = $strArr[$strArr.IndexOf('subscriptions')+1]
@mahoncj
You can then use azureRegistrationResourceIdentifier to retrieve registration info like RegistrationName and ResourceGroupName by logging into AzureCloud
Login-AzureRmAccount -Subscription $azureSubscription -Environment 'AzureCloud'
$regResourceAzure = Get-AzureRmResource -ResourceId $azureRegResIden
$registrationName = $regResourceAzure.Name
$resourceGroupName = $regResourceAzure.ResourceGroupName
$resourceGroup = Get-AzureRmResourceGroup -Name $resourceGroupName
$resourceGroupLocation = $resourceGroup.Location
$billingModel = $regResourceAzure.Properties.billingModel

#in-progress

@mahoncj  Thanks again for your comment. I'm going to close this now, but you have additional questions please let me know

#please-close

@mattbriggs Thank you for the above code block! That's exactly what we're after. Very much appreciated.

#please-close


change egress router to allow user to extend the router handler

allow router hander to be extend.
tuning ingress-proxy hanlder

 change egress router to allow user to extend the router handler light-4j master


MapView annotation requiring custom icon fails with: Image source size {128, 128} does not match loaded image size {0, 0}

react-native version: 0.27.1
I was following mapview example to use custom annotation icon.
<MapView
  style={styles.map}
  annotations={[
    {title: 'Thumbs Up!',
    latitude: 48.3124827,
    longitude: 18.0182664,
    image: require('image!uie_thumb_big')}
  ]}
/>

But I get error  Image source size {128, 128} does not match loaded image size {0, 0}
When I use  image: require('./uie_thumb_big')}, it runs fine.

Please use Leland Richardson's react-native-maps as it is more feature-complete than our internal implementation.

@facebook-github-bot bugfix

Hey @mauron85, we're a small team and rely on the community to fix issues that don't affect fb apps. If you're sure this is a bug can you send a pull request with a fix?

@facebook-github-bot close


Correction/adding more clarity to definition of Remote User

https://github.com/MicrosoftDocs/sql-docs/issues/6966

@nachiketrss : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks @nachiketrss for submitting this PR! Your commit will be merged and this article update is in flight. After the updated article is published, GitHub will list you as an article contributor. Thanks again for this feedback, your suggestions help improve our documentation.
#sign-off


subtract of BDay results in days instead of pd.Timestamp

Code Snippet
from pandas.tseries.offsets import BDay
import datetime

(datetime.date(2023,1,1) - BDay(7)).date() # this line reports `.date()` is not a member of `date`, but actually it's a `pd.Timestamp` and the code works, only Pylance in VSCode has a false positive

Pylance is working correctly here. We include the latest pandas-stubs in every Pylance release. In pandas-stubs, BDay inherits (indirectly) from BaseOffset which has the following __rsub__ overload:
_DatetimeT = TypeVar("_DatetimeT", bound=date)

# some lines removed for clarity

@overload
def __rsub__(self, other: _DatetimeT) -> _DatetimeT: ...

date doesn't have a __sub__ overload that handles pandas types (which makes sense since date comes from the stdlib), so we look for a matching __rsub__ and find this one which tells us that the result of a "date - BDay" subtraction operation will be a date.
If you feel that the stubs are incorrect, please file an issue on pandas-stubs.

@debonte: indeed, the stub seems to be incorrect. Thanks for pointing me to the right direction.


The pr.txt files does not match the curve in the paper

Hi,
I'm trying to reproduce the PR curves in the paper. However I find that the pr.txt files in the repository does not match the curves reported in the paper (PCNN+ATT for example).
Are these files generated by models that are not fully trained?
Can you provide pr.txt files that can reproduce curves in the paper?
Much appreciated.

I have the same questions. pr-1.txt has 2000 lines, shouldn't it have more than ~96k lines (more than one prediction for each entity pair in test file). I changed line 237 of test.h to {for (int i=0; i<int(aa.size()); i++)} which results in ~96k*52 lines in pr.txt. But, the graph still does not match.
It will be very helpful if you could provide us with the right script to generate the PR curve.
Thanks

I have updated the test.h in PCNN+ATT. And the original pr.txt and models of our experiments can be downloaded in https://pan.baidu.com/s/1bo0fgXx.

Thank you! @Mrlyk423
This helps a lot!

Thanks for your response


Sim race condition

Sid and I think the race condition and deadlock is fixed.
Quality Assurance Checklist
To make reviews more efficient, please make sure the software feature meets the following standards and check everything off that meets the quality check. Once everything has been checked, the assigned reviewers will begin the review process. Edit this description to check off the list.
There are exceptions with all guidelines. As long as your decisions are justified, then you are good! Contact the reviewers or the leads about any exceptions.
Requirements

[ ] Followed Coding Style Guide
[ ] Code Build checks pass
[ ] No merge conflicts
[ ] Software feature has test associated with it.
[ ] Software feature has documentation for it updated.
[ ] If applicable, does software feature have simulation test associated with it (.json & out.json file)
[ ] Test provides useful information and uses relevant data to accurately represent BPS

NOTE: If test file already exists, use that one

[ ] 2 Members of the team have already reviewed my PR

NOTE: Approver will not look at PR if 2 other members haven't reviewed first

[ ] Did you Have Fun?

Things to Consider

[ ] Even if the above are checked, is this the best way of writing my code?

It's possible to write code that works, but are there ways to make code more efficient?

The mutexes should be around the instruction write(simulatorLog, msg, strlen(msg));' line in 'Simulator.c' .Going on what Manthan said about using non micrium locks one way is using the pthreads. so you can use pthread_mutex_lockandpthread_mutex_unlock. Some example code is in the cpu_c.c` in the RTOS submodule. Not sure if that works, i think @ClarkPoon knows more abt them than me.

The mutexes should be around the instruction write(simulatorLog, msg, strlen(msg)); line in Simulator.c .Going on what Manthan said about using non micrium locks one way is using the pthreads. so you can use pthread_mutex_lock and pthread_mutex_unlock. Some example code is in the cpu_c.c in the RTOS submodule. Not sure if that works, i think @ClarkPoon knows more abt them than me.

pthreads should work but I'll ask around and look into it

@ray4477 The race condition you are talking about does exist but is being dealt with in another PR. The issue that @connorl309 was dealing with was multiple places in the code transitioning to a new state at the same time (thereby accidentally skipping states and not properly testing the code) which is why he was protecting the states variable. What I am not sure of is whether a mutex around it actually fixes this issue.

please fill out qac and request more reviewers


crash on android Q

hi calligraphy crash on android Q please check it
this part of code make crash
 @Override
    protected void attachBaseContext(Context newBase) {
        super.attachBaseContext(ViewPumpContextWrapper.wrap(newBase));
    }

Dupe of #33

@jbarr21 so, is there any way to fix this?


Fixed header "Content-Length: 0"

The header "Content-Length: 0" causes problems in Firefox and curl (curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1) or Firefox doesn't download the content).
The "backends.Backend.Length()" function can only return 0, so maybe it can be removed completely.

@flottes,  hi how did you trigger this error?

The error occurs when the upstream server responds without a "Content-Length" header. The cache server then adds "Content-Length: 0", which causes the problem.


Deselecting pre-selected group

Hello,
Before I was not using the group-select part of Vue-Multiselect, but it is really useful. Up to now I have used v-model to preselect values, since it worked just fine for my application. I do not know what the preferred method for preselecting options is.
However, I am now trying to implement groups as well, including preselect. Deselecting preselected groups does not seem to work though, see JSFiddle.
Looking at the events, it can be seen that the elements that are removed are added again (if I understand correctly).
Is this not working due to the way I am preselecting options? And, if so, what is the proper way to preselect options in Vue-Multiselect?
Thank you in advance,
Jaap

Using a work-around (Using the @select and @remove events to add and remove elements to a secondary array) I have been able to also remove objects, though the solution is not exactly pretty.
I have got it working for now, but I'm still wondering is this is the intended solution?

This looks like a bug. It should work with the way you’re preselecting them. Please use the workaroud and I will try to fix this during the weekend. Thanks for reporting!

U can make it with computed property. Here is the code JSFiddle.
The array selectedValues at start needs to be same as the value array. And i added underscore.js.

So, there is a workaround but it was determined by @shentao up above that it should be fixed....why the decision to just not fix it and force the workaround?

Any update for this?

Any workaround other than underscore js on this issue?


Add missing includes for musl libc

IODash currently fails to build on musl; I found it while packaging ydotool for Void Linux...
see https://github.com/void-linux/void-packages/pull/31237

This also fixes building on Alpine Linux (which also uses musl libc)


How much time is required

Hi ,I wonder how much time is required when I use one-shot guidance on A100 GPU

That depends on the "max_train_steps" you select. Lower values such as 50 or 100 require several minutes. But some concepts may need large training steps such as 500, and this takes about 20-30 minutes. So you can start from a low training step, if the results are unsatisfactory, you can raise it.


[Languages] Hashing in C++ using std::hash

Proposed title of article
Hashing in C++ using std::hash
Proposed article introduction
To generate a hash of any C++ object, we will use the standard C++ library's (std:hash) inherent support for hashing. We unknowingly utilize a hash function whenever we use an associative container. Key-value pairs used in map, multimap, unordered map, and other data structures are mapped to one another. The hash function and hashcode creation form the foundation of mapping. There are no arguments or initialization values required to create an object in the hash class by default. The hash value of the argument supplied to it is returned by this method. The value stays the same if the argument doesn't.
In this tutorial, we will discuss in details about Hashing in C++ using std::hash and how we can implement it in programming.
Key takeaways
By the end of this tutorial the reader will understand the following concepts.

How to create an object in std::hash?
Character hashing
String hashing
Integer hashing
Vector hashing
Hashing and collision

Article quality
So that it adds value beyond what is already in the official blogs and documentation, I plan on making this article unique and beginner-friendly. To aid the rest of EngEd, this article will go beyond a basic explanation and give a step-by-step approach.
References
N/A

Good afternoon and thank you for submitting your topic suggestion.
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.


Java 16.9 : Suspending, resuming and stopping threads

Description
Add audio, documentation, and video regarding the Suspending, resuming and stopping threads
Location of File to be added The files should be added inside the Suspending, resuming and stopping threads which will be inside Multithreaded Programming folder which will be inside of Java folder. If the folder is not present, create the folder with this exact name.

The documentation file can be in the .md/.py/.ipynb format.
Audio should be in .mp3 format and to be submitted through a Google drive link.
Video can be in any format and should be submitted through a Google Drive link.

Note:
You are required to comment with \assign CONTENT_TYPE, so that other content types can be created at the same time. Failing to comment in the above manner will lead to the removal of assignment from the issue even if the bot assigns. You are required to do a PR within 7 days otherwise you will be unassigned and others will be assigned. Issues will be assigned on a first come first serve basis.
Domain
Java_Domain
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[x]    I follow Contributing Guidelines & Code of conduct of this project.

/assign documentation

/assign documentation @AkMo3 @garvitraj

/assign video

\assign documentation
@AkMo3 @garvitraj please assign

@jaya6400 You have been assigned video

ok mentor

/assign audio

@garvitraj can you please assign me the issue


Item Route

create new item
fetch an item
fetch all item
update an item
delete an item

in User route #7 PR

in User route #7 PR


iOS build: Replace %20 with space in config script

CLA: trivial
Fixes building iOS using ./config.

How can I get to make my contributions on this repository?

Merged
master:
53fd220c8fc953b603dd13257d6b2e2d1e7eb864 iOS build: Replace %20 with space in config script
1.1.1:
7b031c206228ae1f48bdd9e271fc101f91f817e1 iOS build: Replace %20 with space in config script


Vehicle behaviour on Gradient Road

Hello All,
We encountered trembling behavior in vehicles on Gradient road, Whether it is Carla vehicle dynamic issue or Gradient roads are not supported in Carla? Could you please help us regarding this issue.
Here with we have attached movie file for your reference
Tested platform:
Carla: <IP_ADDRESS>
Linux: Ubuntu 18.04 LTS
Python 3.7
Thanks in advance!
https://user-images.githubusercontent.com/65219753/106630096-875b9c00-65a1-11eb-8db3-54808ed3a37c.mp4

We have noticed similar 'bouncing' when using OpenGL in CARLA 0.9.8 and 0.9.11, but switching to -vulkan from -opengl seemed to make it go away.  What rendering options were you using?

we have noticed similar bouncing issue when switching over to -vulkan from -opengl in carla <IP_ADDRESS>
https://user-images.githubusercontent.com/65219753/106723980-b4ee2700-662d-11eb-82f4-1850b409f143.mp4

Hi,
It says that the video can't be played because the file is corrupt. Could you upload them again and also give more information about what you are executing?

Hi,
We are using a road profile with certain elevation angle and trying to run the default carla vehicle in autopilot mode. We could observe normal motion in the straight road but once the vehicle enters  the road with elevated profile we could notice bouncy movement during its motion. we observed similar behaviour even in curved road with elevation angle. what could be the reason behind this weird behaviour of the vehicle in the elevated road? herewith we are attaching the video again
https://user-images.githubusercontent.com/65219753/106914838-69ba3e00-672b-11eb-9403-95e6ea90c253.mp4

Hi @MS012086, how are you generating the map? Are you using Roadrunner? How long is the road?
With Gradient roads I assume that you mean the shape of the road cross section, I suppose that roadrunner of the software you are using could create small bumps in the road if this is not perfectly aligned, causing the car to have this weird motion. Can you verify that the road is completely flat and without sudden height differences?

Hi @Axel1092 , Yes, We are using roadrunner tool for map generation. The road is about 5 km long. We have checked the road profile in roadrunner and could  see that the height of the road increase gradually without any sudden difference. The road is flat and only its height increases gradually after a certain distance . Herewith attaching a screenshot from roadrunner.

@MS012086 sorry for the late response. I can only think that this issue is due to small variations in the road geometry at the time of exporting. Carla has no support for superelevation or crossfall (non flat cross section in the road). Perhaps roadrunner is exporting additional objects as well. Also, in the parts where the vehicle has the strange behavior we can see this weird noise in the image which leads me to think that there is an issue with the geometry of the road.

Hi @Axel1092 ,
Thank you very much for your information.
We have removed additional objects( Guardrail and surrounding landscape) from road profile.
And now we could not visualize the bouncing behavior on the road.
Even after removing the additional objects, we could see the noise in the image but it is not affecting the vehicle behavior.

We have been trying to debug a very similar situation - a flat three lane road which is 5km - with no elevation change. If terrain is present - vehicles appear to collide with invisible humps positioned on the road. Removing the terrain object (which surrounds the road) fixes this behavior.

@Axel1092 - Here is an video that shows the difference/problem. Note the vehicles appear to be colliding with some kind of bumps along the road when terrain object is active. The only difference between the first and second part of the video is the deletion of the terrain mesh from the level.
https://user-images.githubusercontent.com/16140583/111001829-5b1e0280-8339-11eb-8f2b-54911570d564.mp4

A workaround - is to import a generic/flat DEM into RoadRunner and apply it to your scene. This changes the triangulation of the terrain mesh before it is exported, which in our case fixed the problem.

It would seem that roadrunner is creating some geometry under the road that is causing the cars to move like that. Perhaps the terrain is not flat under the road and it overlaps with the road itself?

I also observed the same behavior in Carla. The car suddenly jumps at some location on the road mesh. The mesh appears to be smooth (verified in 3D modeling viewers) and still the cars jumps, front wheels first followed by rear wheels as if it hit something. This behavior is only observed with cars moving on the road. Other objects like rolling cylinder/sphere in the same place of the road does not hit anything. When I changed the road mesh to the procedural mesh generated from Carla, the car does not jump and follows smoothly. Can anyone suggest what is going wrong here?

Are you using road runner to create scenes? Do those scenes have bridges in
them?
On Tue, Mar 19, 2024 at 12:05 AM HariKrishnaPadala @.***>
wrote:

I also observed the same behavior in Carla. The car suddenly jumps at some
location on the road mesh. The mesh appears to be smooth (verified in 3D
modeling viewers) and still the cars jumps, front wheels first followed by
rear wheels as if it hit something. This behavior is only observed with
cars moving on the road. Other objects like rolling cylinder/sphere in the
same place of the road does not hit anything. When I changed the road mesh
to the procedural mesh generated from Carla, the car does not jump and
follows smoothly. Can anyone suggest what is going wrong here?
—
Reply to this email directly, view it on GitHub
https://github.com/carla-simulator/carla/issues/3853#issuecomment-2006018102,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3ESJ72UTXHM5DGN4TL7VLYY7PSDAVCNFSM4W67EQUKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBQGYYDCOBRGAZA
.
You are receiving this because you commented.Message ID:
@.***>

Not Roadrunner. I am trying to use the procedural mesh from CARLA. The scene does not have bridge, just a normal road intersection. The car jumps mainly when it is trying to cross a intersection, even though the intersection appears to be smooth.


Error: No instrument is found in the subscription file. Please check the file path and the content of the subscription file

disregard,   I figured it out

@sparcusa hi! How did you solve this problem?

I think you can follow the following steps to diagnose it:

Input the full/absolute path rather than relative path first. For example, even though you think your file is in the local directory, try to put --config /home/yourname/your/path/instruments.ini first. If it works fine, then your path is incorrect.

If you have input your absolute path but still find the same error, please try to copy one instrument from the sample file into your one first.


Tell us about your request

Tell us about your request
Currently a Business License customer needs to have each associate login with an email address to trigger the SSO flow.  Not a big deal, but more documentation and places for error.  A verified domain admin can tell everyone to enter in<EMAIL_ADDRESS>and if example.com is verified it will redirect to the configured IdP and the claims returned will determine what DockerID you are connected to.  The input email beyond domain has no effect on what you will login as.
Just provide an additional endpoint for https://login.docker.com/u/login/sso?domain=example.com or something of the like that issues the state token (couldn't figure out how to issue that while sending the username query param) and goes directly to the IdP.
Which service(s) is this request for?
Docker Hub
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Just give folks one URL (and possibly an internal vanity) to login to Docker Hub when needed.  They can bookmark it and not worry about using a personal id or dockerid vs email.
Are you currently working around the issue?
Just documentation for folks is what is there.
Additional context
Docker Desktop itself won't know by default, but possibly the use of registry.json can trigger it to use the SSO endpoint and avoid prompting for the password.  This could also be in a settings file or some other installer argument.
Originally posted by @byjrack in https://github.com/docker/roadmap/issues/375

Is this related to FirebaseUI? If not, please close this and track the original issue posted on docker roadmap.


Update configure-close-confirmation-window.md

Changed widow to window.

Hi @acolum,
Thanks for notifying the error. I have incorporated your feedback in the topic. You will see the changes in a couple of days.
Hence, closing the PR.
Expecting lot more feedback that can enahnce the customer experience.
Thanks and regards,
Karthik

The changes are live.


Suggestion : Tilemap Node

Godot version:

Godot 3.1
OS/device including version:

Issue description:

I can't use the GUI to change the position of a tilemap node, I have to manually do it by changing the numbers. Please add that feature, it just keeps drawing tiles when I want to move it.
Steps to reproduce:
Create a tilemap
Try to change its position by the GUI move tool.
Minimal reproduction project:

I think it's better this way cause changing the position of TileMap can cause problems if you are using multiple tilemaps, so it stops anyone from messing with it.
I don't see a reason so as to why there should be any need for it.

You can use the GUI. Move the cursor to a number, then Ctrl and mouse left click and move left and right instead of typing numbers.

I think allowing movement of the tilemap (and perhaps hiding the grid and to-be-placed tile) when the move tool is selected might be a useful addition.
Same for the rotate and maybe scale tools.


Fix histogram pool poisoning bug chunkenc.Iterator

Backport of #14605
Changelog:
* [BUGFIX] PromQL: fix native histograms getting corrupted due to vector selector bug in range queries.

This is against main, not against the 2.54 release branch. I guess the intention was to create this against the latter?


Add deck to papermill plugin task

TL;DR
This PR modifies the papermill plugin so that, if render_deck=True is passed to init, the rendered output html is inserted as a flyte deck.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[x] Code documentation added
[x] Any pending items have an associated Issue

Complete description
This PR modifies the papermill plugin so that, if a kwarg render_deck is passed, the flyte deck is added automatically, without need for a follow up task. The render_deck kwarg was used to ensure backwards compatibility, by default, the behaviour of the papermill plugin won't be changed (i.e., this deck support is opt-in).
Note that this won't happen for cached execution, there is an open issue out for fixing flyte decks for cached execution.
I tested this change by installing this branch of flytekit into a container and registering one of our company's test notebook tasks, and running it. It gets a deck as intended:

Not 100% happy with how I tested this plugin. Since the unit tests use local execution, the deck/context functionality I think isn't getting used. Let me know if there is a better way to do test this.
Tracking Issue
n/a (can open an issue if you like, JFDI'd this after discussing with Ketan here)
Follow-up issue
NA

Did a quick force push to my branch to --signoff in a rebase.


Create mergesort.cpp

What type of PR is this? (check all applicable)

[ ] 🚀 Added Name
[ ] ✨ Feature
[ ] 🌟 stared the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[x] 🚩 Other

Description
Add Link of GitHub Profile

#4186 mergesort


Relative to root?

It says that the git path is relative to root. Root according to my understanding, is the top level directory from which pages are served. If so, the site's sources live in the public page. Isn't that like saying (using hugo as an example):
hugo -d .    etc...
instead of hugo -d public    etc...??
generating the html in the same directory.
Please clarify.

Yes if you need to clone in the same directory, use . as clone path.

body p { margin-bottom: 0cm; margin-top: 0pt; }

That's nice. Is it safe to assume then that this can be taken
further, say
{
  root /var/www/srv/site1
  git site1 {
    path ../../src
  }
}

directory site1 under /var/www/srv will have to be created manually.
Caddy gives an initial warning that /var/www/srv/site1 does not
exist (yet). Html will be generated into and served from
/var/www/srv/site1 from the source tree (given by the "path"
directive) residing at /var/www/src/site1. Did I get that right.
Wouldn't uncoupling the source path from the root would add
flexibility?

On 27/1/16 17:07, Abiola Ibrahim wrote:

  Yes if you need to clone in the same directory, use .
    as clone path.
  —
    Reply to this email directly or view
      it on GitHub.

Yeah, that works too.
Thanks.