etcdctl: show warning if ETCDCTL_API is not set

FIXES #7385

output
$  bin/etcdctl
WARNING:
   Environment variable ETCDCTL_API is not set; defaults to etcdctl v2.
   Set environment variable ETCDCTL_API=3 to use etcdctl v3.

NAME:
   etcdctl - A simple command line client for etcd.
...

$  bin/etcdctl -h
WARNING:
   Environment variable ETCDCTL_API is not set; defaults to etcdctl v2.
   Set environment variable ETCDCTL_API=3 to use etcdctl v3.

NAME:
   etcdctl - A simple command line client for etcd.
...

$  bin/etcdctl set foo bar
 WARNING:
    Environment variable ETCDCTL_API is not set; defaults to etcdctl v2.
    Set environment variable ETCDCTL_API=3 to use etcdctl v3.

 bar

I think the decision was to add a comment in the -h output. If you want to interact v2 API specify xxx; if you want to interact with v3 API...
/cc @heyitsanthony

Huh? I thought this warning was going to be in --help for ctlv2?

@heyitsanthony @xiang90 my bad. I'll add it to --help  for ctlv2.

new output
$ bin/etcdctl -h
NAME:
   etcdctl - A simple command line client for etcd.

WARNING:
   Environment variable ETCDCTL_API is not set; defaults to etcdctl v2.
   Set environment variable ETCDCTL_API=3 to use v3 API or ETCDCTL_API=2 to use v2 API.

USAGE:
   etcdctl [global options] command [command options] [arguments...]
...

All fixed. PTAL

fixed the newline issue. PTAL

rebase on master?

rebased and no conflict.

lgtm

Unrelated proxy-ci failure
--- FAIL: TestWatchErrConnClosed (0.11s)
	watch_test.go:616: expected grpc: the client connection is closing, got context canceled

Unrelated semaphoreci failure
=== RUN   ExampleKV_getWithRev
2017-03-01 19:56:36.705608 I | etcdserver/api/v3rpc: Failed to dial localhost:7046820601300917340: grpc: the connection is closing; please retry.
2017-03-01 19:56:36.705711 I | etcdserver/api/v3rpc: Failed to dial localhost:18192653325062318460: grpc: the connection is closing; please retry.
2017-03-01 19:56:36.835185 I | raft: 5c6423fcc50f5227 is starting a new election at term 2
2017-03-01 19:56:36.835323 I | raft: 5c6423fcc50f5227 became candidate at term 3
2017-03-01 19:56:36.835409 I | raft: 5c6423fcc50f5227 received MsgVoteResp from 5c6423fcc50f5227 at term 3
2017-03-01 19:56:36.835511 I | raft: 5c6423fcc50f5227 [logterm: 2, index: 25] sent MsgVote request to 250396c2f3f7f913 at term 3
2017-03-01 19:56:36.835639 I | raft: 5c6423fcc50f5227 [logterm: 2, index: 25] sent MsgVote request to 509c8d4ffbeda3ba at term 3
2017-03-01 19:56:36.835748 I | raft: raft.node: 5c6423fcc50f5227 lost leader 509c8d4ffbeda3ba at term 3
2017-03-01 19:56:36.836355 I | raft: 509c8d4ffbeda3ba [logterm: 2, index: 25, vote: 509c8d4ffbeda3ba] ignored MsgVote from 5c6423fcc50f5227 [logterm: 2, index: 25] at term 2: lease is not expired (remaining ticks: 6)
2017-03-01 19:56:36.836418 I | raft: 250396c2f3f7f913 [term: 2] received a MsgVote message with higher term from 5c6423fcc50f5227 [term: 3]
2017-03-01 19:56:36.836533 I | raft: 250396c2f3f7f913 became follower at term 3
2017-03-01 19:56:36.836637 I | raft: 250396c2f3f7f913 [logterm: 2, index: 25, vote: 0] cast MsgVote for 5c6423fcc50f5227 [logterm: 2, index: 25] at term 3
2017-03-01 19:56:36.836729 I | raft: raft.node: 250396c2f3f7f913 lost leader 509c8d4ffbeda3ba at term 3
2017-03-01 19:56:36.837319 I | raft: 5c6423fcc50f5227 received MsgVoteResp from 250396c2f3f7f913 at term 3
2017-03-01 19:56:36.837379 I | raft: 5c6423fcc50f5227 [quorum:2] has received 2 MsgVoteResp votes and 0 vote rejections
2017-03-01 19:56:36.837477 I | raft: 5c6423fcc50f5227 became leader at term 3
2017-03-01 19:56:36.837532 I | raft: raft.node: 5c6423fcc50f5227 elected leader 5c6423fcc50f5227 at term 3
2017-03-01 19:56:36.838459 I | raft: raft.node: 250396c2f3f7f913 elected leader 5c6423fcc50f5227 at term 3
2017-03-01 19:56:36.838569 I | raft: 509c8d4ffbeda3ba [term: 2] received a MsgApp message with higher term from 5c6423fcc50f5227 [term: 3]
2017-03-01 19:56:36.838629 I | raft: 509c8d4ffbeda3ba became follower at term 3
2017-03-01 19:56:36.838691 I | raft: raft.node: 509c8d4ffbeda3ba changed leader from 509c8d4ffbeda3ba to 5c6423fcc50f5227 at term 3
2017-03-01 19:56:37.711252 I | context deadline exceeded
FAIL	github.com/coreos/etcd/clientv3	1.692s


Creating User Authentication UI(Login and Signup) with Compose Desktop

Topic Suggestion
[Kotlin] Creating User Authentication UI(Login and Signup) with Compose Desktop
Proposed title of article
Creating User Authentication UI(Login and Signup) with Compose Desktop
Proposed article introduction
With Compose Multiplatform, one can create a very interesting layout using Kotlin and Jetpack compose for Desktop applications. Having a good user authentication layout attracts users to sign in to your system easily. Compose desktop has made this achievable with a lot of ease unlike SWINGS in Java which requires one to write lots of code. This tutorial will help the reader to understand how to use Compose Desktop to create well-structured desktop applications just like in Android.
Key takeaways

How to use Compose Desktop.
How to implement Layout designs using Compose Desktop.
Compose desktop design patterns

Article quality
This article is going to be unique since Compose Desktop is a new technology that is just coming into existence. it is going to help the learner to get started with Compose Desktop. It will help the learner to also migrate from using the tiresome SWING library in Java.
References
Compose Desktop

Compose for Desktop seems like a good topic - since it is just coming out. Let's ensure that it adds value to the community. Thanks


Failing to start service with label match for hostname

Based on the previous discussion, I am attaching a hostname label to an host, then trying to start the service. it is stuck in activating state. Logs imply that it is failing to meet scheduling criteria.
I get the following error from the rancher server logs:
2016-01-22 13:35:47,041 ERROR [79906ea2-0066-4603-b8a0-b6d6d370674a:1853] [instance:123] [instance.start->(InstanceStart)->instance.allocate->(InstanceAllocate)] [] [cutorService-24] [c.p.a.e.i.AllocatorEventListenerImpl] No allocator handled [EventVO [id=915175e1-531c-434e-9d88-52adacdab0e0, name=instance.allocate, previousNames=null, replyTo=reply.3150290857929820295, resourceId=123, resourceType=instance, publisher=null, transitioning=null, transitioningMessage=null, transitioningInternalMessage=null, previousIds=null, data={}, time=Fri Jan 22 13:35:47 UTC 2016, listenerKey=null, transitioningProgress=null]]
2016-01-22 13:35:47,045 ERROR [79906ea2-0066-4603-b8a0-b6d6d370674a:1853] [instance:123] [instance.start->(InstanceStart)->instance.allocate] [] [ecutorService-7] [c.p.e.p.i.DefaultProcessInstanceImpl] Unknown exception io.cattle.platform.eventing.exception.EventExecutionException: Failed to find a placement
2016-01-22 13:35:47,045 ERROR [79906ea2-0066-4603-b8a0-b6d6d370674a:1853] [instance:123] [instance.start->(InstanceStart)] [] [ecutorService-7] [i.c.p.process.instance.InstanceStart] Failed to Scheduling for instance [123]
2016-01-22 13:36:12,696 ERROR [31fa7ded-b4c8-4cee-a017-fb418d02540b:1859] [instance:124] [instance.start->(InstanceStart)->instance.allocate->(InstanceAllocate)] [] [cutorService-26] [c.p.a.e.i.AllocatorEventListenerImpl] No allocator handled [EventVO [id=89213756-f980-4bc7-881f-8345f0c06fec, name=instance.allocate, previousNames=null, replyTo=reply.3150290857929820295, resourceId=124, resourceType=instance, publisher=null, transitioning=null, transitioningMessage=null, transitioningInternalMessage=null, previousIds=null, data={}, time=Fri Jan 22 13:36:12 UTC 2016, listenerKey=null, transitioningProgress=null]]
2016-01-22 13:36:12,700 ERROR [31fa7ded-b4c8-4cee-a017-fb418d02540b:1859] [instance:124] [instance.start->(InstanceStart)->instance.allocate] [] [ecutorService-4] [c.p.e.p.i.DefaultProcessInstanceImpl] Unknown exception io.cattle.platform.eventing.exception.EventExecutionException: Failed to find a placement

(repeats a few times)
The configuration is as follows:

And the host itself in the same environment (notice the label matches):

The relevant lines from the compose.ml:
  labels:
    io.rancher.scheduler.affinity:host_label: hostname='bm03.pfs.co.il'

Why is it failing to schedule?
Just in case it was the single-quotes, I tried cloning the service and removing the single quotes from the hostname in the label, and then removed from the label on the host itself. Same problem.

Some updates:

I tried it on a separate Rancher server install, it worked just fine.
I tried it with an arbitrary label, tt_pool=a. It failed as well, but worked on the other Rancher instance.
I checked the service and the host in "View API", they show the labels correctly.

I could just reinstall Rancher, but I want a clean understanding of why it is failing.

Help?

What version are you running again? Also, is it just this host? I wasn't sure if "other Rancher instance"  meant a whole other setup or another host.
Have you tried adding another host with a host label to your existing Rancher setup to see if that works or fails.
Not sure what would have caused the scheduler to fail.

This was true both with any recent versions we tried. Right now, we are at 0.56.0 (not running CoreOS, so didn't bother upgrading to 0.56.1 yet).
"other Rancher instance" does mean whole other setup. I basically have 2 independent Rancher server setups, each with 2 hosts, both upgraded to 0.56. With one setup, host_label affinity works as advertised. On the other entire setup, it fails.  All of the above worked on one setup, failed on the other.
I am not sure either, but give me some steps, let's step through and see where it is failing.
As for adding another host and trying labels there.... you win!
I added another host (bm02), cloned the service, added various labels (I tried both pool=a and hostname=bm02 and hostname=bm02.pfs.co.il), and all worked.
So this means something is messed up with how that particular host (or its labels) are being viewed. What can I do to resolved it?

Any chance this is your host that has the incorrect IP?

Any chance this is your host that has the incorrect IP?

I don't understand.

The host that you have the scheduling issues, is it the same host that you have in your upgraded setup that's having connectivity issues (and it looks like it has the incorrect IP registered in the UI)?
I'm merging two threads of issues together. FYI, I'm trying to re-test what happens when you re-run the rancher/agent command with a new IP to confirm what will happen.

Ah! No, no it isn't. The one where I am running the ipsec tests is a separate rancher install. This is the install where labelling and scheduling work just fine.

@deitch Is this host still giving you issues? It sounds like it was something with that host as you were able to schedule other hosts.

Hmm, I haven't looked in a bit of time, but I know it is working now. I don't know if that was post upgrade of Rancher, or a clean install of the service node.
Let's consider it closed. If it comes up again, I will reopen.

I do have the same problem.
It does not happen everytime but once in a while.
I'm restarting stack services using rancher compose and get this error at activation:

service.activate.exception | Failed to allocate instance [container:1i1357]: Bad instance  [container:1i1357] in state [error]: Allocation failed: needs host with label host: mob-1
Sometimes, it eventually manage to restart everything but rancvher-compose does not wait long enough.
Using rancher-1.6.11.
Any idea?


fix: artifact subdir error when using volumeMount

Fixes https://github.com/argoproj/argo-workflows/issues/12174
I tried contacting original author from https://github.com/argoproj/argo-workflows/pull/12200 but met no success
We want to expedite this fix and have this ready for the next patch release
Motivation

To make sure if an artifact contains a subdir and is mounted using volume claim, the workflow runs without failing.
VolumeMount is necessary if the user wants to use ephemeral storage.
Modifications
Make sure the executor creates a subdirectory before downloading files

Verification

Added new e2e test -> e2e failed (verified original issue)
Added code change -> e2e succeed (verified fixed the issue)

Hey @tczhao - I'm not sure how much you plan on contributing going forward but in case you're interested, I wanted to link you to this just in case you haven't seen it :)

Hey @tczhao - I'm not sure how much you plan on contributing going forward but in case you're interested, I wanted to link you to this just in case you haven't seen it :)

Hi @juliev0, thanks for letting me know.
I should sign up for that.


Decorate only requests with clients

Currently, we decorate both the app and the request with the clients.
We should decorate only requests, so that we are sure we can correlate calls between services.
This is breaking change, so it should shipped before 1.0.0

Should be enough to just remove: https://github.com/platformatic/platformatic/blob/main/packages/client/index.js#L378
...but we need to update documentation too.


[bug] ref_indices contains values

https://github.com/Jfortin1/neuroCombat/blob/cab18534be578779fda3ac1440c029f6450f8cbf/neuroCombat/neuroCombat.py#L95
The following line solves the bug:
ref_indices = np.argwhere(covars[:, batch_col] == ref_batch).squeeze()

Fixed in https://github.com/Jfortin1/neuroCombat/commit/77d526b5118f466c33b5325a0f7e300880b4b7c4. Thanks!


Please provide your ORCID

Hi !
in order to publish your research in the Sci-GaIA Open Access Repository, you need to have an ORCID. Please respond to this ticket with your ORCID : e.g. orcid.org/0000-0002-6607-7145
If you do not have one, please sign up at https://orcid.org/register

Hello - could you respond with your ORCID please ?

Here is mine
orcid.org/0000-0002-6290-1707
github account name is bsegun
On Fri, Nov 25, 2016 at 3:08 PM, Bruce Becker<EMAIL_ADDRESS>wrote:

Hello - could you respond with your ORCID please ?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/sci-gaia/LagosHackfest/issues/30#issuecomment-262963683,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWbdhVU7rMIDIfwue1GoyJXWSi8BiDwEks5rBuvmgaJpZM4K6lKK
.

--

Professor Benjamin Aribisala, PhD (Birmingham, UK)
Professor of Computer Science
Head of Department, Computer Science Department
Lagos State University
http://www.csc.lasu.edu.ng/about-us/hod.html
<EMAIL_ADDRESS>Chairman, ICT Committee
Lagos State University


Add AAD authentication for Managed Instance

Issue Type: Feature Request
For Managed Instance important scenario is connect with AAD account so please consider adding this. Min bar is AAD user with password like in SSMS.
SQL Operations Studio version: sqlops 0.31.4 (e026ab85a72c190cc4ccc834503aa9fe36dd6407, 2018-07-18T02:14:21.826Z)
OS version: Windows_NT x64 10.0.17134

@jovanpop-msft thanks for suggestion.  We're tracking this request in https://github.com/Microsoft/sqlopsstudio/issues/13.  Currently we're waiting on AAD support in the .Net Core SqlClient driver to surface this connection option in the UI.


Query SN-like candidates in last 14 days - 1054 (42S22): Unknown column 'objects.latestrmag' in 'field list'

The query at https://lasair-iris.roe.ac.uk/query/202/ returns the error '1054 (42S22): Unknown column 'objects.latestrmag' in 'field list'' . latestmag does not appear in the schema at https://lasair-iris.roe.ac.uk/schema should the field be rmag though it is not clear if this is the latest value or a value at time past.

That is correct, the latest magnitudes are "gmag" and "rmag"


Add Discord link

All Submissions:

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?

@alexrudall I get a "Discord invite is invalid" when I click on the link.


How to make this pod persistent, thank you.

+1

local-cluster                 bash      NodePort   <IP_ADDRESS>:32517   Complete   29m

CloudShell

why use deploy to owner this cr . use job has some disadvantage

@wanminny you can set the ttl to CloudShell CR, this is lifetime of pod.

why not use deploy to owner this cr . use job has some disadvantage

@wanminny I'm curious are there any scenarios that require a permanent cloudshell?


Multiline support for rust?

Before I fiddle around / maybe submit a PR for /** */ style rust comments, I just want to make sure there wasn't a reason it wasn't already implemented (given the rust single line style is).
Thanks!

No reason, I just overlooked it, there may be others missing too. Feel free to submit a PR or I can do it tomorrow when I'm free. It's pretty straightforward.

63c5d9ffda731c7b7885bd15ae469413dc21b6d7


Refactor: clean Repository and Runtimes structs

moved HealthEndpoints and BuildConfig structs to function.go
moved Template to repository.go so Repository, Runtime and Template are together.
removed fields that were leaking details from Repository and Runtime

/lgtm
/hold for someone else to pull the merge trigger

@lance @lkingland please re-LGTM

/unhold

/lgtm


Release notes should clearly discern between edge and stable channel

File: release-notes/docker-ce.md, CC @johndmulhausen
Like most of the end users I'm on the stable channel, and today I got the 17.06.2 update from the apt repository.
I checked the release notes and found that the proxy support has been enhanced, but unfortunately I hadn't noticed the version mismatch.. After a few attempts, I realized that it was not gonna work, as that feature belongs to the 17.07 which is only available on the edge channel, while I'm on the stable, like I said.
So I think that the release notes document should clearly discern the release notes for the different channels in two separate sections of the document.
BTW, please note that the release notes for 17.06.2-ce are missing.

This was fixed. :)


sl-date-range-picker

Your picker is throwing an exception because it sets the date picker change handlers to startDateChange and endDateChange actions that not defined on the sl-date-range-picker itself. I'm guessing that this component hasn't been used recently? :)
Uncaught Error: <items@component:sl-date-range-picker::ember1453> had no action handler for: startDateChange

For anyone using ember-cli running into this issue, just create the correct template
app/templates/components/sl-date-range-picker.hbs file to override the existing one:
{{#if label}}
    {{label}}
{{/if}}

    {{sl-date-picker
        class="sl-daterange-start-date col-md-6"
        endDate=latestStartDate
        placeholder=startDatePlaceholder
        startDate=minDate
        value=startDateValue
        inputElementIdBinding="inputElementId"
    }}

    {{sl-date-picker
        class="sl-daterange-end-date col-md-6"
        endDate=maxDate
        placeholder=endDatePlaceholder
        startDate=earliestEndDate
        value=endDateValue
    }}

{{#if helpText}}

{{helpText}}

{{/if}}

It's odd that I'm not seeing any errors at all from this... I went ahead and removed the change bindings, as they're clearly not needed anyway.


Abseil test failure on AIX due to some linking error(terminate getting called)

Thank you for your contribution to Abseil!
Before submitting this PR, please be sure to read our contributing
guidelines.
If you are a Googler, please also note that it is required that you send us a
Piper CL instead of using the GitHub pull-request process. The code propagation
process will deliver the change to GitHub.

Hi Team,
This PR is raised from long time.
Can someone review the change

I don't understand the purpose of this or why it fixes an issue or even what the issue is. Since AIX is not a supported platform (https://opensource.google/documentation/policies/cplusplus-support) and this complicates the code, I'd rather not accept this as is.

@derekmauro
Even AIX is not supported platform as per link you shared, I see various closed PR related to  AIX
https://github.com/abseil/abseil-cpp/pulls?q=AIX
Regarding complexities, can we have separate section for AIX rules like below,
#if AIX
<exiting rules + AIX changes>
#else

We sometimes accept PRs for unsupported platforms if they do not complicate the code. This PR introduces unexplained platform specific build flags. It also provides no explanation why it is necessary since everything seemed to be working before. I suspect there is a more generic way of changing the CMake configuration anyway to achieve whatever this PR is meant to achieve.

@derekmauro
Thank you for following up on this. I agree that  problem/solution is not described properly.
@krushna100
Could you please create a issue and provide the details of the  problem/how to reproduce and the proposed solution .
Mention this PR in that issue.

:closed_book: MEV SW OD Build #27839 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-ts-trunk
FAILURE
59604
 Artifacts
IPU SDK Build

mev-trunk
FAILURE
56680
 Artifacts
Simics_C0_ACC

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

:closed_book: MEV SW OD Build #27894 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-trunk
FAILURE
56702
 Artifacts
IPU_IMC_6_6_4

mev-ts-trunk
SUCCESS
59633
 Artifacts

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

mev-ts-trunk BAT tests: success - build 59633 - it is required if PR have BAT MEV status check as mandatory. If failed, please review Tasks in provided link to Berta. For questions please contact with<EMAIL_ADDRESS>


feat js package

The goal here is to create a js package to use the protofiles in the nest api

Why use camelCase instead of snake_case for proto fields name ?  My bad, LGTM :+1: !


Adding postgresql instructions

ended up putting all this in https://github.com/content-services/content-sources-backend/pull/20


Does not work in VS Code Jupyter Notebooks

Neither %load_ext nb_black nor %load_ext lab_black work with Jupyter Notebooks in Visual Studio Code. There is no error. The code just doesn't format.

nb-black version 1.0.7
VS Code version 1.42.1
VS Code Python Extension version 2020.2.64397
Python version 3.8.1

Just leaving as another suggestion: there is a command for format_cell available in VsCode. In Mac the shortcut is shift+option+F
Again, not a real replacement for the excelent tool that is nb_black, but better than having un-linted code 😅

https://github.com/n8henrie/jupyter-black works really well for me.


fix build release problem

Fixes a problem where build.sc was not in agreement with build.sbt
Broke release scripts
Build release issue
Release Notes

This wasn't @jackkoenig's fault. There is insufficient documentation on release process/script assumptions.


Feature/add seed data builder

This PR adds to models the ability to create flexible seed data for their relationships.
This is a powerful way to create seed data by combining this with mirage factories / routes:
Example of seed data (a customer has many premises, a premise has many energyAccounts and servicesAccounts).
 server.create('customer')
  .anySeedFunctionDefinedInTheCustomerModel() // <= defined on customer, returns customer
  .hasOne('premise', { //
    status: hasPassedScreening || null
  }) // <= defined on customer, returns premise
  .hasNo('servicesAccount') // <= defined on premise, returns premise
  .hasOne('energyAccount') // <= defined on premise, returns energyAccount
  .isJointInvoiced() // <= defined on energyAccount, returns energyAccount
  .anySeedFunctionDefinedInTheEnergyAccountModel(); <= defined on energyAccount, returns energyAccount

Each model has default seed data defined in Model.default()
We made server available as a global in the development environment to make it accessible inside Mirage models (was only a global in test before).
Haven't added tests yet but could do if you want to merge the PR.

Interesting approach, thanks for opening this. I think I'd like to go in more of a factory_girl direction - I really like working with their API. It might look something like this:
// models/post.js
export default Model.extend({
  comments: hasMany()
});

// models/comment.js
export default Model.extend({
  post: belongsTo()
});

// factories/post.js
import { Factory, trait } from 'ember-cli-mirage';

export default Factory.extend({

  title() {
    return faker.lorem.sentence()
  },

  withComments: trait({
    afterCreate(post, server) {
      server.createList('comment', 3, { post });
    }
  })

})

Use would be something like
server.create('post', 'withComments');

We can also add an association helper so users can seed relationships directly:
// factories/post.js
import { Factory, trait } from 'ember-cli-mirage';

export default Factory.extend({

  title() {
    return faker.lorem.sentence()
  },

  comments: association({
    count: 3
  })

})

which would set up the association by default.

whichever way would work I suppose, as long as we have the ability to flexibly change the relationships (right now the afterCreate hook in factories can just take care of one case).
What I like in my approach is the ability to write very user-friendly seed data for test cases ("post.hasOne('comment').isAdmin().hasMany('features')") (where isAdmin() and features are defined on comments) which seems to need access to models themselves.
In your code above, with server.create('post', 'withComments');, I don't know then how to access these comments to setup their own properties / relationships. In my case I can do server.create('post').hasMany('comments', {isEditable: true}), and it will return the different comments on which I can define more associations. This is nicely chained.

I think withComments would be a trait that creates comments in afterCreate, and that's where you could specify overrides/traits for those comments:
// factories/post.js

export default Factory.extend({
  withComments: trait({
    afterCreate(post, server) {
      server.createList('comment', 3, 'someTrait', { an: 'override' });
    }
  })
});

But its true you couldn't specify traits on the comments from the test. You'd need a different trait on the post for that.

@samselikoff ;) so shall we go in this direction then? BDD tests written like this are just awesome: customer.hasAnAccount.isUsingFixedDirectDebit.etc.
Should you wish to go in this direction I'm ready to add tests for the hasOne, hasNone, hasMulti methods above. What was missing to make this PR work was:

Make server available as a global in development (or make it available inside Models at least).
An init hook inside models (using a default() function right now but it's ugly, i didn't get how to properly override the constructor as _super didnt work).

?

Added some comments in #852, want to get your response but let's discuss there.

@samselikoff , using my hasOne, hasMulti, hasNone etc. methods on Mirage models now and it's just great. Still, I'm seeing now that I would ideally need observes on Mirage models (to update properties when children change) etc., and the more I think about it, the more I'm realizing that actually Mirage models should just be Ember-data models, with a different test store (accessible from server), a specific testSerializer etc. This way we could leverage the whole Ember-data infrastructure (ember inspector etc.). You may have already thought about that when building Mirage but I would be curious to know your thoughts about that: it seems to be that you are going in a way with the Mirage models where you will actually have to build many more things to make the whole stuff coherent (normalizers etc.), while it would be simpler to just leverage  the framework.
?

:thumbsdown:

Hey, I am responding right now, didn't mean to close without commenting. Writing...

Closing this for now since we've merged traits.
Thanks for your thinking on this, keep it coming. Yes we actually had this very discussion many months ago, and a few other times again since then. Originally the idea was vetoed mostly based on instinct: Ember Data is a library built for a few specific reasons: (1) client-side identity map (2) fundamentally asynchronous (talk to multiple hosts, deal with HTTP lifecycle etc). Mirage's db/orm layer originally wasn't either of these, so I didn't want to force a round peg into a square hole. Also many users don't use Ember Data, and originally it was very important for Mirage to be minimal in terms of its API and complexity so that folks would actually use it.
Obviously over the past year Mirage's complexity has grown, and we now have an ORM and the db is effectively an identity map/data store. Mirage-in-the-browser is still fully synchronous, but there's been talk about allowing it to run in node (we'd get the Network devtools for free, for one). So, it's true that it seems like the needs of Mirage's data layer have come closer and closer to those of Ember Data.
Some more random thoughts:

I'd like to extract core Mirage from Ember CLI Mirage one day (when? I don't know), as Mirage itself is unaware that it's ever talking with an Ember app. It's true that we could do this while still relying on standalone Ember Data but it would make more integration work for us here, make Mirage core rely on another external dependency etc.
Ember Data objects are observable, and while you cited that as something you'd like to have in Mirage I'm not convinced it's needed (definitely willing to discuss). Despite in the increase in complexity I still want Mirage to be as simple as possible. Data creation should be focused on setting up server scenarios for dev/testing, that's about it.

Anyway that's kind of a brain dump, I'm happy to keep the discussion going. I have a contract to round out the ORM with the missing relationships and I'll most likely be doing that by working on the existing data layer. Bringing in Ember Data is a big step and would take some more thought.
Thanks again for your input.

Oh and I closed this PR not to shut down the convo but because we merged traits in. I'm glad your API is working for you and your team, I actually think that's good and teams should feel like Mirage's primitives are low-level enough to allow them to make higher-level helpers specific to their domain, which makes setting up scenarios easy.

Thanks for your response. All makes sense, especially the asynchronous nature of Ember-data (except with {async: false} relationships? And except with custom serializers / adapters, see localStorageAdapter) ?
In my case the need for observers comes from the fact that we can have different server responses to PUT or POST requests, with complex logic based on, say, answers to a survey.
I also saw the need in this PR to have init methods, beforeDestroy hooks etc.
but yes, I realize that this actually makes things closer to Ember-Data, and yes it would be a big work to include ED into Mirage (probably a new add-on?).
In case you may want to go into that direction (i.e. in the direction of this PR or even towards combining Ember-data), I could be interested to take part.

Yah. I'll definitely continue to think about it, and thanks for offering your help. I'll keep it in mind.
Again in most of the use cases I've seen folks don't need those advanced hooks, so if it's only 5-10% of users needing them I'd rather push that out to those specific users. However this could be colored by my personal use of Mirage. In my projects I've never felt this need, but I should probably take a survey and see what features folks think are missing.


Server-side configuration

Hi,
I'm trying to migrate from restic to rustic and get some benefits of config files.
There are tons of wrappers around restic. I'm personally using my own that also stores configuration on remote side. And I want to get rid of it :)
So I want to propose some discussion about this feature. What I would like to have is:

Make sure that backup list (names, schedule, excludes) are configured on remote side.
Have per-host exclude list (with partial sharing)
Do self-update if needed using my own build (basically tested/approved build)
Upload logs

Ideally I would like to just add rustic poll-do-geverything to /etc/cron.hourly and let it do everything needed (basically just check and do backup if needed). cron.hourly is used here to make sure backup is retried in case of network failure.
Right now I've custom wrapper for restic and I'm using rest-server as backend for this. Just extra restic-like repo is hijacked and reused to serve this. But I think we can think about extra directory layout.
PS. Most likely I'll try to contribute code if it's interesting

@dionorgua I would be very happy if you could try out the present very beta version. Even more if you could add feedback (issues) on what might be good extensions to rustic_scheduler...


delete Object not delete RLMArray property, delete cascade not work?

when you call
[realm deleteObject:rlmObject];

it will delete rlmObject , but the RLMArray object associated with with the rlmObject will not deleted.  To delete it, I need to call
[realm deleteObjects:rlmObject.assets];  // assets is a RLMArray

This will become a big problem. some object will leak, and the realm will become larger and larger. People will forget to delete RLMArray property
I hope you can provide delete cascade method to delete all the object and all the property.

ok , I write a Helper to delete model cascade. if you like it , you can check out it at
https://github.com/com314159/RealmDeleteCascad

We have an issue tracking adding cascading deletes, #1186, so you'll see any updates on that front over there. We are working on that.
And, your repository seems empty for me. Did you forget push to the repository?

it pushing now

I have write a Helper , you can just delete all the object with code.  I just read all the Realm property value and delete it.
[RLMHelper deleteModelCascad:model inRealm:realm];

It sounds like your workaround is no problem.

pefect


Fix bug where parent policy event was not sent

The parentStatusUpdateNeeded variable is (usually) carefully guarded
to ensure it only ever moves from false->true, and never back to false.
The moved section of code was not obeying that, and it was being run for
every object template. The result was that one object template could
mark the status as needing an update, but then be overriden by a later
run through the loop.
This section can just be outside of the loop, improving performance and
removing the bug. The additional variable to guard the update to
parentSatusUpdateNeeded might not be strictly necessary, but this bug
was too annoying to find to not make every effort to prevent it in the
future.
Signed-off-by: Justin Kulikauskas<EMAIL_ADDRESS>

Tide seems stuck... I'm going to try and poke it
/override KinD tests (1.18, latest)

Now I might've broken it
/override KinD tests (1.18, latest)


Ginkgo: test runner: add flag to allow helm overrides

test: add ability to override/add extra helm flags for ginkgo tests.

This adds -cilium.install-helm-overrides flag which provides a way to
add or override test flags without modifying the test code.

This is useful for forked projects to extend testing by providing their
own custom flags to the test program.

For example, you could extend the tests by doing:

-cilium.install-helm-overrides="foo=bar,\"zap={a,b,c}\"" which would
add: --set foo=bar and --set zap={a,b,c} to the cilium install params.

/test

/ci-ginkgo

/ci-ginkgo

/test

/ci-ginkgo

/test

/test

/ci-ginkgo

/ci-ginkgo

/test


M3 connecting article

Detail how to find and use the connection details for this service

The existing code samples cover what we need here.


Expand content whitelist

When exporting tabular data from flow simulators like eclipse or opm the current whitelist ALLOWED_CONTENT is too narrow.
list is currently (commit 949e906) the highest level:
depth, time, thickness, property, seismic, fluid_contact, fluid_outline, field_region, regions, pinchout, subcrop, fault_lines, velocity, volumes, volumetric, khproduct, and timeseries. See _definitions
Of these it is only khproduct, volumetrics, and timeseries that are relevant to simulator results.

Yes, the list is not exhausted by any means. We have usually expanded it when explicit needs are uncovered, through separate issues.
Suggest to make specific issues for specific allowed contents so that they better can be done and closed.
Ideally, allowed contents should correspond to defined (data) products produced by FMU workflows. It is, however, also influenced by legacy contracts with e.g REP and others.

Closing this, we expand the whitelisted contents regularly on an as-needed basis. The content is a crucial metadata tag, as it is basically the only one that says what a piece of data actually is. Ref discussions on data products.


Change Paragraph Heading Style and Spacing

Currently, a \paragraph heading does not match the look of the monster ability heading or a paragraph heading from the PHB. It also has an unreasonable amount of space after it.

Looks like this is handled by;
https://github.com/evanbergeron/DND-5e-LaTeX-Template/pull/44


Support Prometheus versions before 2.26

Describe the bug
Installed krr v1.6.0 on my macbook via brew, pointed krr at my cluster, it crashed on running with the following error message:
(backtrace excluded, can add it if it would be helpful)
PrometheusApiClientException: HTTP Status Code 400 (b'{"status":"error","errorType":"bad_data","error":"invalid parameter \'query\': parse error at line 2,
char 32: unknown function with name \\"last_over_time\\""}')

Software versions
Prometheus v2.12.0
kube-state-metrics v2.4.1
krr v1.6.0
run with:
krr simple -n staging -p http://url.to.prometheus

Expected behavior
Expecting the krr report on resource limit recommendations
Additional context
I checked and it's clear prometheus and kube-state-metrics are somewhat backrev.   The docs for krr don't indicate specific version compatibility.   I  can look into upgrading the software, but if there are known version incompatibilities or older versions of krr that might work with the older versions, that would be really helpful before I start digging without knowing where I'm headed.  Thanks!

Hey, we don't have any official guide on version compatibility right now. But if you do that research, please open a PR and contribute your findings!
We test KRR regularly on the version of kube-prometheus-stack bundled with Robusta OSS but we don't have a full test matrix beyond that. (Yet.)
Any contribution to docs or a testing system would be great.

Thanks @dgdevops, nice catch.
I've updating the README and am updating the issue's title.
Just a heads up - we're not prioritizing support for earlier Prometheus versions at the moment. But - as always - PRs are welcome.


feature request:  If it is not done, than calculate the IMEI and it's last check digit by the Luhn algorithm

Issue: A few times I experienced that GL750 Mudi could not boot and/or the celluilar interface did not start witch some randomly generated IMEIs and I was assuming that they  either may be gray/blacklisted ones nad/or simply not valid by syntax?
If  syntaxial validity check is not done than please consider the Luhn algorithm formula for generated IMEIs
https://sndeep.info/en/tools/checksum_calculator

Do you have any reason to suspect the IMEI being at fault? As far as I am aware, we're calculating the checksum.
I wonder whether the device not booting or the cellular interface not being available can be attributed to something else failing. Do you happen to have a log when the cellular interface does not come up?


Flexdatalist loading spinner

I couldn't find it in flexdatalist, is there spinner for autocomplete ?
for example like this: http://cdn.rawgit.com/salmanarshad2000/demos/v1.0.0/jquery-ui-autocomplete/custom-html-in-dropdown.html
if you type PHP you will see spinner right of the input, I want to add inside of my input is that possible with flexdatalist ?

Hi,
Yes, it's possible. You'll need to implement the spinner yourself using the available events.
Check out before:flexdatalist.data and after:flexdatalist.data in http://projects.sergiodinislopes.pt/flexdatalist/
Cheers!
Sérgio


[database] Fix, test connection error message for module not found

CATEGORY

[X] Bug Fix
[X] Enhancement (new features, refinement)
[ ] Refactor
[ ] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY
When the connection scheme is composed by 2 elements "+://...." the error reported to the user is  "Unexpected error occurred, please check your logs for details" and should be "Could not load database driver: ..."
TEST PLAN

Create a database connection with: something+dummy://someserver:9999/test
Check that the error reported is "ERROR: Could not load database driver: something+dummy"

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Would it be possible to add a test for this case?

Hmm, I wasn't able to reproduce with the test string something+dummy://someserver:9999/test. Were you testing a specific driver when this came up?

Yes caught this while testing MSSQL, so used:
mssql+pymssql://sa:XXXXXXXXXX@localhost:1433/msdb
You can reproduce it by removing the pymssql from the virtualenv


ci(fastlane): correct ruby block in Fastfile (missing end)

Fastfile correction found by: @kaichengyan
Update Fastlane and other gems

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@palpatim appears to just be dumb luck that it worked. The number of ends has not changed in this PR, just their positions, so some of the lanes were nested inside of the increment_versions lane but apparently that still works in fastlane. Both the prior and current versions were technically valid Ruby, just with nonsensical block nesting in the former case.
I tested this locally, ensuring that calling fastlane unstable and fastlane release still executes all of the required private lanes, etc.


AES-128 padding for packet length % 16 == 0

In OSDP V2 1_6_2014 - Appendix D.4.5 Padding is specified that
padding is necessary also if the data block is multiple of 16.
At the moment in the library there is no padding if length % 16 == 0.

@z8a, Acknowledged. Thanks again, great find.

I've reported your modifies on my firmware but they aren't working. I was not able to understand why.

What is the issue you are facing? Can you paste the logs produced by this library with loglevel set to DEBUG?

@z8a, Are you still facing this issue? or have you resolved it? You need to provide some additional information if you'd like me to look into it.


feat(overflow menu): add top placement configuration for overflow menu

Closes #836
Changelog
New

It is now possible to change the placement of the overflow menu to the top position.

Also the storybook examples are on the same line ... display: flex doesn't have the same defaults everywhere, so you may need to add row/column direction ... alternatively you should be good with more margin and the default display: block


feat(console): authorizations from user context, add grants to auth user view, fix app saving

Closes #903
Closes #902

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

GitHub release
v0.100.0

Your semantic-release bot :package::rocket:


what are the RAM requirements for node-js server. How can i improve performance in node-js server?

Issue Description
what are the RAM requirements for the node-js server? How can I improve performance in the node-js server?
i have 1GB server on digitalocean.
and use this module to analyze videos via the node js server. but after some time the error was received.
W tensorflow/core/framework/cpu_allocator_impl.cc:82] Allocation of 9830400 exceeds 10% of free system memory.
and my pm2 restart.
please tell me how much RAM is required to run this smoothly and how can I improve to the batter.
Steps to Reproduce
Expected Behavior
Environment

Human library version?
Built-in demo or custom code?
Type of module used (e.g. js, esm, esm-nobundle)?
TensorFlow/JS version (if not using bundled module)?
Browser or NodeJS and version (e.g. NodeJS 14.15 or Chrome 89)?
OS and Hardware platform (e.g. Windows 10, Ubuntu Linux on x64, Android 10)?
Packager (if any) (e.g, webpack, rollup, parcel, esbuild, etc.)?
Framework (if any) (e.g. React, NextJS, etc.)?

Diagnostics

Check out any applicable diagnostic steps

Additional

For installation or startup issues include your package.json
For usage issues, it is recommended to post your code as gist
For general questions, create a discussion topic

how much memory is required depends on which models you have enabled
you can always monitor you engine memory usage with console.log(human.tf.memory())
and if you need more info on tensorflow internals memory allocation, you can increase its logging with
process.env.TF_CPP_MIN_LOG_LEVEL = '0';
there are some TF_ environment variables that change default behavior of tensorflow's memory allocator, but i didn't experiment much with that.
i'm closing the issue as its not a product issue per-say, but feel free to post further on this thread.


feat: The great MIPS64 migration

Overview
cannon-rs was started as a side project, as a way to learn more about cannon as well as spike out potential optimizations to the FPVM. Today, the project sits largely dormant as a fun toy.
As the OP Stack approaches the multi-proof future, space for new Fault Proof VMs comes into play. Currently, the Test in Prod team is working on bringing https://github.com/protolambda/asterisc to production readiness. cannon-rs sits in an odd spot, where it is just a faster version of cannon, bringing little value to the security of the OP Stack.
Instead of cannon-rs serving as an alternative implementation of cannon, it has the potential to serve as a 3rd fault proof VM with little modification - converting to the MIPS64 ISA. 64-bit register size gives many affordances - more platform support, larger memory address space, etc.
This project is pending specification. If anyone would like to pick this up, please signal below and I'd be glad to help specify the work and guide the project :)

@clabby we would like to try it. @thinkAfCod and I are planning to try more rust projects this year.

I'd love to help if I can :)

@clabby Based on the mips64 documentation and my own understanding, I completed the mips64 modification (including the current instruction set, registers and memory 64 bits, 8-byte alignment, excluding new instruction sets such as double-word support).
Retested and found that the current asm file memory operation is 4-byte aligned, and the following code cannot be tested. I am not sure whether I must modify the asm file for 8-byte memory operations?

@GrapeBaBa Thank you very much for starting work on this! Awesome to see 💪
These tests were pulled from OpenMips, which is an implementation of MIPS32r1. These should still work on a MIPS64 processor - When executing MIPS32 instructions on a MIPS64 processor, the alignment requirements of MIPS32 instructions should be preserved.
See page 27 of the architecture spec:

The CPU uses byte addressing for halfword, word, and doubleword accesses with the following alignment constraints:
• Halfword accesses must be aligned on an even byte boundary (0, 2, 4...).
• Word accesses must be aligned on a byte boundary divisible by four (0, 4, 8...).
• Doubleword accesses must be aligned on a byte boundary divisible by eight (0, 8, 16...)

In other words - for MIPS32 instructions that read or write memory, the memory must preserve the ability to enforce single-word aligned accesses (32 bit / 4 byte alignment). For MIPS64 instructions, doubleword alignment rules apply when accessing memory.

@clabby Except evm tests, all tests passed. Before the contract supports mips64, it may be necessary to review the rust code, especially the part about patch and memory handling.


Content and layout update

Submitted this against master because it looks like dev is behind. Did you remove the up arrow from the nav bar? It's not showing up anymore

No it's a styling issue, I need to push a fix for that


Fix schema generation for views with request_serializer property

This closes #57 and also fixes support for versioned
request serializers.

Ah damn. I messed that PR up in the last second when refactoring a bit. It's not ready to be merged. Sorry.


Question:  chacha poly support in 1.0.1?

Topic really..I've tried to compile it in with:
./Configure enable-chacha enable-poly1305

but after compiling and doing a "openssl ciphers" chacha poly1305 do not appear.  Thank you.

no, it's only in 1.1.0

Thank you!


How can I default to sqlcipher4 with sequelize?

const Sequelize = require("sequelize");
const db = new Sequelize({
    dialect: 'sqlite',
    storage: path.join(process.cwd(), "sample.db"),
    dialectModulePath: '@journeyapps/sqlcipher',
    logging: false,
    define: {
        freezeTableName: true
    }
});
db.query("PRAGMA key = 'password'");

I am not able to open the sample.db file with sqlitebrowser SQLCIPHER 4.

The only way its works is by adding the below line and then use SQLICIPHER 3 in sqlitebrowser
db.query('PRAGMA cipher_compatibility = 3');

Which version of this package are you using?
The SQLCipher 4 defaults should be used by default, so I'm not sure why this isn't working.
You can try to set the individual parameters explicitly to match sqlitebrowser:
PRAGMA cipher_page_size = 4096;
PRAGMA kdf_iter = 256000;
PRAGMA cipher_hmac_algorithm = HMAC_SHA512;
PRAGMA cipher_kdf_algorithm = PBKDF2_HMAC_SHA512;

@rkistner I use @journeyapps/sqlcipher": "^4.1.0

I also encountered the same problem

Is there any solution?

I've tested with @journeyapps/sqlcipher versions 4.1.0 and 5.0.0, and couldn't reproduce in either version.
Tested with sqlitebrowser 3.12.99 / sqlcipher 4.3.0.
If you still run into the issue, I recommend:

Test with the sqlcipher CLI instead of sqlitebrowser.
Test using this library directly, without sequelize.

Also check whether adding PRAGMA cipher_compatibility = 4 (before setting the key) makes a difference.


[docs]: inline markdown in code blocks not rendering correctly

The docs have some code blocks that seem to be using inline markdown to embolden certain parts of the code. That inline markdown isn't being rendered though so the code blocks contain invalid syntax.
Here's an example from the Codemod 2.0 page:
https://github.com/codemod-com/codemod/blob/a02ae784dd3e8dbce41b370d6e99ab3ec6128c2e/apps/docs/guides/building-codemods/codemod2.mdx?plain=1#L56-L64
Note that line 62 contains **astGrep("import { $$$_ } from '@mui/icons-material'"**. The ** bold symbols are displayed in the rendered code block:

thanks, i pushed a fixed for this... you ROCK. keep these coming! <3


Better CI for all target platforms

Import from here

Android (#17), iOS (#18) and Web/WebAssembly/WASM (#19) support will be added at some later point.


Fixes #114: Participation in jspm/systemjs project not possible

Please consider these tweaks to make my life easier!  I do not want to maintain a fork.
Thanks for the awesome project; as we use the library more I hope to send a few more useful PRs.

Any chance these changes could be adopted?   Basically it looks like module.exports was nearly removed universally except in two places.  I would like to stop maintaining my fork.
Thanks!

I will look into seeing if I can configure jspm to auto import index.js
On Wed, Feb 8, 2017 at 10:32 AM, Jonathan Petitcolas <
<EMAIL_ADDRESS>wrote:

@jpetitcolas commented on this pull request.
In lib/eventDrops.js
https://github.com/marmelab/EventDrops/pull/115#pullrequestreview-20786757
:

@@ -2,7 +2,7 @@ import d3 from 'd3';

import configurable from 'configurable.js';
import defaultConfig from './config';
-import drawer from './drawer';
+import drawer from './drawer/index.js';
I'm not very confortable with this change. Is it compulsory for jspm?
Isn't there any module to counter that?
If not, write at least a comment to let the index.js file here.
Otherwise, another developer would probably remove it in a near future. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marmelab/EventDrops/pull/115#pullrequestreview-20786757,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAq8l79RyRhrR92CFxLEXSDl6mau550tks5rad_5gaJpZM4K1qGe
.

I updated the PR to remove the requirement for the index.js sub-import.  Looks like a later version of jspm relaxed this or I had it misconfigured.

Perfect! Thanks! :)


Sync with main branch

Description

Sync with main branch for ODH 2.18 release

AFAIK, we don't sync with main. I think this should be closed.

@israel-hdez can you please elaborate? I've done this a few times already, not sure why we don't do this.

@spolti Similarly to KServe, we base our ODH release on an upstream release.
By pulling changes from main into the release branch our release is no longer based on an upstream release, but just on latest code. Thus, the release branch no longer makes sense and we could simply release from main, which is not our current goal.

ohhh right lol
I didn't pay attention to the target branch, indeed, we can close this.


”Țibănești” is listed in the drop-down menu

Description:
"Țibănești" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Țibănești" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Țibănești, IAȘI".


Terminal resolution error after scaling window size

Type: Bug
Terminal resolution error after scaling window size
VS Code version: Code 1.71.0 (Universal) (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:25:38.437Z)
OS version: Darwin x64 21.6.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz (8 x 2000)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
4, 3, 3

Memory (System)
16.00GB (0.52GB free)

Process Argv
--crash-reporter-id e25fe8ef-b82c-41fd-a55c-0f87141a7ea6 --crash-reporter-id e25fe8ef-b82c-41fd-a55c-0f87141a7ea6

Screen Reader
no

VM
0%

Extensions (48)

Extension
Author (truncated)
Version

javascript-ejs-support
Dig
1.3.1

githistory
don
0.6.19

vscode-html-css
ecm
1.13.1

code-runner
for
0.11.8

html-snippets
gey
0.2.3

gc-excelviewer
Gra
4.2.55

riscv-venus
hm
1.7.0

vue-snippets
hol
1.0.4

d3-js-snippets
Hri
1.0.0

latex-workshop
Jam
8.29.0

better-cpp-syntax
jef
1.15.19

cmake-language-support-vscode
jos
0.0.4

vscode-leetcode
Lee
0.18.1

rainbow-csv
mec
2.4.0

vscode-language-babel
mgm
0.0.36

vscode-dotnet-runtime
ms-
1.5.0

python
ms-
2022.14.0

vscode-pylance
ms-
2022.9.10

jupyter
ms-
2022.8.1002431955

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

remote-containers
ms-
0.251.0

remote-ssh
ms-
0.84.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.3

cmake-tools
ms-
1.12.26

cpptools
ms-
1.13.0

cpptools-extension-pack
ms-
1.3.0

hexeditor
ms-
1.9.8

vetur
oct
0.36.0

java
red
1.10.0

LiveServer
rit
5.7.9

code-spell-checker
str
2.7.3

latex-utilities
tec
0.4.6

latex-support
tor
3.10.0

cmake
twx
0.0.17

vscode-lldb
vad
1.7.4

vscodeintellicode
Vis
1.2.25

vscode-java-debug
vsc
0.44.0

vscode-java-dependency
vsc
0.21.0

vscode-java-pack
vsc
0.25.1

vscode-java-test
vsc
0.37.1

vscode-maven
vsc
0.38.0

volar
Vue
0.40.13

JavaScriptSnippets
xab
1.8.0

markdown-all-in-one
yzh
3.4.3

material-theme
zhu
3.15.5

riscv
zhw
0.0.8

(3 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaac:30438847
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
i497e931:30553904

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette).
Happy coding!

https://user-images.githubusercontent.com/92004310/189330169-5a7c6456-e940-420d-bc8a-62955550e158.mov

/duplicate https://github.com/microsoft/vscode/issues/157585

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


Support initial namespace of the cluster without startup the broker

Motivation
Setup the initial namespace of the cluster without startup the broker
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (no)

need to cherry-pick to branch-2.6 @wolfstudy

need to cherry-pick to branch-2.6 @wolfstudy

Sure, done.


request_state promise and update message

When requesting state from the back-end, a regular update message is sent back, and a complicated logic to match the message id is applied to resolve the promise correctly. Another consequence is that the resolution of the request_state promise is external to the promise code itself.
I think that the response to a request state should not be a regular update but a separate message type.

When requesting state from the back-end, a regular update message is sent back, and a complicated logic to match the message id is applied to resolve the promise correctly. Another consequence is that the resolution of the request_state promise is external to the promise code itself.
I think that the response to a request state should not be a regular update but a separate message type.

I don't see how a separate message type will solve these problems.  Because the notebook doesn't have request/reply messaging, we'll still need to map the responses ourselves.

@SylvainCorlay ?

I was trying to push for request/reply messages in comm, but I think that it is not going to happen in a near future.

I pushed the target to 4.2, so we can keep it on our plate for when request/reply messages get added.

Should we consider this one solved?


"packages.txt" file ignored in the same dir

Suppose we have "/some/path/file.blend" and "/some/path/packages.txt" (files on same directory level).
In this case "packages.txt" file is ignored

Can't reproduce anymore. It looks like the issue was about spaces in path, which is fixed by 72d6fc5c1612a323d.


Opening devtools when opening in terminal

Oni Version: 0.3.6 Stable
Operating System: macOS 10.13.6
Issue: Executing oni from the terminal opens up the editor AND the chrome devtools.
Expected behavior: Only the editor should be opening up
Actual behavior: Chrome devtools is opened up as well as the editor
Steps to reproduce:

Add oni to PATH
Execute oni from terminal

Any news on this? It still occurs. I even uninstall and reinstall oni and opened from the terminal but the issue still occurs.

I've not been able to reproduce this, so could be something specific to your machine.
Is it possible that you have some form of node environment variable set? I think we check the NODE_ENV one as part of checking if we are running in development mode, and then if we are, open the dev tools.

So I would have to change my NODE_ENV to something else like production? Cause right now my NODE_ENV is set to dev.


Removed an unsuitable package info

Needless to set tins version strictly here, sorry.
I'd clean forgotten to remove before doing commit.
coveralls requires it by setting json version specifically.

Good looking out!


Feature/#110 config

PR for Issue #110.
PR Status
READY
Changes proposed in the pull request:

Pass in config variables using closure.defines.
Fixed app so it would work with :advanced optimizations.

Breaking changes?

None (will test a lot tomorrow on the various environments but locally seemed to work fine)

Screenshot of feature:

@emilyseibert @oconn @dehli

Note: With this change I've also added aliases. This means that you can run the app locally just by calling:
lein local-dev


Tyepscript: Property 'join' does not exist on type 'typeof Prisma'

Bug description
I'm using Prisma in a typescript project and the join function is causing the file to fail compilation with: Property 'join' does not exist on type 'typeof Prisma'
I referenced this from the documentation: https://www.prisma.io/docs/concepts/components/prisma-client/raw-database-access#tagged-template-helpers
How to reproduce
Copy the following in to a Typescript file:
import { Prisma, PrismaClient } from "@prisma/client";
export function test() {
const pc = new PrismaClient();
const results = pc.$queryRawselect A as test from TEST where A in (${Prisma.join(     ["1", "2"]   )});
}
Expected behavior
The join function should exist on the Prisma type.
Prisma information
Dependency on "@prisma/client": "^4.8.0"
Environment & setup
This is an issue in Windows and in github workflows.
Prisma Version
8.19.2

I should mention that the compilation works after running prisma generate. But I assume this shouldn't be necessary?

Yes, running prisma generate is necessary. I think this is because $queryRaw depends on the provider.
We could maybe mention something in the docs.

Ok. I was hoping it would be possible to push the functions on to the Prisma module without a generate.
I was able to copy the join function out as a shim, and that worked, but ran into more functions that needed the generate to be run first. I ended up just running prisma generate before running my project build/unit tests. shrug

For example, on MongoDB these utilities would not make sense as they are only useful when using SQL.
But I get the point that it could be nice if it would be always available without having to generate 👍🏼


Set Metadata option to get state store API

Description
This PR sets Metadata option to state.GetRequest from Dapr Runtime.
As a follow up to this, the docs should also be updated here ?
Issue reference
This PR will close: https://github.com/dapr/dapr/issues/956
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

This change is

Thanks for the contribution @ksashikumar Could you please resolve conflicts and update the PR?

Thanks for the contribution @ksashikumar Could you please resolve conflicts and update the PR?

I've updated the PR. But the actions failed while bootstrapping the environment. Possibly because of the Github Incident ? 🤔

@amanbha @yaron2 @shalabhms  is this good to merge?

@amanbha @yaron2 @shalabhms is this good to merge?

yup we will merge once pr build is done.


Ensure perspective value is non-zero

Setting transform: {perspective: 0} was causing app failure due to NaN produced by divide by zero in MatrixMath.js.
See issue #2616

@facebook-github-bot shipit

cc @mkonicek

ping @bestander :)

Temporal anomaly in flux relays caused a spike in antimatter collectors.
I realigned the dilithium crystals and it should be fine in an hour.


Membership not working anymore.

I've been using ytarchive to download member and non-membership videos on YouTube for while now, and I've always been able to make the cookies file with with this Chrome extension (https://chrome.google.com/webstore/detail/get-cookiestxt/bgaddhkoddajcdgocldbbfleckgcbcid) and it would download with no problem. Now, it's telling me I'm not a member no matter what channel I try.

I even tried it on 0.3.2 and the latest version, still not working. Maybe YouTube changed how they format their cookies? I'm out of ideas. I even tried yt-dlp and it gave me the same issue.

Cookie format is not dependent on the site.
It's still working for me. When is the last time you exported your cookies?
Check to make sure the cookies look fine. Cookies should look like the following in the file:
.youtube.com    TRUE    /       FALSE   0       wide    1
domain, true/false, path, true/false, some number, cookie name, value

I made a new cookies file just now, like 10 minutes ago.
I'm assuming this cookies file isn't safe to share publicly? If it is okay I can just paste it. But, from what I see, all the lines seem to be formatted that way.

Actually, some of the values are formatted like that, and some are formatted like this:
.youtube.com	TRUE	/	FALSE		wide	1	5
Maybe the extension was updated and broke something. Thanks for the help. If you don't mind me asking, how do you generate a cookies file? That extension was the only way I could figure it out myself.

Correct, that is not safe to do. I went through mine looking for a cookie that was specifically safe to post as an example.
The only things I can think of are it not exporting the right cookies, it exporting stale cookies, somehow it doesn't see you as logged in when exporting, or the site is not set correctly. But given it was working before, it's hard to say.
That extension you linked updated a day ago, maybe it changed the export format, but that wouldn't have affected the previously exported cookies.

I use this but slightly modified since I have have my logged in account in a container tab.
https://addons.mozilla.org/en-US/firefox/addon/export-cookies-txt/


tsconfig.json includes from node_modules not rewritten

Currently we are referencing d.ts types from a shared library in our local projects like here:
{
    "extends": "../../../tsconfig-base.json",
    "compilerOptions": {
        "target": "es6",
        "lib": [ "es6", "dom" ],
    },
    "include": [
        "./**/*",
        "./**/*.json",
<EMAIL_ADDRESS>    ]
}

When copying these files into the sandbox, the paths are not altered, so that they point to non-existent subdirectories and tsc -b is failing.
As a workaround, we added them like this:
{
    "include": [
<EMAIL_ADDRESS><EMAIL_ADDRESS>    ]
}

Please alter paths and add additional ../../to the entries. This might also make sense for other directives (typeRoots, excludes, ...).
Stryker config
{
    "$schema"<EMAIL_ADDRESS>    "_comment": "Stryker Mutator config",
    "packageManager": "yarn",
    "reporters": [
        "html",
        "clear-text",
        "progress"
    ],
    "mutate": [
        "src/main/**/*.ts",
        "!src/main/**/*Spec.ts"
    ],
    "ignorePatterns": ["lib", "build", "www"],
    "testRunner": "mocha",
    "testRunnerNodeArgs": [
        "--require",
        "esm"
    ],
    "mochaOptions": {
        "extension": [
            "ts",
            "tsx"
        ],
        "spec": [
            "src/**/*Spec.ts"
        ],
        "require": [
            "src/test/ts-hook",
            "ignore-styles",
            "mocha-steps"
        ],
        "package": "./package.json",
        "ui": "bdd",
        "async-only": false,
        "grep": ".*"
    },
    "coverageAnalysis": "perTest",
    "checkers": [
        "typescript"
    ],
    "tsconfigFile": "src/test/tsconfig.json"
}

Test runner config
.mocharc.js
'use strict';
module.exports = {
    reporter: 'mocha-better-spec-reporter',
    file: ['src/test/setupEnvironment.ts'],
    extension: ['.ts'],
    require: [
        'esm',
        'src/test/ts-hook',
        'ignore-styles',
        'mocha-steps'
    ],
    recursive: true,
    timeout: '10s',
    exit: true,
};

Stryker environment

├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>│  ├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>

├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>├─<EMAIL_ADDRESS>
Test runner environment

yarn run mocha --exit 'src/**/*Spec.ts'

Your Environment

software
version(s)

node
16.13.0

yarn
1.22.10

Operating System

NixOS
unstable

Thanks for opening this issue. As a workaround, could to try to run with --inPlace?

Fix released in v5.5.1


Should aiohttp-cors add a Vary: Origin when emitting a access-control-allow-origin?

When aiohttp-cors writes an header like Access-Control-Allow-Origin, with the Origin request Header, I think it shoul also emit a Vary: Origin (because the response vary according to the Origin). What do you think?

Also see : https://fetch.spec.whatwg.org/#cors-protocol-and-http-caches


How to feed SparseTensor in C++ API?

I trained model via python. After training done, I want to load the model and its checkpoint for prediction via C++. But I can't find any solutions about how to feed SparseTensor or Example in C++ API.
python train code:
with tf.name_scope('input'):
    filename_queue = tf.train.string_input_producer(
    tf.train.match_filenames_once(file_name), num_epochs=max_epoch)
    serialized_example = self.Decode(filename_queue)
    capacity = thread_num * batch_size + min_after_dequeue
    batch_serialized_example = tf.train.shuffle_batch(
                                    [serialized_example],
                                    batch_size=batch_size,
                                    num_threads=thread_num,
                                    capacity=capacity,
                                    min_after_dequeue=min_after_dequeue)
    features = {}
    features['label'] = tf.FixedLenFeature([], tf.float32)
    features['continuous_feature'] = tf.FixedLenFeature([], tf.float32)
    features['sparse_id'] = tf.VarLenFeature(tf.int64)
    features['sparse_val'] = tf.VarLenFeature(tf.float32)
    instance = tf.parse_example(batch_serialized_example, features)

    label_tensor = instance['label']
    continuous_feature_tensor = instance['continuous_val']
    sparse_id_tensor = instance['sparse_id']
    sparse_val_tensor = instance['sparse_val']

with tf.variable_scope("emb") as scope:
    embedding_variable = tf.Variable(tf.truncated_normal([1000000, 50], stddev=0.05), name='emb_matrix')
    embedding = tf.nn.embedding_lookup_sparse(embedding_variable, sparse_id_tensor, sparse_val_tensor, "mod", combiner="sum")
net = tf.concat([embedding, continuous_feature_tensor], 1, name='concat')
dim = net.get_shape().as_list()[1]
weight = tf.Variable(tf.truncated_normal([dim, 100], stddev=0.05), name='fully_weight')
bias = tf.Variable(tf.truncated_normal([100], stddev=0.05), name='fully_bias')
net = tf.matmul(net, weight) + bias
cross_entropy = tf.nn.sparse_softmax_cross_entropy_with_logits(logits=net, labels=label_tensor, name='cross_entropy')

In C++, all solutions I have found is to feed vector<pair<string, Tensor>> into session.Run(). However, in my model, I don't know which function in C++ I should use.
Thanks.
@martinwicke

This seems similar to #12264. /CC @skye

which c++ interface do you use to feed sparseTensor?

which c++ interface do you use to feed sparseTensor?

when i save model i use placeholder,and use tfserving for predict.In the client,I use the tfserving grpc c++ client,the predictRequest's inputs is map of <string,tensorproto>

@formath Do you mind to share the code for running such model in C++? The Session::Run() function accepts a vector of <string, Tensor> pairs, but I don't know how to create a Tensor object for sparseTensor (SparseTensor is not a subclass of Tensor...)

fixed


Resolve image align bug on view mode by modfying style

According to issue #4 , we have alignment bug on view mode.
This is caused by the Prosemirror in editor mode was aligned by its parent dom, so the styles were not applied when parsing it as HTML.
So I was able to solve this by changing the style to the image's own margin values.
Please check it and feedback to me.

@bae-sh sorry for the ping, could we get a release with this PR? We would really need this fix :)


Components imported in tests (Jest) throw overload errors on props

If I have a component with, say, 2 props. Neither of them required, but have defaults and I mount a component with only 1 prop specified, the plugin will throw up on an overload.
Example:
import Block from '@/components/Block'
import { mount } from '@vue/test-utils'

describe('Block', () => {
  it('should increase a', () => {
    const wrapper = mount(Block, {
      propsData: {
        heading: 'Foo',
      },
    })
    expect(wrapper.find('h1').text()).toBe('Foo')
  })
})

Component:
<template>
  <h1>{{ heading }}</h1>
</template>

<script lang="ts">
import { defineComponent, ref } from 'vue'

export default defineComponent({
  name: 'Block',

  props: {
    heading: {
      type: String,
      required: true,
    },

    subheading: {
      type: String,
      default: '',
      required: false,
    },
})
</script>

Error:

@pikax Do you have any suggestion here?

This is an issue with vue-test-utils types: https://github.com/vuejs/vue-test-utils-next/pull/274

vuejs/vue-test-utils-next#274 is merged, closing this.


Add note on git repo layout to FAQ (and correct example URL, while we're here)

Thanks Daniel :smile:


switches to ISO 80000-1:2009 for default format

ISO 80000-1:2009 specifies a whitespace or no group seperator at all,
to prevent dot and comma confusion.

Closing because #29 is preferred.


Firestore : projects.databases.documents.batchWrite is missing

Hi, I'm needing batchWrite functionality as described here:
https://firebase.google.com/docs/firestore/reference/rest/v1/projects.databases.documents/batchWrite
But it appears to be missing? I see batchGet is available. I'm using version 0.55

Added in v1 https://pub.dev/documentation/googleapis/latest/firestore.v1/ProjectsDatabasesDocumentsResource/batchWrite.html


Add JWT validation

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

Project coverage is 86.95%. Comparing base (0e36bfd) to head (6049bec).

Files with missing lines
Patch %
Lines

middlewares/jwt.js
37.50%
8 Missing and 2 partials :warning:

services/user-service.js
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #20      +/-   ##
==========================================
- Coverage   89.34%   86.95%   -2.40%
==========================================
  Files          30       30
  Lines         338      345       +7
  Branches       27       29       +2
==========================================
- Hits          302      300       -2
- Misses         36       43       +7
- Partials        0        2       +2

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


fix: move component to components, duplicate articles

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
The React 'components' and 'component' articles are duplicates and should be merged to 'components'. I have done this in this PR.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Upgrade to Spring Boot 2.2.0 M4

and associated dependencies

Shippable failed only b/c folder for test results didn't get created.  Build passed otherwise.


feat: Multi-column notebooks

📝 Summary
Enables multi-column functionality for marimo notebooks! 🚀

🔍 Description of Changes

[x] Toggle columns by selecting the "columns" option in Notebook Menu > App Width
[x] Represent columns in frontend state model by organizing state.cellIds with MultiColumn<CellId>, an array CollapsibleTree<CellId> objects.
[x] Add/delete columns using the + or x button in the column header
[x] Insert column breakpoints on cells
[x] Serialize columns into notebook file using new column property in cell config
[x] Update cell movement actions and drag-and-drop across columns
[x] Update and add unit tests for columns

📋 Checklist

[x] I have read the contributor guidelines.
[x] For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
[ ] I have added tests for the changes made.
[x] I have run the code and verified that it works as expected.

📜 Reviewers
@akshayka OR @mscolnick

/marimo create-test-release

Might just be me, but I think we could use some more contrast between the column header and app background

@wasimsandhu maybe we can increase the slate scale for both the body and header by 1 of the column wrapper? Does that look better?

@mscolnick Just tried it, but I think I've been looking at it too long. Might be good to have some fresh eyes on it

I've moved this to a feature flag, can be added by adding this to your marimo.toml:
[experimental]
multi_column=true


Difficulty in Styling chakra-ui-file-picker Component

I am using the chakra-ui-file-picker component in my project to create a file input. While the component works well for basic use cases, I am facing difficulty in styling the component to match my application's design.
I have tried using Chakra UI's style props and other customization options, but the component seems to have limited support for styling. This is causing inconsistencies in the appearance of my application, and I am unable to achieve the desired look and feel.
I would appreciate it if you could look into this issue and provide a solution or enhancement to the component that allows for better customization and styling options. This would greatly improve the developer experience and make it easier to integrate the chakra-ui-file-picker component into various projects.
Thank you for your attention to this matter.

So what I have done is put those props on the component:
inputProps?: InputGroupProps     inputGroupProps?: InputGroupProps     buttonProps?: ButtonProps
So you can style this components in a separate way. Is this not working for you?

Thanks 😊


[BUG] BUMP_TOKEN not recognized, You are not allowed to deploy to this documentation

I used this GitHub Action several times as expected but I'm now facing an error about the BUMP_TOKEN:
Error: You are not allowed to deploy to this documentation.
please check your --token flag or BUMP_TOKEN variable

I updated it twice from the documentation Settings page and updated the GitHub secret accordingly but I'm still facing the issue.
Failed job on Github: https://github.com/gothinkster/realworld/runs/4666834360?check_suite_focus=true
Related GitHub workflow: https://github.com/gothinkster/realworld/blob/v2/.github/workflows/bump.yml

Hi Gerome, thanks for this feedback.
We've identified the issue: as you are working on a fork, you don't get the secrets from your main repository (it would work if the branch was in your main repo).
We need to enhance this and make diff correctly working on forks. We have several options in mind, we'll obviously keep you informed as soon as we have fixed the issue.
In the meantime, you can either:

temporary remove the api-diff part of your workflow and only keep deploy-doc (which should work as it occurs from your main repo)
add the secret to your own fork, but this means that it won't work for other forks

Also, I think it could be a good idea to change the Bump GitHub action version you load in your workflow to bump-sh/github-action@v1 (instead of<EMAIL_ADDRESS>so it can be automatically updated.
Sorry for the issue!

Thanks for the quick feedback.
As forks are the way to contribute to an open-source project for an external contributor, sharing them a secret isn't that much recommended and it would slow down contribution proccess.
I will update the GitHub Action version indeed!

Hi @geromegrignon, thanks for your contribution.
We published a new version of our GH action to be able to solve your problem. You can now use the diff feature of Bump without any authentication (perfect for PR contributions on public repos).
Please check the latest release changelog to see the example GitHub action workflow which should fix your issue: https://github.com/bump-sh/github-action/releases/tag/v1.1.1
Thanks for your patience and please let me know if you need more info :slightly_smiling_face:

The issue being staled and with no response, I'm closing it.
Feel free to re-open if you still have an issue :pray:. Thank you!


Obscure error messages with default args in application

Compiler version
Scala compiler version 3.3.0-RC1-bin-SNAPSHOT-git-a1729b0 -- Copyright 2002-2022, LAMP/EPFL
Minimized code
➜  dotty git:(test/current) ./bin/scalac -d /tmp ./tests/untried/neg/t4727.scala
-- [E007] Type Mismatch Error: ./tests/untried/neg/t4727.scala:5:8 -----------------------------------------------------
5 |    new C[Int]
  |        ^^^^^^
  |        Found:    Null
  |        Required: Int
  |        Note that implicit conversions were not tried because the result of an implicit conversion
  |        must be more specific than Int
  |
  | longer explanation available when compiling with `-explain`
1 error found

That is
➜  dotty git:(test/current) cat ./tests/untried/neg/t4727.scala
class C[T](x : T = null)

object Test {
  def main(args: Array[String]): Unit = {
    new C[Int]
  }
}

Output
Scala 2 tweaks the message with a hint that default args are involved.
t4727.scala:5: error: an expression of type Null is ineligible for implicit conversion
Error occurred in an application involving default arguments.
    new C[Int]
    ^
1 error

Expectation
It's a small thing, but maybe when default args are re-engineered or tweaked, a hint could be added along these lines.

The longer explanation includes the desired hint in encoded form, as from the tree one can infer it was a default arg at fault.
Experiment with added info in short form, and expanded info in long form.


Add RewriteURIs feature to HTTPRoute

What this PR does / why we need it:
Add the RewriteURIs functionality to HTTPRoute by reusing the code used for Ingress by using konghq.com/rewrite.
Feature gate RewriteURIs still required.
Which issue this PR fixes:
#5576
Special notes for your reviewer:
NA
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[x] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

FYI @pmalek

@dweber019 Could you please update your PR to resolve the conflicts?

please resolve the CHANGELOG.md conflicts

Conflicts resolved.


feat: add $(capture).module.css

Description
Add $(capture).module.css to jsx and tsx in the same way as $(capture).module.less and $(capture).module.scss.
Linked Issues
Closes #241
Additional context
This is a follow-up PR after the closure of draft #184.

Just rebased on top of the newest state of main to fix the linting issues.


python310Packages.garminconnect: 0.1.50 -> 0.1.51

Changelog: https://github.com/cyberjunky/python-garminconnect/releases/tag/0.1.51
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 212383 run on x86_64-linux 1

2 packages built:

python310Packages.garminconnect
python311Packages.garminconnect


Extraneous argument label 'size:' in call

Hello,
I have updated my project to Swift version 3 and NVActivityIndicatorView 9 issues

It seems that the "size:" label is now useless. Any idea?
Edit: I have 15 issues
Vincent

@skrosoft: What Cocoapods version are you using? I guess 1.1.0.rc.2will solve this.

@ninjaprox i am already using version 1.1.0.rc.2.

I think you should remove all your "size:" label.
Example: https://github.com/ninjaprox/NVActivityIndicatorView/blob/master/NVActivityIndicatorView/Animations/NVActivityIndicatorAnimationCubeTransition.swift line 64

It's needed as here. How about clean up project, pods then try again?

Maybe the XCode automatique converter to Swift 3 has modified your code.
I have removed the pod from the Podfile, executed "pod install"
I have added the pod in the Podfile, executed "pod install"
It seems to be now ok, thank you.

 Thanks for reporting! Let me know if encountering any other issues.


Causing AppImage to crash on NixOS

https://github.com/tauri-apps/tauri/blob/af3268a4be69e2dee72ba867ee54bc36d12712e6/core/tauri-utils/src/lib.rs#L299-L309
Heya folks, this bug has been reported before in #7046.
I have tracked down the root cause and it appears to be this check.
I don't think that this is the best way to actually check, whether we're actually running on an AppImage and it certainly causes crashing on NixOS, though I haven't found a cleaner alternative.
I would be very thankful, if someone could take a look and maybe help us figure out how to fix it, as it might also affect some other distributions. ❤

@FabianLars  Why was this bug closed without comment or checkin ?

This issue was opened 3 times so the chain was broken, but it was fixed here: https://github.com/tauri-apps/tauri/pull/7843

@RAVENz46 The change was included in tauri-utils 1.5.0 so make sure you're using the latest tauri versions and run cargo update in the src-tauri dir to force nested deps to update.

Wait, now I realized that tauri-utils seems version 2.2.0-alpha.
Here is I try to launch binglite appimage build.
thread 'main' panicked at '`APPDIR` or `APPIMAGE` environment variable found but this application was not detected as an AppImage; this might be a security issue.', /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tauri-utils-2.0.0-alpha.5/src/lib.rs:207:11
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Same logic applies there, this project uses a quite old alpha version from before the fix was added.

@FabianLars Alright, thanks for you help!


Use the remote branch name

Without this, the plugin opens github with the local branch name. If the remote branch name is different, that will result in a 404 on GitHub.
This also updates the plugin to use the remote associated with the branch, which won't necessarily be the same as the default remote for the repo (which was previously used). If a remote is specified in the user's config, that will still take precedence.

Looks good, thanks! I'm going to make one change after I merge: to display an error if there's no upstream for the current branch.

Perfect, thanks!


Allow imagemin working with builders (for example node-browserify)

It's wrong now master branch state.
Maybe some npm module updated and broken

Master branch state wrong now. Maybe some npm module updated and broken

Thanks for the report. Fixed in https://github.com/imagemin/imagemin/commit/6a548d0ad21e485024509a7d78acc044232bffe3.

Though I understand what you are trying to do, I think the problem should be better fixed in those builders.


source address bind errors fail all upstream retries

When upstream connections are used with a specified source address/port, and the upstream request fails, e.g., due to a timeout, it may happen that all retry attempts fail on a bind error. This is due to the new connections trying to bind to the same source address, while the address/port is apparently still in use even though the logs indicate the deferred deletion has been done before the new bind attempt.
Example logs:
< C9 is bound to the local address <IP_ADDRESS>:56122 >
[C9] connecting to <IP_ADDRESS>:443
[C9] connected
... < about 30 secs later > ...
[C9] ssl read 1031 bytes into 1 slices
[C9] parsing 1031 bytes
[C9] headers complete
[C9] completed header: ...
[C8][S1906562538001471449] upstream headers complete: end_stream=false
[C8][S1906562538001471449] performing retry
[C8][S1906562538001471449] resetting pool request
[C9] request reset
item added to deferred deletion list (size=1)
[C9] SSL shutdown: rc=0
[C9] disconnect. resetting 0 pending requests
[C9] client disconnected, failure reason: <none>
item added to deferred deletion list (size=2)
item added to deferred deletion list (size=3)
[C9] message complete
[C9] message complete
[C9] parsed 1031 bytes
clearing deferred deletion list (size=3)
creating a new connection
Bind failure. Failed to bind to <IP_ADDRESS>:56122: Address already in use
[C10] connecting
[C10] connecting to <IP_ADDRESS>:443
[C10] raising bind error
[C10] closing socket: 1
[C10] purge pending, failure reason: <none>
[C8][S1906562538001471449] upstream reset: reset reason connection failure
[C8][S1906562538001471449] performing retry
item added to deferred deletion list (size=1)
clearing deferred deletion list (size=1)
creating a new connection
Bind failure. Failed to bind to <IP_ADDRESS>:56122: Address already in use
[C11] connecting
[C11] connecting to <IP_ADDRESS>:443
[C11] raising bind error
[C11] closing socket: 1
[C8][S1906562538001471449] upstream reset: reset reason connection failure
[C8][S1906562538001471449] performing retry
creating a new connection
Bind failure. Failed to bind to <IP_ADDRESS>:56122: Address already in use
[C12] connecting
[C12] connecting to <IP_ADDRESS>:443
[C12] raising bind error
[C12] closing socket: 1
[C8][S1906562538001471449] upstream reset: reset reason connection failure
[C8][S1906562538001471449] Sending local reply with details upstream_reset_before_response_started{connection failure}

@jrajahalme I don't have any great ideas on how to fix this. What do you propose? Some kind of fast failure?

@mattklein123 I guess make sure the old socket is closed before retrying an upstream connection to allow bind to the same source address and port? If this is already done, then maybe SO_REUSEADDR on the socket would help?

@jrajahalme I suspect that doing any of that is going to be pretty difficult given the current structure of the code, but I'm not 100% sure. If you want to try to mock something up for discussion feel free.

@mattklein123 I'll play around on the cilium/proxy side, should be pretty easy to add the SO_REUSEADDR option to see if it interferes with anything and if it indeed might help.

@mattklein123 SO_REUSEADDR on the client connection socket alone does not work, since the client sockets remain in TIME-WAIT state after being closed, thus preventing the same 5-tuple being reused. Client socket lingering may be a problem in general as it uses up resources in the kernel even after Envoy has closed the connection. I tested the approach of setting the SO_LINGER option with 0 timeout on the socket before closing due to an error condition, and this allowed retries with the same source address/port without errors:
diff --git a/source/common/network/connection_impl.cc b/source/common/network/connection_impl.cc
index 96a0bc9fa..0bd1fdc5f 100644
--- a/source/common/network/connection_impl.cc
+++ b/source/common/network/connection_impl.cc
@@ -13,6 +13,7 @@
 #include "envoy/event/timer.h"
 #include "envoy/network/filter.h"

+#include "common/api/os_sys_calls_impl.h"
 #include "common/common/assert.h"
 #include "common/common/empty_string.h"
 #include "common/common/enum_to_int.h"
@@ -707,6 +708,23 @@ ClientConnectionImpl::ClientConnectionImpl(
   }
 }

+void ClientConnectionImpl::close(ConnectionCloseType type) {
+  // Avoid sockets lingering in TIME-WAIT state after closing without flushing.
+  if (type == ConnectionCloseType::NoFlush) {
+    struct linger sl;
+    sl.l_onoff = 1;   /* 1 to enable */
+    sl.l_linger = 0;  /* 0 for TCP RST instead of a timeout */
+    auto& os_syscalls = Api::OsSysCallsSingleton::get();
+    const Api::SysCallIntResult result =
+        os_syscalls.setsockopt(ioHandle().fd(), SOL_SOCKET, SO_LINGER, &sl, sizeof(sl));
+    if (result.rc_ != 0) {
+      ENVOY_LOG(debug, "Socket option failure. Failed to set SO_LINGER: {}", strerror(errno));
+    }
+  }
+
+  ConnectionImpl::close(type);
+}
+
 void ClientConnectionImpl::connect() {
   ENVOY_CONN_LOG(debug, "connecting to {}", *this, socket_->remoteAddress()->asString());
   const Api::SysCallIntResult result = socket_->remoteAddress()->connect(ioHandle().fd());
diff --git a/source/common/network/connection_impl.h b/source/common/network/connection_impl.h
index d62f5e898..a55355308 100644
--- a/source/common/network/connection_impl.h
+++ b/source/common/network/connection_impl.h
@@ -232,6 +232,9 @@ public:
                        Network::TransportSocketPtr&& transport_socket,
                        const Network::ConnectionSocket::OptionsSharedPtr& options);

+  // ConnectionImpl
+  void close(ConnectionCloseType type) override;
+
   // Network::ClientConnection
   void connect() override;
 };

At a high level ^ sounds sane to me, but TBH I'm not sure of the implications of doing that. I would be slightly worried that we are not correctly specifying NoFlush vs. Flush in all cases and the other end might start getting RST when it wouldn't before? At minimum I think we would want to runtime/config guard this somehow.
@alyssawilk @PiotrSikora @ggreenway any thoughts on ^?

Why the same source port is being reused? Shouldn't the retrying connection use a new port?

@PiotrSikora see the original issue, this is when the source port is being forced to the same value.

@mattklein123 The implementation above is just a rough proof of concept I cooked up quickly :-). Maybe should add a new ConnectionCloseType::ResetNoFlush (or similar) that the codec layer would use on client connections after streams are reset? ClientConnectionImpl::close() would then detect that, do the SO_LINGER thing, and call ConnectionImpl::close(ConnectionCloseType::NoFlush). This way we only ever reset client connections that need to be reset. Note that Envoy currently never resets client connections, so this is new behavior.
@PiotrSikora I may be overtly cautious, but in general a proxy in the middle using the original source address would not know which source port numbers are already used by the source itself, so it could be unsafe for the proxy (or the kernel beneath) to pick random source port numbers it views as available.
Apart from the use-case with the original source address/port, there is little value in keeping defunct client connections lingering in the kernel. However, if you think adding these resets in the general case is risky, we could restrict them to the client connections which have a specific source address with a non-zero port set?