Fire change event without making an actual change to file

I am using this lib to run individual tests when they themselves change or to run the whole test suite if certain files in the project change.
What I am doing sometimes is adding comments to files ('//') and then saving the file, just to get the watcher 'change' events to fire, so my tests run on demand, but that adds unnecessary comments to files and eventually they will end up in source control which is bad.
Is there some keystrokes to use to fire a change event somehow if a file on the filesystem hasn't experience a change in its contents?

const watcher = chokidar.watch('dir')
watcher.emit('change', 'filepath')

that should do the trick

thanks but I meant not programmatically so much - I meant via some
keystrokes - which somehow change file without changing its contents - is
there some recommend way to do that? otherwise maybe could use some sort of
stdin thing and then use the simple methodology you described.
On Oct 22, 2016 5:32 PM, "Paul Miller"<EMAIL_ADDRESS>wrote:

const watcher = chokidar.watch('dir')
watcher.emit('change', 'filepath')
that should do the trick
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/paulmillr/chokidar/issues/543#issuecomment-255562313,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKn56JNJI6nus9GhLo-mgBF1_D5wN65Eks5q2qsHgaJpZM4KdvSV
.

Like touch?

maybe, yeah, would that fire a change event in this library? Or maybe a 'touch' event?

There is no touch event in chokidar. It will fire a change event when you touch a file on POSIX platforms

ok good to know!

works for me, I guess it would be interesting for the docs to document would kind of low level events the library hooks into. I frankly don't know which lower level events "change" events originate from.


[BUG] Cluster registration URL is not shown

Reproduce:
Install Rancher v2.10.0-rc3
Install Harvester UI plugin
Visit "Virtualization Management" page
Click "Import Existing" button to import existing Harvester cluster
No registration URL visible. Importing Harvester cluster impossible

I can reproduce this issue using harvester-ui-extension v1.0.1. cc @torchiaf
Using v1.0.0 is fine.
The error reported after creating cluster registration endpoint.
Error in fetch(): Error: Unknown schema for type: clusterregistrationtoken

Testing with rancher-v2.10-rc4 image with harvester-ui-extension v1.0.0 (branch : gh-pages),  the registration URL is succesfully show up.

@m-ildefons could you try again using harvester-ui-extension gh-pages branch ?

Hi Andy,
with v2.10.0-rc4 it works indeed as expected.
I'll close this issue then, since there is nothing to be done.


Replace fanpool with fixed worker pool and client write queues

This PR addresses the issues highlighted in #150 and #149.
In particular:

Replaces the FanPool with a basic fixed-size worker pool.
Client writes are now queued in packet channels per client. Instead of writing directly to the client, messages are added to the channels, which are then ranged by each client and written out in FIFO order.
A lock has been added to NextPacketID.
A mutex and lock has been added to Particle (topics), as I detected a race condition in my testing.

Interestingly, it improved the benchmark statistics, and in some cases considerably (see diff of readme).
It is an operational proof-of-concept, in as much as it hasn't been tested on production, however, it passes PAHO reliably, and test coverage is maintained and passing. There may be improvements we can make to this code.
@thedevop - if could you look this over and give it a test, I would be very appreciative! Please let me know what you think.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

79 of 80 (98.75%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 98.597%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

server.go
25
26
96.15%

Files with Coverage Reduction
New Missed Lines
%

server.go
3
99.62%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
5129

Relevant Lines:
5202

💛  - Coveralls

@mochi-co , few feedbacks:

Given each client has a buffered channel to receive writes (write chan). Is it better to have:

publishClient -> fixedPool (process/fan out to subscribers) -> subscriberWriteChan or
publishClient (process/fan out to subscribers) -> subscriberWriteChan
Other than some lock contentions, everything should be non-blocking and process quickly.

One of the goal is not to prevent a slow receiving subscriber hold up publishing to other subscribers, so sending to the write chan needs to be non-blocking using select.
Potential Inflight issues (address separately from this PR?)

Should there be a limit to max inflight msgs as well?
Have you considered using a tree instead of a map so order can be retained?
For QoS > 0, if the msg is dropped due to write chan full, then inflight needs to removed (or not set in the first place)

@mochi-co , few feedbacks:

Given each client has a buffered channel to receive writes (write chan). Is it better to have:

publishClient -> fixedPool (process/fan out to subscribers) -> subscriberWriteChan or
publishClient (process/fan out to subscribers) -> subscriberWriteChan
Other than some lock contentions, everything should be non-blocking and process quickly. In fact, most of the s.publishToClient can be done by the client write routine.

My concern with the second approach is that if Client A is publishing to subscribers of Topic, without an intermediary (pool) there's a possibility of blocking subsequent reads for Client A. Additionally, the hooks involved in this process are blocking, so in cases where a hook such as persistence is used, there could be a significant delay before these subsequent reads can occur.

One of the goal is to prevent a slow receiving subscriber hold up publishing to other subscribers, so sending to the write chan needs to be non-blocking using select.

I'm not 100% certain what you mean in this case - could you elaborate?

Potential Inflight issues (address separately from this PR?)

Should there be a limit to max inflight msgs as well?

Inflights are currently limited by ReceiveMaximum on the client and server side. Is this what you mean?

Have you considered using a tree instead of a map so order can be retained?

I did consider this, but it becomes harder to select and delete/modify inflights by id. Currently the inflight map is simply sorted by created date before return. The alternative requires iterating through each inflight for any select/update/delete by id, and I wasn't able to determine a clean solution that performed significantly better than the existing map+output sort approach (also lock contention became an issue during iterations on larger datasets). As always, open to ideas, however.

For QoS > 0, if the msg is dropped due to write chan full, then inflight needs to removed (or not set in the first place)

Not 100% sure about this. I would expect that a dropped message would is the same as a network disruption - the QoS packet delivery should be retried when the client reconnects. As long as the QoS flow quota has not been exhausted, we should we not continue to queue inflights?
Thank you very much for your time! Look forward to hearing your (and anyone else's) thoughts! 🙂

Given each client has a buffered channel to receive writes (write chan). Is it better to have:

publishClient -> fixedPool (process/fan out to subscribers) -> subscriberWriteChan or
publishClient (process/fan out to subscribers) -> subscriberWriteChan
Other than some lock contentions, everything should be non-blocking and process quickly. In fact, most of the s.publishToClient can be done by the client write routine.

My concern with the second approach is that if Client A is publishing to subscribers of Topic, without an intermediary (pool) there's a possibility of blocking subsequent reads for Client A. Additionally, the hooks involved in this process are blocking, so in cases where a hook such as persistence is used, there could be a significant delay before these subsequent reads can occur.

From publishToSubscribers to publishToClient, the only hook is OnSelectSubscribers. If publishToClient is handled by client write routine, it would be behind a buffer channel and should offer the same level of protection as the fixed pool.

2. One of the goal is to prevent a slow receiving subscriber hold up publishing to other subscribers, so sending to the write chan needs to be non-blocking using select.

I'm not 100% certain what you mean in this case - could you elaborate?

Currently in publishToClient, send to cl.State.outbound is a blocking operation, it will not drop message to slow receiving subscriber per discussed. This can be changed to below so it's non-blocking:
	select {
	case cl.State.outbound <- out:
		atomic.AddInt32(&cl.State.outboundQty, 1)
	default:
		// call drop hook?
	}

3. Potential Inflight issues (address separately from this PR?)
1. Should there be a limit to max inflight msgs as well?

Inflights are currently limited by ReceiveMaximum on the client and server side. Is this what you mean?

The following will directly add a message to inflight without any constraints, did I miss some other checks?
https://github.com/mochi-co/mqtt/blob/a8c9bdc48beffe3107b1bc4b8684639c3c7b1c5c/server.go#L836

3. For QoS > 0, if the msg is dropped due to write chan full, then inflight needs to removed (or not set in the first place)

Not 100% sure about this. I would expect that a dropped message would is the same as a network disruption - the QoS packet delivery should be retried when the client reconnects. As long as the QoS flow quota has not been exhausted, we should we not continue to queue inflights?

I was referring to intentionally dropping messages due to the subscriber is slow at receiving. Since subscriber was skipped due to write chan full, it should not exist in inflight neither.

From publishToSubscribers to publishToClient, the only hook is OnSelectSubscribers. If publishToClient is handled by client write routine, it would be behind a buffer channel and should offer the same level of protection as the fixed pool.

Ah, this makes me think we were talking about different things. Are you suggesting moving the enqueue from (for example):
s.pool.Enqueue(func() {
    s.publishToSubscribers(pk)
})

to
for id, subs := range subscribers.Subscriptions {
   if cl, ok := s.Clients.Get(id); ok {
       s.pool.Enqueue(func() {
            _, err := s.publishToClient(cl, subs, pk)
	}
    }
}

or are you suggesting to remove the fixed pool entirely?

This can be changed to below so it's non-blocking:

This is very interesting, I've not seen this done for channel writes before.
Is this in place of the following code (apologies, I don't have the ability to test is right now):
if atomic.LoadInt32(&cl.State.outboundQty) >= s.Options.Capabilities.MaximumClientWritesPending {
    return out, packets.ErrPendingClientWritesExceeded
}
cl.State.outbound <- out
atomic.AddInt32(&cl.State.outboundQty, 1)

becomes
select {
    case cl.State.outbound <- out:
        atomic.AddInt32(&cl.State.outboundQty, 1)
    default:
        cl.ops.hooks.OnPublishDropped(cl, pk) // perhaps new hook?
        return out, packets.ErrPendingClientWritesExceeded
}

cl.ops.hooks.OnQosDropped(cl, pk) should probably continue to only be used for inflight messages when they are dropped due to message expiry or clearing. This raises a question about renaming OnQosDropped to OnQosExpired for clarity.

The following will directly add a message to inflight without any constraints, did I miss some other checks?

I see now what you are saying. The quota system restricts the number of messages that are 'inflight' but it does not restrict the number of messages that can be added to a client inflight queue, which is limited by the number of packet IDs available (65535). I think we could add a secondary restriction to the number of pending inflights per client, if you think it would be beneficial.

Since subscriber was skipped due to write chan full, it should not exist in inflight neither.

Should this not be treated the same as QoS offline message queuing?

Ah, this makes me think we were talking about different things. Are you suggesting moving the enqueue from (for example):
s.pool.Enqueue(func() {
    s.publishToSubscribers(pk)
})

to
for id, subs := range subscribers.Subscriptions {
   if cl, ok := s.Clients.Get(id); ok {
       s.pool.Enqueue(func() {
            _, err := s.publishToClient(cl, subs, pk)
	}
    }
}

or are you suggesting to remove the fixed pool entirely?

Yes, I was originally thinking of enqueue publishToClient. Now there are fixed pool, then there is also a buffered chan for the client write. I think we only need one or the other.

This is very interesting, I've not seen this done for channel writes before.
Is this in place of the following code (apologies, I don't have the ability to test is right now):
if atomic.LoadInt32(&cl.State.outboundQty) >= s.Options.Capabilities.MaximumClientWritesPending {
    return out, packets.ErrPendingClientWritesExceeded
}
cl.State.outbound <- out
atomic.AddInt32(&cl.State.outboundQty, 1)

becomes
select {
    case cl.State.outbound <- out:
        atomic.AddInt32(&cl.State.outboundQty, 1)
    default:
        cl.ops.hooks.OnPublishDropped(cl, pk) // perhaps new hook?
        return out, packets.ErrPendingClientWritesExceeded
}

Yes. Here is an example in Go Playground.

The following will directly add a message to inflight without any constraints, did I miss some other checks?

I see now what you are saying. The quota system restricts the number of messages that are 'inflight' but it does not restrict the number of messages that can be added to a client inflight queue, which is limited by the number of packet IDs available (65535). I think we could add a secondary restriction to the number of pending inflights per client, if you think it would be beneficial.

You're right, it does have 65K bound, so we don't need another check. But more important, for message that was dropped in the 1st place, it should not make into the inflight queue.

Since subscriber was skipped due to write chan full, it should not exist in inflight neither.

Should this not be treated the same as QoS offline message queuing?

I would treat them differently. It can be confusing that msg was not sent in the 1st place, but then all the sudden show up upon reconnect. Messages will also be out of order. For example, msg X is dropped when write chan is full, then msg Y subsequently came in and write chan is free. X will be delivered later on upon reconnect. In addition, given the plan is to call OnPublishDropped when msg is drooped, upper layer may have already taken corrective action, and can conflict when msg is delivered again later on.

Closing in lieu of new PR

Race condition address in PR 165


[Feature request]: Add state_class:measurement attribute to battery level

Describe the solution you'd like
You've already got device_class: battery; please add state_class: measurement.
Thank you.

I don't understand what you mean?
Wrong repo?

I'm sorry. This might be the wrong repo. I'm very confused about where client ends and ws begins.
Looking in Home Assistant. The battery level entity for my doorbell has an attribute for device_class but nothing for state_class.

Please open this issue in eufy_security repository, not here

Thanks & sorry about that.


chore(cb2-2406): update readme

Update the README
Documentation ONLY - updated the README
CB2-2406
Checklist (n/a)

[ ] Code has been tested manually
[x] PR title includes the JIRA ticket number
[x] Branch is rebased against the latest develop
[x] Squashed commit contains the JIRA ticket number

rebased against feature branch (feature/CB2-2097)


_react2.proptypes.string undefined is not an object

react: 16.0.0-beta.5
react-native: 0.49.2
react-native-credit-card-input: ^0.3.3
i followed this documentation : https://github.com/sbycrosz/react-native-credit-card-input
Error  : _react2.proptypes.string undefined is not an object

I created PR #88
For time being...
npm install https://github.com/Andreyco/react-native-credit-card-input.git
// or
yarn add https://github.com/Andreyco/react-native-credit-card-input.git

😩 there is so much mess under the hood

@Andreyco Thanks 👍

Thanks @Andreyco!

@sbycrosz @Andreyco Is anyone still looking at PRs for this? Project feels pretty dead, given the breaking changes with RN v0.50. Had to go in and fix the PropTypes and ImageBackground issues myself. Would love to submit a PR but can't even get access to push my branch.

@wtglover can you please share the location of your work similar to what @Andreyco has done?

@sbycrosz I don't think it is included in 4.1 can you please confirm? (especially  - the ImageBackground issue...)


How to add MOE model Mistral 8x7B

Here is the model not sure how to add it to ollama
https://huggingface.co/mattshumer/mistral-8x7b-chat

i believe this pr should enable support to llama.cpp https://github.com/ggerganov/llama.cpp/pull/4406


Mac builds fail

I think some sort of security issue perhaps?
upload/clipboard/src/clipboard.cpp:5:9: warning: 'DLIB_LOG_DOMAIN' macro redefined [-Wmacro-redefined]
#define DLIB_LOG_DOMAIN LIB_NAME

Full log:
log.txt
Defold 1.6.3

Just managed to build without changing anything (I think). I believe the issue can be closed unless there is something interesting in the logs.

There was an error about disk space. We'll look into it. Closing this one though!

"upload/clipboard/src/clipboard.cpp:5:9: warning: 'DLIB_LOG_DOMAIN' macro redefined [-Wmacro-redefined]
#define DLIB_LOG_DOMAIN LIB_NAME"
Is just a warning that the define is already defined from the build system.
The superfluous define should be removed from this extension to avoid the warning.

The superfluous define should be removed from this extension to avoid the warning.

Removed in https://github.com/britzl/defold-clipboard/commit/c159ca1bc6aeaff7f40e1cdb464384f97ab86c92


Account for the fact that there non-llama.cpp gguf files now

companion internal PR
TL;DR: we want the ability to discriminate non-llama.cpp gguf repos
I've picked ${architecture}.context_length as a property that, if it's in the gguf file, we assume it's compatible with llama.cpp
Another option was to check whether architecture is inside the list in @huggingface/gguf (and keep this list up to date with upstream, maybe through some CI)
Both options are possible, so let me know what you think is best

(since we'll need to keep the architecture list fully synced at all times - which gets updated quite a bit)

Yes, but IMO in the future we (e.g. @ngxson 😁) can automate the syncing of our architecture list with upstream through some CI


Publish feature branch

Overview
While we don't define how to handle publishing charm in different channel based on spec ISD114, this workflow allows publishing to a temporary branch that can be used to deploy the charm and test it.
Rationale
Publish and test a new feature without affecting edge and stable versions.
Juju Events Changes

Module Changes

Library Changes

Checklist

[x] The charm style guide was applied
[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Manging Charm Complexity
[x] The documentation is generated using src-docs
[ ] The documentation for charmhub is updated.
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

No need to update doc.

Out of curiosity, would this be for testing on staging? (With github runners we currently scp the files manually... and we can't quite use the edge channels due to deployment promotion reasons) LGTM!

The idea was to testing in staging features that could break the current version but while talking with @javierdelapuente a better approach is to use flags to enable/disable features so we won't have too much trouble reviewing features branches.
Closing this in favor of that :+1:


[SPARK-31607][SQL] Improve the perf of CTESubstitution

What changes were proposed in this pull request?

In CTESubstitution, resolve CTE relations first, then traverse the main plan only once to substitute CTE relations.
Why are the changes needed?

Currently we will traverse the main query many times (if there are many CTE relations), which can be pretty slow if the main query is large.
Does this PR introduce any user-facing change?

No
How was this patch tested?

local perf test
scala> :pa
// Entering paste mode (ctrl-D to finish)

def test(i: Int): Unit = 1.to(i).foreach { _ =>
  spark.sql("""
    with
    t1 as (select 1),
    t2 as (select 1),
    t3 as (select 1),
    t4 as (select 1),
    t5 as (select 1),
    t6 as (select 1),
    t7 as (select 1),
    t8 as (select 1),
    t9 as (select 1)
    select * from t1, t2, t3, t4, t5, t6, t7, t8, t9""").queryExecution.assertAnalyzed()
}

// Exiting paste mode, now interpreting.

test: (i: Int)Unit

scala> test(10000)

scala> println(org.apache.spark.sql.catalyst.rules.RuleExecutor.dumpTimeSpent)

The result before this patch
Rule                                       Effective Time / Total Time                     Effective Runs / Total Runs
CTESubstitution<PHONE_NUMBER> /<PHONE_NUMBER>                         10000 / 20000

The result after this patch
Rule                                       Effective Time / Total Time                     Effective Runs / Total Runs
CTESubstitution<PHONE_NUMBER> /<PHONE_NUMBER>                         10000 / 20000

About 2 times faster.

Test build #122074 has started for PR 28407 at commit c906218.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26749/
Test PASSed.

cc @peter-toth @hvanhovell @HyukjinKwon

Thank you always, @cloud-fan .

I like this approach and LGTM.
Just a side note that due to its eager way of substitution it can also cause performance degradation with queries where a CTE is defined but never actually used. But the performance gain that the PR can bring with realistic queries is worth the change.

Test build #122074 has finished for PR 28407 at commit c906218.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122074/
Test PASSed.

Just a side note that due to its eager way of substitution it can also cause performance degradation with queries where a CTE is defined but never actually used.

Yea I thought about it as well. It's still doable if I change the map type to Map[String, PlanHolder] where PlanHolder can lazily calculate the plan. However, I feel it's too rare to have CTE relations defined but not used, and may not worth it.

Test build #122126 has started for PR 28407 at commit b022e35.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26799/
Test PASSed.

the last commit just updates comment, and it already passes compilation.
I'm merging to master, thanks for review!

Test build #122126 has finished for PR 28407 at commit b022e35.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122126/
Test PASSed.


docs: Add instructions and example for KRMfn

Add a section to the readme and an example for a no-install kustomize approach
using khelm as a containerized KRM function.

@jskrzypek I realize the CONTRIBUTING.md doesn't say anything about one sentence per line - my bad, I'll update the CONTRIBUTING.md.
Do you still think you could find the time to address the concerns mentioned above?
(Otherwise I'd merge it as is and polish it myself before it rots here.)

I'm really sorry, but I'm just swamped at the moment. 😓

No worries, I'll merge it then!


xdg-utils: don't clobber words with sed eg passed

Things done:

[X] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
[X] Built on platform(s): NixOS
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

More
Fixes issue #13904
cc @edolstra

Please note, that points are not mandatory, but rather desired.
See #13904

This doesn't work well.

The sed occurrences weren't replaced with this PR. Still thanks. I pushed a larger refactoring of the code that seems to do less clobbering, although I didn't see how to easily distinguish e.g. file words...


How can i forward karpenter controller logs to elasticsearch using filebeat.

What problem are you trying to solve?
I need to send the karpenter controller logs to elastic search using filebeat . so that i can provide logs view using graylog or ELK.
How important is this feature to you?
It helps to developers to know status or nodes where workload pods are running. So that it will be helpful for to dubug incase nodeclaim deleted ,workload pods are not running at that point of time.

I'd recommend asking in the Karpenter Kubernetes slack channel for questions on how to integrate other tools, or ask in the respective github repos for this. I'll close this out, as this is more directed to elastic search or filebeat, and isn't specific to Karpenter.


F12 should work across files/modules

Brainstorming for this item:
Phase 1: Parsing out what gets brought in from Import-Module and looking for any scripts/modules found via that method
Step 2: If nothing found, we can get module information from a command, and then via Get-Command -Module / Get-Module where the Module is a script [eventually manifest too] -- parsing through that as needed.


CLOUD-679 fixed readme links

@martonsereg

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1075/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/1076/


[Bug]: Failing to bundle extension on shopify app dev

Please confirm that you have:

[x] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[x] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Extension
Expected behavior
It should properly build the extension and load it.
Actual behavior
Getting the following output below in console when running shopify app dev.
I started off doing this and getting the error in a private repo and got the same error when creating a new app and extension from scratch, detailed in the reproduction steps.
It seems to have trouble building the extension (no dist ouput) despite using the shopify cli to scaffold the extension. Is there a system dependency that the cli depends on to build the extension?
[ERROR] Could not resolve "@shopify/ui-extensions-react/admin"

    extensions/test-app/src/ActionExtension.jsx:16:7:
      16 │ } from '@shopify/ui-extensions-react/admin';
         ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The Yarn Plug'n'Play manifest forbids importing "@shopify/ui-extensions-react" here because it's
  not listed as a dependency of this package:

    ../../.pnp.cjs:43:33:
      43 │           "packageDependencies": [\
         ╵                                  ~~

  You can mark the path "@shopify/ui-extensions-react/admin" as external to exclude it from the
  bundle, which will remove this error and leave the unresolved path in the bundle.

✘ [ERROR] Could not resolve "react/jsx-runtime"

    extensions/test-app/src/ActionExtension.jsx:23:44:
      23 │ export default reactExtension(TARGET, () => <App />);
         ╵                                             ^

  The Yarn Plug'n'Play manifest forbids importing "react" here because it's not listed as a
  dependency of this package:

    ../../.pnp.cjs:43:33:
      43 │           "packageDependencies": [\
         ╵                                  ~~

  You can mark the path "react/jsx-runtime" as external to exclude it from the bundle, which will
  remove this error and leave the unresolved path in the bundle.

✘ [ERROR] Could not resolve "@shopify/ui-extensions-react/admin"

    extensions/test-app/src/ActionExtension.jsx:16:7:
      16 │ } from '@shopify/ui-extensions-react/admin';
         ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  The Yarn Plug'n'Play manifest forbids importing "@shopify/ui-extensions-react" here because it's
  not listed as a dependency of this package:

    ../../.pnp.cjs:43:33:
      43 │           "packageDependencies": [\
         ╵                                  ~~

  You can mark the path "@shopify/ui-extensions-react/admin" as external to exclude it from the
  bundle, which will remove this error and leave the unresolved path in the bundle.

✘ [ERROR] Could not resolve "react/jsx-runtime"

    extensions/test-app/src/ActionExtension.jsx:23:44:
      23 │ export default reactExtension(TARGET, () => <App />);

Verbose output
The output is similar, the prior output suggests it successfully sets up a tunnel and then attempts to build the extension.
Reproduction steps

Run shopify app init, choose Remix, TypeScript
Run shopify app generate extension, choose Admin action
Run shopify app dev

Operating System
macOS Sonoma 14.5
Shopify CLI version (check your project's package.json if you're not sure)
3.66.0
Shell
No response
Node version (run node -v if you're not sure)
v22.5.1
What language and version are you using in your application?
No response

@md-brethren that looks like a different error. Could you please open a new issue and add as many details as you can?

Hi! Are you using Yarn 2.x or above? Because the CLI is only compatible with Yarn classic (1.x). Or NPM or PNPM.
We'll update the requirements here, because that was removed by mistake recently.

I'm running yarn 1.22.1

Closing for now, if you still have issues post a comment and I'll reopen the issue @asoong

Also on yarn @1.22.19
The Yarn Plug'n'Play manifest forbids importing
 "@shopify/ui-extensions-react" here because it's not listed as a dependency of this

I found the root cause of the issue. There was a .pnp.cjs file on the root folder. Removing that resolved this issue. It conflicted with Yarns workspace approach. @isaacroldan @asoong


feat(v2): add ability to hide doc sidebar

Motivation
This PR allows you to hide the doc sidebar along with increasing content column width.
This is useful when there is a lot of long content on the page and you want to focus on it. This feature can also be actively used on medium screens (e.g. on tablets).
GitBook and GitLab docs have a similar feature in, but there the content column width does not increase, which loses the meaning of this feature, in my view.
As a result, the user has the opportunity to expand the content area width by 300px (this is sidebar width) if they hides the sidebar (see screenshots below).
I would even recommend turning it on by default, because in reality few docs generators have this functionality, this will be our just one more advantage.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview.

Before
After

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

@yangshun what do you think of this feature? Actually, it did not take a lot of code to implement it, but it seems to me that this will be a useful feature for our users. Moreover, that is good from the point of view of UX.

Hi,
The feature looks a good idea to me, but I'm not a fan of having the collapsed sidebar still being visible (a matter of taste, but I see some apps do that as well).
This feature is mostly useful on medium screens, what about making the sidebar totally disappear, with an ability to toggle/pin it?
I'm thinking about something like:
https://codepen.io/Kristuff/pen/apEEYM
If we keep current designs, some details:

During transitions, the sidebar should keep a constant width, otherwise there's FOUC due to text wrapping
Not a fan of having the expansion icon so much at the bottom, i'd rather add it to the center of the sidebar with more paddings

Not a fan of having the expansion icon so much at the bottom, i'd rather add it to the center of the sidebar with more paddings

Agreed, the current design works but can be made more aesthetically pleasing.
Some ideas:
Visible

Hidden

Let's revisit this in future if/when Alexey is back. This was never published and it has a ton of merge conflicts now.


The possibility of defining the memory limit to use is added.

I am trying to correct the error reported in #1
I hope it can help

Thanks @mnico :)


Add documentation on how to add your own models

Add an explanation in github wiki, GUI or as a markdown file in the repo on how to create/add your own models

I have added some simple wiki how(s) regarding adding your own models (as well as model formats). I will probably add some simple gifs/videos on this in the near future.


CSS Modules of css-loader support?

Hi.
I am using this and implementing server side rendering. But this does not work with css-loader with modules option like ?modules&importLoaders=1&localIdentName=[name]__[local]___[hash:base64:5].
If compiling css
// a.css
.a {
  color: red;
}

and js importing it
var styles = require('./a.css')
console.log(styles) //  puts ->  Object {a: "a__a___3whEy"}

then webpack-assets.json should be
{
  ...
  "assets": {
    "./a.css": {"a":"a__a___3whEy"}
  }

but in fact it will be like
{
  ...
  "assets": {
    "./a.css": ".a__a___3whEy {\n  color: red;\n}\n"
  }
}

I think internal require-hacker ignores exports.locals even though css-loader generates css class map object as js module like
exports.locals = {
  className: "_23_aKvs-b8bW2Vg3fwHozO",
  subClass: "_13LGdX8RMStbBE9w-t0gZ1"
}

cf. CSS Module section of css-loader
Thanks.

It works with CSS modules.
https://github.com/halt-hammerzeit/webpack-isomorphic-tools#style-loader-css-stylesheets-with-css-modules-feature
Post your configuration.

The repo is https://github.com/endaaman/rei_no_are

Ok, now compare these two and find the solution:
https://github.com/halt-hammerzeit/webpack-isomorphic-tools#style-loader-css-stylesheets-with-css-modules-feature
https://github.com/endaaman/rei_no_are/blob/master/webpack-isomorphic-tools.js

Ohh Im great sorry. I didnt see the section. Thank you very much.

FYI
I'm posting this in every issue and PR to notify whoever may be interested:
today I've released an alternative helper library called universal-webpack.
It takes a different approach than webpack-ismorphic-tools and instead of hacking Node.js require() calls it just compiles all code with target: 'node' webpack configuration option.
As a result, all Webpack plugins and features are supported.
If you think you might need that here's an example project:
https://github.com/halt-hammerzeit/webpack-react-redux-isomorphic-render-example


SECCON

a good concept. Are there any sample configurations to help illustrate the framework's effectiveness.

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

ID: c3fa1093-f014-b19a-0a3f-621bb239b23d
Version Independent ID: eaf6cb9a-9d2a-5ea0-71ba-0801e073d49e
Content: Windows security configuration framework
Content Source: windows/security/threat-protection/windows-security-configuration-framework/windows-security-configuration-framework.md
Product: w10
Technology: windows
GitHub Login: @appcompatguy
Microsoft Alias: appcompatguy

We validated the configurations and approaches with several preview customers, if that's what you're asking.

I think the OP meant to ask if there are any written configuration examples which could be added to the documentation page for viewing and testing (e.g. try before buy samples). Considering the scope of this topic, though, I imagine that such examples would include so much work that it might not be feasible to create any stand-alone examples for the public to view and test.

+1 for a better documentation explaining what is this about and how to use so it's more approachable on first visit.

@officedocsbot assign @e0i

Has there been a follow up to level 1 and level 2 (SECCON frameworks) - Level 2 and Level 1 guidance is coming soon apparently but this article appears to be over a year old?

Has there been a follow up to level 1 and level 2 (SECCON frameworks) - Level 2 and Level 1 guidance is coming soon apparently but this article appears to be over a year old?

The dates didn't get updated in the template we started with (will be fixed when the next update is published so they're accurate) - the article is only about a month old. We are working on it, but there are a number of initiatives to align to in order to drive the right outcome. We recently published this for Azure - https://docs.microsoft.com/en-us/azure/active-directory/devices/concept-azure-managed-workstation - and are working with multiple teams to ensure that everyone is providing the same information in a usable way!

Ah ok, that makes more sense. Thanks for the reply

@rvanstone
We are closing this issue since your question seems to be answered. Feel free to re-open this issue if you feel it hasn't been answered.
Thanks.

@officedocsbot close


the file was moved

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


chores: Included template for issues creation

Included template for issues creation
Description
GitHub Issue templates, for users/devs to easily create issues with required information.

Bug report template
Feature request template
Question template
Sprint template

How Has This Been Tested?

Import the template to your fork repo for testing.

Merge criteria:

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

/lgtm
/approve
Thanks Harshad, really helpful additions!  :slightly_smiling_face:


make new links

its blocked

wdym? provide more info

@ftgyhuj456 any suggestions? please need your feedback

can now deploy yourself with koyeb (see button in readme), also you can join our discord server for the full list of links: https://discord.gg/QHtx8M5Zkx


User defaults updating is triggered for fresh installs

The UserDefaultsUpdater class triggers the user defaults updating process even for fresh installs. Not only is this unnecessary, it's also dangerous because it's completely untested.
UserDefaultsUpdater must detect that a fresh install has been made and perform no user defaults updating.

Analysis of UserDefaultsUpdater:

The following upgradeToVersionNNN methods do nothing

upgradeToVersion1
upgradeToVersion2
upgradeToVersion3
upgradeToVersion4
upgradeToVersion8
upgradeToVersion9

The following upgradeToVersionNNN methods do something

upgradeToVersion5

Adds a dictionary "BoardPosition" with the following key/value pairs
DiscardFutureMovesAlert = True
BoardPositionLastViewed = -1

upgradeToVersion6

Changes the dictionary "BoardPosition" which was added by upgradeToVersion5
Removes key "BoardPositionLastViewed"

upgradeToVersion7

Changes the dictionary "BoardPosition" which was added by upgradeToVersion5
Adds the following key/value pair
MarkNextMove = true

Summary: The final result of the unexpected updating process is that the dictionary "BoardPosition" is present with some key/value pairs. Fortunately these key/value pairs are exactly those key/value pairs that are present in the registration domain (i.e. RegistrationDomainDefaults.plist).
Conclusion: No real harm done.


Dartpad doesn't open

This window pops up whenever I click Open Pure Dartpad
My OS: Windows 10 LTSC
I have portable, offical, last version of VS Code installed.

I am facing same issues opening Dartpad in visual studio

 This window pops up whenever I click Open Pure Dartpad
My OS: Windows 10 LTSC I have portable, offical, last version of VS Code installed.

Hey guys
Sorry, but I don’t work on this extension anymore🙂


Add meta descriptions to rule pages

Summary
This PR updates the scripts/generate_mkdocs.py to add meta descriptions to each rule as well as a fallback site_description.
I was initially planning to add this to generate_docs.rs; however running mdformat on the rules caused the format of the additional description to change into a state that mkdocs could not handle.
Fixes #13197
Test Plan

Run  python scripts/generate_mkdocs.py to build the documentation
Run mkdocs serve -f mkdocs.public.yml to serve the docs site locally
Navigate to a rule on both the local site and the current production site and note the addition of the description head tag. For example:

http://<IP_ADDRESS>:8000/ruff/rules/unused-import/

https://docs.astral.sh/ruff/rules/unused-import/

Thank you! That's great.


Consolidate cronjobs logging

Signed-off-by: myan<EMAIL_ADDRESS>Ref: https://issues.redhat.com/browse/ACM-7029

Replace sql logging with ORM
Fixed the log issue that the end_at of the retention job isn't set.

/test images

/retest

/retest

/cc @hchenxa @clyang82


Create and  correct user story for feature tracking and creation across the team

As a , I want , So that .
Context: This user story identifies the user role as a movie enthusiast, the feature or requirement as  the ability to search for movies by title, and the reason or benefit as the ability to quickly find desired movies.
Acceptance criteria:
TBD added in separate task card.


Add force autoupdate feature

It closes #1120
For testing purposes, I will release a couple of signed artifacts in a separate branch and publish links to them in the comments below.

v0.2.14-test.0

Windows: x64
macOS: x64 arm64
Linux

AppImage x64 arm64
deb x64 arm64

v0.2.14-test.1

Windows: x64
macOS: x64 arm64
Linux

AppImage x64 arm64
deb x64 arm64

Works perfect on macOS

BUT

It requires Administrator rights (so there are popup shown) on WIndows in case of installing “for everybody”. Therefore it may break up smeshing. The good news is that if you run Smapp with administrator rights, then it updates without any additional questions.So it may work fine for us, but we need to let our users know that they need to run it with Administrator rights.
AppImages shows AppImageLauncher popup (asking "Run once" or "Integrate and run"). :( Trying to find a workaround...

Also, to be sure that after installing update Smapp starts the node and etc — we should insist on turning on "Wallet auto start" on the settings page :-p
You can check it out as well:

Download v0.2.14-test.0
Server your own networks.json with v0.2.14-test.1 as minSmappRelease
Connect to such network — it should force update & restart

p.s.
It checks for update on connecting to the network and then every 24h. Is it enought?


Correct tests failing in master

The executable permissions set in the tests modified should be 755 to work in a zip file. 775 is okay, but the group write gets dropped, which was not what the test was checking.

CircleCI fails https://app.circleci.com/pipelines/github/UnitedIncome/serverless-python-requirements/40/workflows/b0264aa7-fb51-4988-99f6-2145cef52afc/jobs/1082 as it wasn't migrated to v2?

@gliptak yes, I should remove the circle stuff.

That's done, the webhook is disabled.


ATC error after deploying to ABAP system

Hello,
I used the excel upload tool ( cc.excelUpload.v0_19_0 ) in my app and everything seems to be working fine.
But when i deployed the app to the ABAP system I get the following ATC error, Please let me know the best way to handle this.

Please use the bug template.
Did you use central or in-app deployment?
Thanks

I just had a look again and in the Note 2588088 this is suggested as resolution:

Run the following report manually : /UI5/APP_INDEX_CALCULATE

If this is not the resolution, this is a false positive because you defined the component in the manifest.
The default usage is to use a deployed component, but guess you using the component from the app.
So the test is looking for the component on the local system but can not find it because it is not deployed.
Can you confirm this?

Do you need more support on this?

thanks Marian, I am ok for now. I will reach out if I need help. thanks

I got a report that a different company has the same message.
What SAP System is this error from?
As a "Hotfix" you can deploy the component with the version (in this case v0.19.0) to the SAP System like described here:
https://docs.spreadsheet-importer.com/pages/CentralDeployment/
Unfortunately you have to do that for every version.
I´ll check if there is a different solution

Still a workaround and not a solution, but that works adding this in the manifest.json:
"sap.app": {
  "embeds": ["thirdparty/customControl/spreadsheetImporter/v0_29_0"]
}

documented here:
https://docs.spreadsheet-importer.com/pages/GettingStarted/#decentralized-deployment


Runtime error when running Roberta with multiple GPUs on CommonSenseQA

When I run Roberta with multiple GPUs on CommonSenseQA, I encounter a problem of runtime time. Does anyone encounter the same problem ? Thanks.
 -- Process 1 terminated with the following error:
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/torch/multiprocessing/spawn.py", line 19, in _wrap
    fn(i, *args)
  File "/usr/local/lib/python3.5/dist-packages/fairseq_cli/train.py", line 284, in distributed_main
    main(args, init_distributed=True)
  File "/usr/local/lib/python3.5/dist-packages/fairseq_cli/train.py", line 80, in main
    train(args, trainer, task, epoch_itr)
  File "/usr/local/lib/python3.5/dist-packages/fairseq_cli/train.py", line 121, in train
    log_output = trainer.train_step(samples)
  File "/usr/local/lib/python3.5/dist-packages/fairseq/trainer.py", line 287, in train_step
    raise e
  File "/usr/local/lib/python3.5/dist-packages/fairseq/trainer.py", line 264, in train_step
    ignore_grad
  File "/usr/local/lib/python3.5/dist-packages/fairseq/tasks/fairseq_task.py", line 230, in train_step
    loss, sample_size, logging_output = criterion(model, sample)
  File "/usr/local/lib/python3.5/dist-packages/torch/nn/modules/module.py", line 547, in __call__
    result = self.forward(*input, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/fairseq/criterions/sentence_ranking.py", line 49, in forward
    classification_head_name='sentence_classification_head',
  File "/usr/local/lib/python3.5/dist-packages/torch/nn/modules/module.py", line 547, in __call__
    result = self.forward(*input, **kwargs)
  File "/usr/local/lib/python3.5/dist-packages/torch/nn/parallel/distributed.py", line 459, in forward
    self.reducer.prepare_for_backward([])
RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by (1) passing the keyword argument `find_unused_parameters=True` to `torch.nn.parallel.DistributedDataParallel`; (2) making sure all `forward` function outputs participate in calculating loss. If you already have done the above two steps, then the distributed data parallel module wasn't able to locate the output tensors in the return value of your module's `forward` function. Please include the loss function and the structure of the return value of `forward` of your module when reporting this issue (e.g. list, dict, iterable). (prepare_for_backward at /pytorch/torch/csrc/distributed/c10d/reducer.cpp:518)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7f414b2e0273 in /usr/local/lib/python3.5/dist-packages/torch/lib/libc10.so)
frame #1: c10d::Reducer::prepare_for_backward(std::vector<torch::autograd::Variable, std::allocator<torch::autograd::Variable> > const&) + 0x734 (0x7f414c573ac4 in /usr/local/lib/python3.5/dist-packages/torch/lib/libtorch_python.so)
frame #2: <unknown function> + 0x691b2c (0x7f414c562b2c in /usr/local/lib/python3.5/dist-packages/torch/lib/libtorch_python.so)
frame #3: <unknown function> + 0x1d3f04 (0x7f414c0a4f04 in /usr/local/lib/python3.5/dist-packages/torch/lib/libtorch_python.so)
frame #4: PyCFunction_Call + 0x77 (0x4ea137 in /usr/bin/python3)
frame #5: PyEval_EvalFrameEx + 0x59f6 (0x53c176 in /usr/bin/python3)
frame #6: PyEval_EvalCodeEx + 0x13b (0x540b0b in /usr/bin/python3)
frame #7: /usr/bin/python3() [0x4ec3f7]
frame #8: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #9: PyEval_EvalFrameEx + 0x252b (0x538cab in /usr/bin/python3)
frame #10: PyEval_EvalCodeEx + 0x13b (0x540b0b in /usr/bin/python3)
frame #11: /usr/bin/python3() [0x4ec3f7]
frame #12: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #13: /usr/bin/python3() [0x4fbfce]
frame #14: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #15: /usr/bin/python3() [0x574db6]
frame #16: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #17: PyEval_EvalFrameEx + 0x252b (0x538cab in /usr/bin/python3)
frame #18: PyEval_EvalCodeEx + 0x13b (0x540b0b in /usr/bin/python3)
frame #19: /usr/bin/python3() [0x4ec3f7]
frame #20: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #21: PyEval_EvalFrameEx + 0x252b (0x538cab in /usr/bin/python3)
frame #22: PyEval_EvalCodeEx + 0x13b (0x540b0b in /usr/bin/python3)
frame #23: /usr/bin/python3() [0x4ec2e3]
frame #24: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #25: /usr/bin/python3() [0x4fbfce]
frame #26: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #27: /usr/bin/python3() [0x574db6]
frame #28: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #29: PyEval_EvalFrameEx + 0x4ed6 (0x53b656 in /usr/bin/python3)
frame #30: /usr/bin/python3() [0x53fc97]
frame #31: PyEval_EvalFrameEx + 0x50bf (0x53b83f in /usr/bin/python3)
frame #32: /usr/bin/python3() [0x5401ef]
frame #33: PyEval_EvalFrameEx + 0x50bf (0x53b83f in /usr/bin/python3)
frame #34: PyEval_EvalFrameEx + 0x4b14 (0x53b294 in /usr/bin/python3)
frame #35: /usr/bin/python3() [0x53fc97]
frame #36: PyEval_EvalFrameEx + 0x50bf (0x53b83f in /usr/bin/python3)
frame #37: PyEval_EvalCodeEx + 0x13b (0x540b0b in /usr/bin/python3)
frame #38: /usr/bin/python3() [0x4ec358]
frame #39: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #40: PyEval_EvalFrameEx + 0x252b (0x538cab in /usr/bin/python3)
frame #41: PyEval_EvalCodeEx + 0x13b (0x540b0b in /usr/bin/python3)
frame #42: /usr/bin/python3() [0x4ec3f7]
frame #43: PyObject_Call + 0x47 (0x5c20e7 in /usr/bin/python3)
frame #44: PyEval_EvalFrameEx + 0x252b (0x538cab in /usr/bin/python3)
frame #45: PyEval_EvalFrameEx + 0x4b14 (0x53b294 in /usr/bin/python3)
frame #46: PyEval_EvalFrameEx + 0x4b14 (0x53b294 in /usr/bin/python3)
frame #47: PyEval_EvalFrameEx + 0x4b14 (0x53b294 in /usr/bin/python3)
frame #48: /usr/bin/python3() [0x53fc97]
frame #49: PyEval_EvalFrameEx + 0x50bf (0x53b83f in /usr/bin/python3)
frame #50: /usr/bin/python3() [0x53fc97]
frame #51: PyEval_EvalCode + 0x1f (0x5409bf in /usr/bin/python3)
frame #52: PyRun_StringFlags + 0x8f (0x52084f in /usr/bin/python3)
frame #53: PyRun_SimpleStringFlags + 0x3c (0x60f15c in /usr/bin/python3)
frame #54: Py_Main + 0x581 (0x640381 in /usr/bin/python3)
frame #55: main + 0xe1 (0x4d0001 in /usr/bin/python3)
frame #56: __libc_start_main + 0xf0 (0x7f41513c6830 in /lib/x86_64-linux-gnu/libc.so.6)
frame #57: _start + 0x29 (0x5d6999 in /usr/bin/python3)

/usr/lib/python3.5/multiprocessing/semaphore_tracker.py:129: UserWarning: semaphore_tracker: There appear to be 3 leaked semaphores to clean up at shutdown
  len(cache))

Here is my fine tune scripts:
MAX_UPDATES=3000        # Number of training steps.
WARMUP_UPDATES=150    # Linearly increase LR over this many steps.
LR=1e-05              # Peak LR for polynomial LR scheduler.
MAX_SENTENCES=16      # Batch size.
SEED=1                # Random seed.
 Just comment them out!

Do you suggested that the default of find_unused_parameters need to be changed to "True", and then I can use multiple GPUs to run RoBerta ?

Yeah. I actually did it but still it gave me errors in multi GPU. Then I
removed all the unused model elements (Roberts head class ). It worked
On Tue, 10 Sep 2019 at 12:15 PM Allenyummy<EMAIL_ADDRESS>wrote:

Do you suggested that the default of find_unused_parameters need to be
changed to "True", and then I can use multiple GPUs to run RoBerta ?
[image: image]
https://user-images.githubusercontent.com/36063123/64574653-e31cf800-d3a2-11e9-96ae-e560753b1a7b.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pytorch/fairseq/issues/1119?email_source=notifications&email_token=AEA4FGSZ6IO7ZCB5VO5UIULQI3RLZA5CNFSM4IUXAIGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6JM7GQ#issuecomment-529715098,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEA4FGQXXG2LVCDBOWSVOR3QI3RLZANCNFSM4IUXAIGA
.

Sorry, I'm new to Roberta. How to remove all the unused model elements ?

What is the unused model elements (Roberts head class) ?

@chiangyulun0914 can you try running train cmd with --find-unused-parameters?

Yeah, I tried, and I think it was in stuck.

Just commented out the function starting in the following line.
https://github.com/pytorch/fairseq/blob/master/fairseq/models/roberta/model.py#L261

Yeah, I tried, and I think it was in stuck.

Did you solve this problem by commenting out the function? I have met this problem too, even I commented out the function.

No, I haven't tried to comment out the function provided by shamanez.
What does the error look like after commenting out the function ?

Hi,
After running the scipts with multiple gpu, I meet this error:
RuntimeError: Not all gradients have been reduced from the backward of the previous iteration. This is unexpected and fatal error. Please check and ensure that the model's parameters are not changed after you wrap up the model with DistributedDataParallel.
Which means the model's parameters have been changed？Why? Have you met this error?

Please try with --ddp-backend=no_c10d, it seems some of the finetuning code doesn't work well with the built-in PyTorch DistributedDataParallel.

This should be fixed after using --ddp-backend=no_c10d. The README has been updated as well.


Remove deprecated rejectOnNotFound from docs

main/content/400-reference/200-api-reference/050-prisma-client-reference.mdx

Note: Definitely not remove, we only have 1 docs and majority of users will use an older Prisma in the beginning, and a lot of users will for a loooong time.


refactor: move cmd/aries-agentd out of pkg

Signed-off-by: sudesh.shetty<EMAIL_ADDRESS>

Codecov Report

Merging #156 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #156   +/-   ##
=======================================
  Coverage   87.17%   87.17%
=======================================
  Files          30       30
  Lines        1076     1076
=======================================
  Hits          938      938
  Misses         74       74
  Partials       64       64

Impacted Files
Coverage Δ

cmd/aries-agentd/main.go
65.21% <ø> (ø)

Continue to review full report at Codecov.

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


fix accessibility of included fabric api modules by using modApi instead of modImplementation

is there a similar something to replace mixinextras implementation() aswell?


Use -1 to disable key algorithm type in ssh.minimum_key_sizes

Fix #11634
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Please send backport


Fix failing Lighthouse job

Jira
http://vjira2:8080/browse/BDS-2048
Summary
Updates Lighthouse assertions to "warn" not "error" on pages that are not crawlable.
Details
Lighthouse Travis job was failing when it hit pages that weren't crawlable, and these are indeed pages we do not want to be crawled. So, the assertion has been updated to only "warn" when a page is not crawlable. It was not specified before, so I assume it was defaulting to "error" as part of the "minScore" assertion.
I also tested a branch with additional feature changes (fix/test-lighthouse-with-feature) and it's passing.
How to test

Review files changed
Verify passing builds

PR was released with v2.19.0


Re-Allow to register helpers without controllers

Example from the README:
You OtherApps:
register Padrino::Warden::Helpers

This is broken in current Versions of Padrino.
This PR readds this functionality while maintaining compatibility

Thanks for your contribution!

No problem. It would be nice of you to bump the version so that gem updated the file

@FeeJai I think I have taken care of that, let me know if there are any problems


MSGPack updates

Updates QCEngine to support the new Msgpack/NumPy-based QCElemental. This change requires https://github.com/leeping/geomeTRIC/pull/96 to pass.

This will pass as 0.6.0 propagates on c-f. Please go ahead and review so we can merge quickly.


Document musical philosophy

Preliminary high points:

Xenakis meets Sethares:

all levels of a composition must allow appropriate stochastic elements
synthesis and and scales have consonance estimates and composition / performance tools can read and write them

Sweet spot is small ensembles:

low clock rate and small RAM limit the amount of audio that can be computed at practical sampling rates by an RP2040
this leads to the need to trade off between a higher-quality of a single voice and multiple lower-quality voices.


Mono still lacks support for stuff

See #157
Neither 4.1.0 nor 4.1.1 seem to include a fix for it.
Needs just the commenting out of the "offending" using, no bad effects otherwise.
/home/[snip]/development/Grapevine-<IP_ADDRESS>/src/Grapevine/Grapevine.csproj (default targets) ->
/usr/lib/mono/xbuild/14.0/bin/Microsoft.CSharp.targets (CoreCompile target) ->

	Server/RestServer.cs(12,60): error CS0426: The type name 'ExtendedProtectionSelector' does not exist in the type 'HttpListener
Extra:
# mono --version
Mono JIT compiler version <IP_ADDRESS> (tarball Sat Aug  4 08:32:47 UTC 2018)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug
	Interpreter:   yes
	LLVM:          yes(3.6.0svn-mono-/)
	GC:            sgen (concurrent by default)

In addition:
/home/[snip]/development/Grapevine-<IP_ADDRESS>/src/Grapevine/Grapevine.csproj (default targets) ->
/usr/lib/mono/xbuild/14.0/bin/Microsoft.CSharp.targets (CoreCompile target) ->

	Interfaces/Server/IHttpListener.cs(135,75): error CS1061: 'HttpListener' does not contain a definition for 'DefaultServiceNames' and no extension method 'DefaultServiceNames' accepting a first argument of type 'HttpListener' could be found (are you missing a using directive or an assembly reference?)

If you can live without, commenting out the lines gets the compilation to success.

@acolomitchi I don't have ready access to Mono to test out issues like this. Is this still an issue in the current Grapevine 4? Also, would you be so kind as to check out Grapevine 5 () and let me know if you see any Mono-related issues? It's still in beta, so if I can fix anything there before the release, that would be ideal.

I see none of this in the beta for Grapevine 5, but it looks like something are still left around in Grapevine 4. I'll clean those up and publish a new package.

I see none of this in the beta for Grapevine 5, but it looks like something are still left around in Grapevine 4. I'll clean those up and publish a new package.


patch for cloud-api lambda issue

Important: The AWS Mobile CLI is in maintanence mode. If you are building a new mobile or web app, or you're adding cloud capabilities to your existing app, use the new AWS Amplify CLI instead. Use this template to report bugs. For new feature requests refer to the aws-amplify/amplify-cli repository.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #189 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #189      +/-   ##
==========================================
+ Coverage   80.82%   80.88%   +0.05%
==========================================
  Files          85       85
  Lines        5726     5722       -4
  Branches      920      918       -2
==========================================
  Hits         4628     4628
+ Misses        936      934       -2
+ Partials      162      160       -2

Impacted Files
Coverage Δ

lib/backend-operations/ops-cloud-api.js
61.02% <ø> (+1.74%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix permissions issue

Not sure if this is correct, or whether it needs to be applied for the mac, but I got the following error on two computers running Ubuntu without it:
espeon install_dependencies
[sudo] password for robert:
/home/robert/.lenv/lua/5.1.5/bin/lua: .../.lenv/lua/5.1.5/share/lua/5.1/espeon/util/shell.lua:16: The directory '/home/robert/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/robert/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

stack traceback:
        [C]: in function 'error'
        .../.lenv/lua/5.1.5/share/lua/5.1/espeon/util/shell.lua:16: in function 'shell'
        ...t/.lenv/lua/5.1.5/share/lua/5.1/espeon/util/exec.lua:9: in function 'exec'
        ...hare/lua/5.1/espeon/command/install_dependencies.lua:11: in function 'execute'
        ...bert/.lenv/lua/5.1.5/share/lua/5.1/espeon/espeon.lua:17: in function <...bert/.lenv/lua/5.1.5/share/lua/5.1/espeon/espeon.lua:1>
        ....1.5/lib/luarocks/rocks-5.1/espeon/1.10-0/bin/espeon:3: in main chunk
        [C]: ?

PIP is a mystery to me.


requestAnimationFrame broken on sdk > 23 (removeFrameCallback breaks postFrameCallback)

Environment
Provide version numbers for the following components (information can be retrieved by running tns info in your project folder or by inspecting the package.json of the project):

CLI: 8.3.3
Cross-platform modules: 8.3.5
Android Runtime: 8.3.1
Plugin(s):

  '@nativescript/android': '^8.3.1',
  '@nativescript/types': '^7.1.3',
  '@nativescript/webpack': '~5.0.8',
  '@nativescript-community/ble': '^3.0.13',
  '@nativescript/apple-sign-in': '^1.0.0',
  '@nativescript/appversion': '^2.0.0',
  '@nativescript/core': '^8.3.5',
  '@nativescript/facebook': '^2.1.3',
  '@nativescript/firebase-auth': 'portal:./ns-packages/firebase/packages/firebase-auth',
  '@nativescript/firebase-core': '^2.3.4',
  '@nativescript/firebase-crashlytics': '^2.3.4',
  '@nativescript/firebase-firestore': 'portal:./ns-packages/firebase/packages/firebase-firestore',
  '@nativescript/firebase-functions': 'portal:./ns-packages/firebase/packages/firebase-functions',
  '@nativescript/firebase-messaging': '^2.3.4',
  '@nativescript/geolocation': '^8.0.2',
  '@nativescript/google-signin': '^1.0.0',
  '@nativescript/iqkeyboardmanager': '^2.0.0',
  '@triniwiz/nativescript-stripe': '^8.0.3',
  'nativescript-vue-template-compiler': '^2.8.3',
  'nativescript-google-maps-sdk': 'workspace:*',
  'nativescript-ui-sidedrawer': '^9.0.3',
  'nativescript-vue': 'portal:./ns-packages/nativescript-vue',

Describe the bug
Passing a callback to removeFrameCallback prevents it from being invoked next time it is passed to postFrameCallback. Due to this, requestAnimationFrame can be used in a series only once. After we stop calling requestAnimationFrame, removeFrameCallback is called internally by the FPSCallback instance used by requestAnimationFrame. If we then call requestAnimationFrame again later (can be with a completely different callback), our callback only gets invoked once immediately but then not again after calling requestAnimationFrame from inside our callback.
To Reproduce
Sample project
https://stackblitz.com/edit/nativescript-stackblitz-templates-9ktwdn?file=app/components/Home.vue
Expected behavior
Button should animate each time it is pressed
Additional context
I made a work around for this issue by constructing and starting a new FPSCallback instance directly for my animations (so they have a different unique impl passed to post/removeFrameCallback as opposed to the single global one shared by the instance of FPSCallback used by requestAnimationFrame animation-frame/index.js). However, since doing this my app now seems to consistently crash with no output anywhere from immediately to a minute or two after constructing and starting the fpsCallback instance. With adb logcat --pid=$(adb shell pidof -s com.myappname.app) I was able to get a little crash info that was filtered out by the CLI but it still does not seem helpful:
11-05 18:38:09.942 23019 23019 E v8      : #
11-05 18:38:09.942 23019 23019 E v8      : # Fatal error in , line 0
11-05 18:38:09.942 23019 23019 E v8      : #
11-05 18:38:09.942 23019 23019 E v8      : ignored
11-05 18:38:09.942 23019 23019 E v8      : #
11-05 18:38:09.942 23019 23019 E v8      : #
11-05 18:38:09.942 23019 23019 E v8      : #
11-05 18:38:09.942 23019 23019 E v8      : #FailureMessage Object: 0x7fefb74a70
11-05 18:38:09.943 23019 23019 I v8      :
--------- beginning of crash
11-05 18:38:09.943 23019 23019 F libc    : Fatal signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0x6fa46a2560 in tid 23019 (m.myappname.app), pid 23019 (m.myappname.app)

Can you try the alpha version , thanks

Can you try the alpha version , thanks

Repro seems to be fixed in alpha, thanks  👍


how to use this library in simple project rather than in compose ?

is their any simpler way to use the library in simple project other than jetpack compose project ?

Compose is the future of Android development. There is no plans on supporting legacy views directly. Android does provide support for compose inside a View for those apps which have not yet migrated to compose.


the worker process's memory increase all the time

create stream stream_1(id bigint, ts timestamp without time zone);
create stream stream_2(id bigint,ts char(32));
create stream stream_3(id bigint,date char(16), time char(16));
create sequence  seq_1 start 1;
create continuous transform trans_1_2 as
select id as id,
to_char(ts,'yyyy-MM-dd hh24:mi:ss.ms')::char(32) as ts
from stream_1
then execute procedure pipeline_stream_insert('stream_2');
create continuous transform trans_1_3 as
select id as id,
to_char(ts,'yyyy-MM-dd')::char(16) as date,
to_char(ts,'hh24:mi:ss.ms')::char(16) as time
from stream_1 then
execute procedure pipeline_stream_insert('stream_3');
create continuous view cv_2 as select id,ts from stream_2;
create continuous view cv_3 as select date,time ,id from stream_3;
--create continuous view cv_2 as select count() from stream_2;
--create continuous view cv_3 as select count() from stream_3;
CREATE OR REPLACE FUNCTION public.sdf()
RETURNS void
AS $function$
BEGIN
raise notice 'sdf_lianggj';
end;
$function$  LANGUAGE plpgsql;
CREATE OR REPLACE FUNCTION umparse_trigger() RETURNS trigger AS $$
BEGIN
PERFORM sdf();
return new;
END;
$$ LANGUAGE plpgsql;
CREATE CONTINUOUS TRANSFORM trans_umparse AS
SELECT (new).ts FROM output_of('cv_2')
THEN EXECUTE PROCEDURE umparse_trigger();
--CREATE CONTINUOUS TRANSFORM trans_umparse1 AS
--SELECT ts FROM stream_2
--THEN EXECUTE PROCEDURE umparse_trigger();

pipelinedb version 0.9.5
when I execute the sql statement( insert into stream_1 values(nextval('seq_1'), now()); ), the worker process's momery increases all the time. Is there somethine I use wrongly or it's a bug, thanks

Hi @liang3rd,
Over what period of time did you notice this memory leak? So far I've been unable to reproduce it after running your insert statement for a few minutes:
while (true) do pipeline -c "insert into stream_1 (id, ts) SELECT nextval('seq_1'), now() FROM generate_series(1, 10000);"; done

@derekjn ,
sorry, I forgot a thing(maybe should change the configure file: log_min_messages = notice), so the notice can be printed out, and the memory inceases.

these are the sql file and shell script file.
sql.txt
sh.txt

Thanks @liang3rd! I still cannot reproduce a memory leak with the information given. It may be the case that your terminal is getting flooded with log messages and that is the source of the memory consumption. Can you determine which specific PipelineDB process or processes is showing increasing memory consumption (using ps or some other OS-level tool), and share your findings here?
Ideally we can get snapshots of memory usage for this process over time to show that it is indeed potentially leaking memory.

create stream stream_1(id bigint, ts timestamp without time zone);
create stream stream_2(id bigint,ts char(32));
create stream stream_3(id bigint,date char(16), time char(16));
create sequence seq_1 start 1;
create continuous transform trans_1_2 as
select id as id,
to_char(ts,'yyyy-MM-dd hh24:mi:ss.ms')::char(32) as ts
from stream_1
then execute procedure pipeline_stream_insert('stream_2');
create continuous transform trans_1_3 as
select id as id,
to_char(ts,'yyyy-MM-dd')::char(16) as date,
to_char(ts,'hh24:mi:ss.ms')::char(16) as time
from stream_1 then
execute procedure pipeline_stream_insert('stream_3');
create continuous view cv_2 as select id,ts from stream_2;
create continuous view cv_3 as select date,time ,id from stream_3;
CREATE OR REPLACE FUNCTION public.sdf()
RETURNS void
AS $function$
BEGIN
raise warning 'sdf_lianggj';
end;
$function$ LANGUAGE plpgsql;
CREATE OR REPLACE FUNCTION umparse_trigger() RETURNS trigger AS $$
BEGIN
PERFORM sdf();
return new;
END;
$$ LANGUAGE plpgsql;
CREATE CONTINUOUS TRANSFORM trans_umparse AS
SELECT (new).ts FROM output_of('cv_2')
THEN EXECUTE PROCEDURE umparse_trigger();

sql.txt
sh.txt
my test's steps:
1, init a database cluster;
2, execute the all "create" sql above;
3, change file name "sql.txt" to "test.sql", change file name "sh.txt" to "test.sh";
4, execute ./test.sh
maybe some details of the steps need to change according your test environment.
my test is on a virtual machine that has 2GB memory.
lsb_release -a
LSB Version:    :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
Distributor ID: RedHatEnterpriseServer
Description:    Red Hat Enterprise Linux Server release 5.8 (Tikanga)
Release:        5.8
Codename:       Tikanga

after about 15 minutes, I stop the "./test.sh" and use gdb attach the worker0 progress, and execute: call MemoryContextStats(TopMemoryContext)
the "ErrorContext" is large unusual most.
(gdb) info proc
process 13658
cmdline = 'pipelinedb: bgworker: worker0 [pipeline]   '
cwd = '/home/pipeline/pg095'
exe = '/usr/local/pg095/bin/pipelinedb'
TopMemoryContext: 138040 total in 16 blocks; 14872 free (32 chunks); 123168 used
PL/pgSQL function context: 8192 total in 1 blocks; 4864 free (0 chunks); 3328 used
PLpgSQL cast info: 0 total in 0 blocks; 0 free (0 chunks); 0 used
PLpgSQL cast cache: 8192 total in 1 blocks; 2664 free (0 chunks); 5528 used
PL/pgSQL function context: 24576 total in 2 blocks; 16832 free (3 chunks); 7744 used
CFuncHash: 8192 total in 1 blocks; 1640 free (0 chunks); 6552 used
Rendezvous variable hash: 8192 total in 1 blocks; 1640 free (0 chunks); 6552 used
PLpgSQL function cache: 24528 total in 2 blocks; 3712 free (0 chunks); 20816 used
Type information cache: 24472 total in 2 blocks; 3712 free (0 chunks); 20760 used
ipc_tuple_reader MemoryContext: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
ContExecutor Context: 16512 total in 2 blocks; 8040 free (2 chunks); 8472 used
QueryStateCxt: 57344 total in 3 blocks; 30808 free (4 chunks); 26536 used
QueryStateTmpCxt: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
QueryStateCxt: 57344 total in 3 blocks; 28760 free (2 chunks); 28584 used
QueryStateTmpCxt: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
QueryStateCxt: 57344 total in 3 blocks; 31920 free (2 chunks); 25424 used
QueryStateTmpCxt: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
QueryStateCxt: 122880 total in 4 blocks; 69920 free (3 chunks); 52960 used
QueryStateTmpCxt: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
QueryStateCxt: 57344 total in 3 blocks; 17816 free (4 chunks); 39528 used
QueryStateTmpCxt: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
ContQueryTransactionContext: 0 total in 0 blocks; 0 free (0 chunks); 0 used
ContQueryBatchContext: 8192 total in 1 blocks; 8160 free (0 chunks); 32 used
pzmq MemoryContext: 8192 total in 1 blocks; 6032 free (0 chunks); 2160 used
pzmq dests HTAB: 18888 total in 2 blocks; 3712 free (0 chunks); 15176 used
Operator class cache: 8192 total in 1 blocks; 1640 free (0 chunks); 6552 used
smgr relation table: 24576 total in 2 blocks; 9752 free (3 chunks); 14824 used
TransactionAbortContext: 32768 total in 1 blocks; 32736 free (0 chunks); 32 used
Portal hash: 8192 total in 1 blocks; 1640 free (0 chunks); 6552 used
PortalMemory: 0 total in 0 blocks; 0 free (0 chunks); 0 used
Relcache by OID: 24576 total in 2 blocks; 12752 free (2 chunks); 11824 used
CacheMemoryContext: 1335800 total in 16 blocks; 403424 free (17 chunks); 932376 used
CachedPlan: 1024 total in 1 blocks; 64 free (0 chunks); 960 used
CachedPlanSource: 3072 total in 2 blocks; 1688 free (0 chunks); 1384 used
CachedPlanQuery: 3072 total in 2 blocks; 2000 free (1 chunks); 1072 used
SPI Plan: 1024 total in 1 blocks; 808 free (0 chunks); 216 used
cv_2: 7168 total in 3 blocks; 3360 free (0 chunks); 3808 used
pg_db_role_setting_databaseid_rol_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_user_mapping_user_server_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_user_mapping_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_type_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_type_typname_nsp_index: 3072 total in 2 blocks; 1968 free (0 chunks); 1104 used
pg_ts_template_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_ts_template_tmplname_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_ts_parser_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_ts_parser_prsname_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_ts_dict_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_ts_dict_dictname_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_ts_config_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_ts_config_cfgname_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_ts_config_map_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_transform_type_lang_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_transform_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_tablespace_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_statistic_relid_att_inh_index: 3072 total in 2 blocks; 1672 free (1 chunks); 1400 used
pg_replication_origin_roname_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_replication_origin_roiident_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_range_rngtypid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_proc_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_proc_proname_args_nsp_index: 3072 total in 2 blocks; 1672 free (1 chunks); 1400 used
pipeline_stream_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pipeline_stream_relid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pipeline_query_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pipeline_query_matrelid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pipeline_query_relid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pipeline_query_id_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pipeline_combine_transfn_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pipeline_combine_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_opfamily_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_opfamily_am_name_nsp_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_operator_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_operator_oprname_l_r_n_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_namespace_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_namespace_nspname_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_language_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_language_name_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_foreign_table_relid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_foreign_server_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_foreign_server_name_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_foreign_data_wrapper_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_foreign_data_wrapper_name_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_event_trigger_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_event_trigger_evtname_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_enum_typid_label_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_enum_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_default_acl_role_nsp_obj_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_conversion_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_constraint_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_conversion_name_nsp_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_conversion_default_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_collation_oid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_collation_name_enc_nsp_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_opclass_am_name_nsp_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_cast_source_target_index: 3072 total in 2 blocks; 1968 free (0 chunks); 1104 used
pg_auth_members_role_member_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_attribute_relid_attnam_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_amop_fam_strat_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_amop_opr_fam_index: 3072 total in 2 blocks; 1728 free (1 chunks); 1344 used
pg_aggregate_fnoid_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_auth_members_member_role_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_authid_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_authid_rolname_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_database_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_database_datname_index: 1024 total in 1 blocks; 144 free (0 chunks); 880 used
pg_trigger_tgrelid_tgname_index: 1024 total in 1 blocks; 8 free (0 chunks); 1016 used
pg_rewrite_rel_rulename_index: 3072 total in 2 blocks; 1968 free (0 chunks); 1104 used
pg_amproc_fam_proc_index: 3072 total in 2 blocks; 1672 free (1 chunks); 1400 used
pg_opclass_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_index_indexrelid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
pg_attribute_relid_attnum_index: 3072 total in 2 blocks; 1968 free (0 chunks); 1104 used
pg_class_oid_index: 1024 total in 1 blocks; 88 free (0 chunks); 936 used
WAL record construction: 49768 total in 2 blocks; 6576 free (0 chunks); 43192 used
PrivateRefCount: 8192 total in 1 blocks; 3712 free (0 chunks); 4480 used
MdSmgr: 8192 total in 1 blocks; 7640 free (2 chunks); 552 used
ident parser context: 0 total in 0 blocks; 0 free (0 chunks); 0 used
hba parser context: 7168 total in 3 blocks; 3920 free (1 chunks); 3248 used
LOCALLOCK hash: 8192 total in 1 blocks; 1640 free (0 chunks); 6552 used
Timezones: 83480 total in 2 blocks; 3712 free (0 chunks); 79768 used
Postmaster: 8192 total in 1 blocks; 7776 free (5 chunks); 416 used
ErrorContext: 147030016 total in 17948 blocks; 83136 free (8 chunks); 146946880 used

@liang3rd this is fixed in master. There was a memory leak for allocations being made for log messages, which aren't expected to be made for every event written to a stream. Technically it was a bug, but it was only showing up because the test function is doing so much logging. You're not going to see this issue once you implement that function for actual use, assuming it doesn't log something on every execution :)
Thanks for reporting!


Build base_url correctly if SERVER_ADDR is IPv6

Now that base_url is being calculated using SERVER_ADDR instead of HTTP_HOST, it no longer works on IPv6 hosts. This fixes the problem by surrounding literal IPv6 addresses with proper [square brackets]. IPv4 addresses are not affected.
http://::1/some/controller ← this is not valid
http://[::1]/some/controller ← this is valid

Note that this still doesn’t work if the server is not running on the default port number (a problem affects both IPv4 and IPv6). In theory we could fix this by using $_SERVER['SERVER_PORT'], but it is not safe to do so, according to the PHP docs:

Under the Apache 2, you must set UseCanonicalName = On, as well as UseCanonicalPhysicalPort = On in order to get the physical (real) port, otherwise, this value can be spoofed and it may or may not return the physical port value. It is not safe to rely on this value in security-dependent contexts.

In addition to those, you may as well just strpos() for a colon character instead of using filter_var().


Continuous integration using AppVeyor

To automate the packing and releasing of new versions, I propose to setup continuous integration using AppVeyor.
For this to work on this repository, the secure GitHub authorization token used near the bottom of the appveyor.yml file needs to be updated to one coming from this repository. Also, the status badge in the README.md file must reflect the AppVeyor project associated with this repository.
For this PR, I have setup a project myself.
If you would prefer to host the AppVeyor project, you need to create your own AppVeyor project and the two modifications above must be carried out. Or I can host the AppVeyor project but, in order to push releases to this repository, the secure authorization token from this repository must be specified in the file, instead of mine.

It seems the binaries are included in the source (msi). Is it expected?

The msi files are bootstrapped files that never change based on the name and metadata of the layout. The actual DLL is built dynamically and is put in a folder based upon the target CPU architecture. Therefore, there is no harm in putting those files in the source code.
Building the layout DLLs with MSKLC does not work in an unattended fashion so I has to rely on using the underlying kbdutool.exe program.
In fact, the benefit of using the low-level kbdutool.exe instead of the high-level msklc.exe tool to build the layout DLLs is that MSKLC is limited whereas the kbdutool.exe supports chained dead-keys that I intend to make use of to implement missing extended characters.

I’m using the procedure outlined here:
http://accentuez.mon.nom.free.fr/Clavier-CreationClavier.php

I just created a similar branch here with all your changes included, then edited the files as recommended.
Perhaps you could update your PR with the new values from my branch, so I could merge your PR as-is? I will then delete my local branch.
I did not review the method you set up to decide when to deploy in the release tab. Something seems to be related to the tagging of the sources, but I did not read the documentation yet.

Thank you very much.
To be clear there is a continuous build for each build on the master branch. This is used to check the build.
When tagging the master branch with a version, then a build and a release are performed.
At the moment, this allows to create a release only when explicitly required by a human.
This is very configurable so please let me know what you would like.


Implicitly wait fix to test

#136
Added implicitly_wait to the test before interacting with an element. This will not make the test slower because the test will wait until the element is interactable for IMPLICIT_WAIT seconds.
I have:

[X] Set target branch to the correct branch, usually dev.
[X] Rebased source branch from the target branch.
[X] Ensured code is formatted and linted.
[X] Cleaned up git history.
[X] Ensured commit messages describe what was changed and why.
[X] Ran tests locally after rebasing and checked output.

The issue should be fixed now.


experiment: enable module record builder

Experiment to see what effects turning on module record builder has on semantic analysis runtime.

https://github.com/web-infra-dev/oxc/actions/runs/5722249045

Oh we need to turn it on here as well: https://github.com/web-infra-dev/oxc/blob/98e4240fe153fee106ed700338f2517f76b02b80/tasks/benchmark/src/main.rs#L115

Oh we need to turn it on here as well:
https://github.com/web-infra-dev/oxc/blob/98e4240fe153fee106ed700338f2517f76b02b80/tasks/benchmark/src/main.rs#L115

https://github.com/web-infra-dev/oxc/actions/runs/5730728132


AccessViolationException when logger and ares is active

What version of gRPC and what language are you using?
gRPC 1.18.0 for C#
What operating system (Linux, Windows, …) and version?
Windows 18.03
What runtime / compiler are you using (e.g. python version or version of gcc)
Visual Studio 2017 / MSBuild
What did you do?
using Grpc.Core;
using Grpc.Core.Logging;
using Helloworld;
using System;
using System.IO;
using System.Threading.Tasks;

namespace Crashtest
{
    class Program
    {
        public static void Main()
        {
            string hostname = Environment.MachineName; // any non-localhost
            int port = 8010;

            Environment.SetEnvironmentVariable("GRPC_TRACE", "cares_resolver");
            Environment.SetEnvironmentVariable("GRPC_VERBOSITY", "DEBUG");
            Environment.SetEnvironmentVariable("GRPC_DNS_RESOLVER", "ares");

            GrpcEnvironment.SetLogger(new TextWriterLogger(TextWriter.Synchronized(File.CreateText("test.txt"))));

            var server = new Server
            {
                Services = { Greeter.BindService(new HelloWorldImpl()) },
                Ports = { new ServerPort(hostname, port, ServerCredentials.Insecure) }
            };
            server.Start();

            var client = new Greeter.GreeterClient(new Channel(hostname, port, ChannelCredentials.Insecure));
            var result = client.SayHello(new HelloRequest {Name = "Tester"}); // This will throw in GrpcThreadPool.RunHandlerLoop
        }

        internal class HelloWorldImpl : Greeter.GreeterBase
        {
            public override Task<HelloReply> SayHello(HelloRequest request, ServerCallContext context)
            {
                return Task.FromResult(new HelloReply {Message = "Hello " + request});
            }
        }
    }
}

What did you expect to see?
The example should run fine and log messages to test.txt.
What did you see instead?
An AccessViolationException will be thrown on the client call.
Anything else we should know about your project / environment?
It works fine when not setting GRPC_DNS_RESOLVER=ares.
The cares_resolver tracer flag is missing in https://github.com/grpc/grpc/blob/master/doc/environment_variables.md but found it in the code base. The error also appears when using all as tracer.

Thanks for filing. Are you able to paste the logs here, including the exception?

It‘s sadly not flushing the full log and since it’s in a pooled thread, I was not able to catch it and close the application gracefully.

I haven't repro'd the access violation.
However, I can repro a name resolution - in any case one thing that this bug makes apparent is that c-ares can't resolve Environment.MachineName.

Ok, I can repro an access violation, specifically when I'm:
a) running under `GRPC_TRACE=all'
b) Configuring the grpc logger to log to a file, e.g.:
GrpcEnvironment.SetLogger(new TextWriterLogger(TextWriter.Synchronized(File.CreateText("test.txt"))));

Logging to another endpoint worked in one try. Haven’t tested it repeatedly. Even with this constellation, it’s not occurring everytime. But pretty regularly. It seems to be a combination of TextWriterLogger and the ares resolver. Even when using GRPC_TRACE=all, this only happens with GRPC_DNS_RESOLVER=ares.

Yeah, that "DNS resolution failure" that I thought I was encountering was actually just a subtle bug, described in https://github.com/grpc/grpc/pull/18084 - WIP fixing this.

FTR, regarding the "access violation": this too appears to be caused by same the fact that we make incorrectly error out of a DNS query because we a stale WSA socket error code comparison. When we do this, we initiate a WSA operation on a socket but don't call grpc_socket_notify_on_read. So when we then destroy the socket, we'll not realize  that it has an ongoing I/O operation and so prematurely free it.

The fix for this was backported to 1.19.x in https://github.com/grpc/grpc/pull/18092, so it should be released in the 1.19.0 release soonish


26 January 2024 - TraderX Meeting Agenda

Date
26 January 2024 - 8 am EST / 1 pm GMT
Previous Meeting
12 January 2024 - TraderX Meeting Agenda
Untracked attendees

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[x] Convene & roll call (5mins)
[x] Display FINOS Antitrust Policy summary slide
[x] Review Meeting Notices (see above)
[x] Approve past meeting minutes ( #79 )
[ ] Introductions
[ ] Internal corporate adoption/development of TraderX
[ ] Review Priority issues
[ ] Hack day opportunities
[ ] AOB, Q&A & Adjourn (5mins)

Discussed Points

Meeting cadence. Agreed to cancel up to Thursday the day before, but keep the twice monthly format for now.
@tomhealey-icma Raised the issue of how we're going to do releases, versioning scheme. Would be good to decide if we do releases, and if so, what the purpose of releasing would be.

Action Items

[ ] MS ( @DovOps )  to share experience (next meeting) on running local fork of TraderX with internal modifications
[ ] (See next-meeting labels in Issues)
[ ] @karlmoll to follow-up internally at FINOS around #29  and other opportunities for TraderX to be promoted at other project meetings (guest presenter, etc...)
[ ] @DovOps  to open more tech-debt issues which are good for new contributors to get involved (e.g. test coverage, holistic JS stack upgrades, etc)
[ ] @DovOps to add Maintainers List,  and Roadmap to the README (@karlmoll  to provide example)
[ ] @psmulovics  - Bring update back from TSC meeting about project adoptive ownership... / involvement from the TSC
[ ] @DovOps  Create aspirational roadmap (even without dates) , including top priority integrations and hardening of the project- with rationale, etc to help @karlmoll with recruiting interested contributors. -- Essentially, a MVP of roadmap

Zoom Details

https://zoom.us/j/96264933811?pwd=d2VmSkdudDRXZytPclBRblc4eUlEZz09
Meeting ID: 962 6493 3811
Passcode: 532953

Join by Phone

Find your local number: https://zoom.us/u/adl5rhui4P

@maoo / FINOS

Karl Moll / FINOS

Peter Smulovics / Morgan Stanley

Mimi Flynn / Morgan Stanley

Tom Healey/ICMA

Cliff Tiltman - Morgan Stanley

Matthew Bain / Morgan Stanley

Draft PR as discussed in todays meetup - https://github.com/finos/traderX/pull/102


Plural suffix is missing

It inserting "material-icon" instead of "material-icons" class.
Correct: aspect_ratio
Now: aspect_ratio
Plural suffix is missing. (s)

I know, but the official site uses "material-icons". I think it would be better to come as "material-icons" by default.


Refactor assertions: Move node patterns into subclasses

This way we can remove the metaprogramming of def_node_matcher and public_send, making the cop simpler.

Before submitting the PR make sure the following are checked:

[ ] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[ ] Added tests.
[ ] Updated documentation.
[ ] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[ ] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

Does this still apply?


Error with HHVM 3.9.1 - log4cplus

There appears to be some kind of race condition happening with the extension / the extension's usage of the SDK. I can't tell if the bug is in the SDK itself or in the extension's usage of it, but running HHVM from the CLI with the extension enabled gives an error every so often:
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm -- test.php
foo
log4cplus:ERROR Re-initializing default context after it has already been destroyed.
The memory will be leaked.
log4cplus:ERROR No appenders could be found for logger (com.newrelic.CollectorClientLib).
log4cplus:ERROR Please initialize the log4cplus system properly.
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm test.php
foo
ubuntu@qa-newrelic:~$ hhvm -- test.php
foo
log4cplus:ERROR Re-initializing default context after it has already been destroyed.
The memory will be leaked.
log4cplus:ERROR No appenders could be found for logger (com.newrelic.CollectorClientLib).
log4cplus:ERROR Please initialize the log4cplus system properly.

test.php is a simple script that just has
<?php
echo "foo\n";

Here is the output from run-test:
ubuntu@dev-hhvm:/mnt/packager/hhvm-newrelic-ext/hhvm-newrelic-ext (master)$ ./run-test test
Running 1 tests in 1 threads (0 in serial)

FAILED: test/test.php
014+ datastore_segment_id: 3
015+ datastore_end_error_code: 0
014- datastore_segment_id: 0
015- datastore_end_error_code: -196610
017+ end_error_code: 0
017- end_error_code: -65537

1 tests failed
(╯°□°）╯︵ ┻━┻

See the diffs:
cat test/test.php.diff

For xargs, list of failures is available using:
cat /tmp/test-failureszWgkHL

Run these by hand:
/usr/bin/hhvm --config ./php.ini -c  -vEval.EnableArgsInBacktraces=true -vEval.EnableIntrinsicsExtension=true -vRepo.Local.Mode=-- -vRepo.Central.Path=/mnt/packager/hhvm-newrelic-ext/hhvm-newrelic-ext/hphp/hhvm/verify.hhbc -vEval.Jit=tr
ue      -vResourceLimit.CoreFileSize=0    --file 'test/test.php'

Re-run just the failing tests:
./run-test --threads 1 'test/test.php'

My php.ini (I had to modify the run-test command that generated the command to include it otherwise the extension wasn't loaded) looks like this:
hhvm.env_variables[NEWRELIC_LICENSE_KEY] = YOUR_KEY_HERE
hhvm.env_variables[NEWRELIC_APP_NAME] = YOUR_APP_NAME
hhvm.dynamic_extensions[newrelic]=newrelic.so
hhvm.jit_enable_rename_function=true

Thus it loads the newrelic.so file that I've just built in my build directory, compiled against HHVM 3.9.1 on Ubuntu 14.0.4 Trusty.

New Relic has confirmed with me that there is a bug in the SDK itself. Closing this issue as a result for the time being.