FormFeedback's style is now working when an input validation is false.

Issue description

components: FormFeedback
reactstrap version #4.8.0
react version #16.2.0
bootstrap version #4.0.0

What is happening?
I applied the  component and added onChange method for an input to check the validity of the input.
But I am getting this html output:

Please use a valid URL.

The error color is not red, it is black.
What should be happening?
The error class should be applied the error feedback div.
Just like this example: https://reactstrap.github.io/components/form/
Code
<Input
	type="text"
	name="domain"
	id="domain"
	placeholder="https://www.test.com, etc."
	value={this.state.domain}
	onChange={this.handleDomainChange}
	getRef={(input) => (this.domainRef = input)}
	required />
{
	this.state.isValidDomain == false &&
	<FormFeedback>Please use a valid URL.</FormFeedback>
}

The versions of reactstrap and bootstrap you are using are not compatible
if you want to use reactstrap v4.8.0, you need to use bootstrap v4.0.0-alpha.6
If you want to use bootstrap v4.0.0, you need to use reactstrap v5.0.0-beta (you can install it via npm install reactstrap@next

I upgraded Reactstrap.
The package.json is like this:
"bootstrap": "^4.0.0",     "css-loader": "^0.28.9",     "html-webpack-plugin": "^2.30.1",     "path": "^0.12.7",     "react": "^16.2.0",     "react-dom": "^16.2.0",     "react-transition-group": "^2.2.1",     "reactstrap": "^5.0.0-beta",     "style-loader": "^0.20.1",     "webpack": "^3.11.0",     "webpack-dev-server": "^2.11.1"
The React code is like this:
<FormGroup> <Input  type="text"  name="project"  id="project"  placeholder="Project"  value={this.state.project}  onChange={this.handleProjectNameChange}  innerRef={(input) => (this.projectNameRef = input)} /> <FormFeedback>Please write at least 3 characters.</FormFeedback> </FormGroup>
The feedback field could not be sen both black or red.

It is adding valid-feedback class. The attributes of class are like this:
.invalid-feedback {
    display: none;
    width: 100%;
    margin-top: 0.25rem;
    font-size: 80%;
    color: #dc3545;
}

https://stackblitz.com/edit/reactstrap-v5beta-otzhpy?file=Example.js

You can also add valid={false} to the input to trigger bootstrap styles to display the invalid feedback
https://stackblitz.com/edit/reactstrap-v5beta-zte92o?file=Example.js

Thanks @TheSharpieOne
It is working.

@TheSharpieOne, Your example doesn't work for me (the FormFeedback msg is not displayed), not sure why (BTW, I cannot have the code run on stackbliz, not sure why, but I believe you that it works properly :)
Any idea why?
My package.json:
{
  "name": "fth-submission-form",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "axios": "^0.18.0",
    "bootstrap": "^4.0.0",
    "firebase": "^4.11.0",
    "lodash": "^4.17.5",
    "react": "^16.2.0",
    "react-addons-css-transition-group": "^15.6.2",
    "react-addons-transition-group": "^15.6.2",
    "react-dom": "^16.0.0",
    "react-redux": "^5.0.7",
    "react-router": "^4.2.0",
    "react-router-dom": "^4.2.2",
    "react-scripts": "1.1.1",
    "reactstrap": "^5.0.0-beta",
    "redux": "^3.7.2",
    "redux-persist": "^4.8.3",
    "redux-promise": "^0.5.3",
    "redux-thunk": "^2.2.0",
    "xml2js": "^0.4.19"
  }

@onurdegerli can you provide how you got it working?
I'm running into this now and it seems that the input never gets the "is-invalid" CSS class applied to it, therefore the  element stays hidden. If I manually add "is-invalid" to the input, I see the error.
I am using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Thanks!

please use reactstrap v5 and try again

Thanks @TheSharpieOne.
I have moved to<EMAIL_ADDRESS>and am still seeing the same problem. The "is-invalid" CSS class is still not being applied to the input.

are you adding the valid={false} prop? https://stackblitz.com/edit/reactstrap-v5beta-zte92o?file=Example.js

I have something like this:
      <Container>
        <Row>
          <Col sm="12" md={{ size: 6, offset: 3 }}>
            <Form>
              <FormGroup>
                <Input type="number" onChange={this.onChange} onKeyPress={this.onKeyPress} valid={false} />
                <FormFeedback>Test Error</FormFeedback>
              </FormGroup>
            </Form>
          </Col>
        </Row>
      </Container>

https://stackblitz.com/edit/reactstrap-v5beta-aupvat?file=Example.js
Input's output: <input type="number" class="is-invalid form-control">

Yes - I see you're example is working.
When I step through the code on my side, it's skipping this if() block: https://github.com/reactstrap/reactstrap/blob/5.0.0/src/Input.js#L70 because state is undefined for me.

Ah - ok. So your example is using 5.0.0-beta. I was using just 5.0.0. When I pull in 5.0.0-beta and re-run, it works. Going back to 5.0.0 seems to break it.
https://github.com/reactstrap/reactstrap/blob/5.0.0/src/Input.js#L70
https://github.com/reactstrap/reactstrap/blob/5.0.0-beta/src/Input.js#L68
Those two are different. 5.0.0 seems to use "invalid" variable, whereas 5.0.0-beta uses "valid".

may bad, that is what I get for grabbing the example from above. Here is an updated one. I recall now that we changed from valid={false} to just invalid
https://stackblitz.com/edit/reactstrap-v5-aupvat?file=Example.js

Ah jeez, I totally missed that in the docs. Thanks for the help!

Sorry I only added to the confusion :sweat_smile:

How can i make FormFeedback visible if we don't have any Input Field to set to invalid?

you can add d-block to the className. it will force it to be displayed.


Multiple Blogs

We have multiple people that need a blog, and the question is this.

Is there an easy way to have multiple users all have a blog from the same url?
Does the current schema support multiple users in the same DB, or
Will the users have to have their own DB

Finally, if doing this in Docker, would you have to spin up multiple instances to accomplish this?
Thanks, and I do not expect that you considered any of this, but it lets me understand the limitations.

Hey @samcov
In short: It is currently "SINGLE MODE" if you wanna say so. If you would spin up multiple docker images with their own database, you could achieve that, but then they all have their unique address, which, I guess, is not what you want.
Simply speaking, there is no concept of "Author" / "User" at the moment. If you are authorized, you can do whatever you want. I initially started this for my own blog, not really expecting much resonance. But I like the idea, even though there might be some work to do.


This dynamic require is a no-go in webpack environments

While this is convenient, it makes the library difficult to use with webpack and other bundlers.

Bummer, I think it could be fixed to work, but given this is meant for NodeGit I'm okay with the change.

Any timeline on when we might be able to have this merged in? Looking forward to using this with webpack.


Form Field Next

@bhoppers2008 #431
Included in this PR:

General design changes
Focus ring support
Form label and helper text
Basic API decisions [RFC]
InputNext basic component
Disabled state for FormField and InputNext
Read only state for FormField and InputNext
InputNext - activation line (new design - always on Input)

Not included:

Static adornments, can come in separate PR to avoid this becoming too large
Validation states, can come in separate PR to avoid this becoming too large
Specific support for controls (out of v1 scope, just demonstrated here)
Specific support for multiple inputs (out of v1 scope, just demonstrated here)
Documentation - will be added when decisions are more solidified

Design question:
With the design changes does the variant prop now have any affect on a FormField which wraps Radio/Buttons or checkboxes? E.g. in this story.
If not then maybe variant is actually a prop of input type components rather than the FormField

Design question: With the design changes does the variant prop now have any affect on a FormField which wraps Radio/Buttons or checkboxes? E.g. in this story.
If not then maybe variant is actually a prop of input type components rather than the FormField?
@bhoppers2008

yeah, variants will come under Input now - one thing happening here though is Dropdown uses Button and the variants for Button (i.e. secondary specifically) doesn't match up with the secondary variant here - although, that could just be a Dropdown variant I guess, that overrides the Button styling within Dropdown, which would be ok, if that's appropriate for Dropdown when used outside of FormField too

@joshwooding
One thing that we discussed and should maybe explore is to use a more composition-based API for FormField e.g.
<FormField>
  My Label
  <Input />
  <HelperText>My HelperText</HelperText>
</FormField>

This would be a pretty big change and so needs more discussion/confirmation. It has a little more setup for the consumer in the simple use case but has certain advantages e.g.

Can pass a ref/prop to each component individually
More flexibility on how to arrange the components
Could work nicely with our Layout components

@joshwooding One thing that we discussed and should maybe explore is to use a more composition-based API for FormField e.g.
<FormField>
  My Label
  <Input />
  <HelperText>My HelperText</HelperText>
</FormField>

This would be a pretty big change and so needs more discussion/confirmation. It has a little more setup for the consumer in the simple use case but has certain advantages e.g.

Can pass a ref/prop to each component individually
More flexibility on how to arrange the components
Could work nicely with our Layout components

I like this a lot, @bhoppers2008 and I were thinking about this yesterday using Grid Layout for alignment of the labels when placed on the left, this would make that possible

I would prefer to use the compositional API that is being discussed. @libertymayc I agree with you here from the looks of the requirements, a component to wrap the controls seems necessary

Q for devs: should we change disabled and readonly props to one 'state' prop that's an enum, since both can't/shouldn't be applied at once?

@joshwooding One thing that we discussed and should maybe explore is to use a more composition-based API for FormField e.g.
<FormField>
  My Label
  <Input />
  <HelperText>My HelperText</HelperText>
</FormField>

This would be a pretty big change and so needs more discussion/confirmation. It has a little more setup for the consumer in the simple use case but has certain advantages e.g.

Can pass a ref/prop to each component individually
More flexibility on how to arrange the components
Could work nicely with our Layout components

I like this a lot, @bhoppers2008 and I were thinking about this yesterday using Grid Layout for alignment of the labels when placed on the left, this would make that possible It does though add more room for error and slightly more work for user (e.g., ensuring states are given to the control and helper text consistently)
we would possibly also need to consider providing a wrapper i.e.
<FormField>
  My Label
  <FormFieldControls>
      <Input />
      <Input />
   </FormFieldControls>
  <HelperText>My HelperText</HelperText>
</FormField>

unless we want to give the responsibility of multi inputs layout being handled by the user - or otherwise recommend which Layout to use for controls in this case

This exploration will come in next PR.

If we're aiming to merge this with three next components, then will need to document the plan of what to do with the existing ones. There are various teams using them now, so migration / adoption should not be an afterthought.
e.g. will next be the ones eventually promoted to core? what's the difference between current input / dropdown and new ones?

seen some changes in chromatic, currently fixing


Harmonic value DC not handled properly by Synergize

In investigating Ross T's question about the meaning of "DC" as a harmonic value, Jari noticed an oddity in the values being sent by Synergize.
I've since compared SYNHCS vs. Synergize and can confirm that

Synergize sends value 31 (0x1f) for "dc"
SYHNCS sends value -2 (0xf4)

Similar mistake is made in the value stored in the edited VCE.

Fixed for 2.3.1

Fixed in 2.3.1


add Column.len, which returns Scalar, instead of Column.len (returning int)

@shwina what is your thoughts on this one? I know cuDF is eager and so it always has the length of columns accessible, but given its scalar class is built to be on device (ignoring the internal implementation of how it handles both host and device access), do you have any thoughts here?

So I expect the length to be used for things like comparisons or equality checking which does work between Scalars and plain Python integers in cuDF. This should be an OK change

approved in today's call


Vite 2.0 beta serves JSON content modified

[ ] Read the docs.
[x] Use Vite >=2.0. (1.x is no longer supported)
[x] If the issue is related to 1.x -> 2.0 upgrade, read the Migration Guide first.

Describe the bug
When running Vite 2.0 (beta), and fetching a JSON file that's part of the source code, the JSON contents are served as an ES module.
Actual content:
$ more firebase.json
{
  "firestore": {
    "rules": "back-end/firestore.rules",
    "indexes": "back-end/firestore.indexes.json"
  },
  "functions": {
    "source": "back-end/functions"
  },
  "hosting": {
    "public": "nope"
  },
  "emulators": {
    "firestore": {
      "port": 6767
    },
    "functions": {
      "port": 5002
    },
    "auth": {
      "port": 9100
    }
  },
  "//": {
    "hosting.public": [
      "Need to provide this, so the '__' Firebase configs can be picked up. The directory does not need to exist."
    ]
  }
}

Served content:
$ curl http://localhost:3000/firebase.json
export const firestore = {
	rules: "back-end/firestore.rules",
	indexes: "back-end/firestore.indexes.json"
};
export const functions = {
	source: "back-end/functions"
};
export const hosting = {
	"public": "nope"
};
export const emulators = {
	firestore: {
		port: 6767
	},
	functions: {
		port: 5002
	},
	auth: {
		port: 9100
	}
};
export default {
	firestore: firestore,
	functions: functions,
	hosting: hosting,
	emulators: emulators,
	"//": {
	"hosting.public": [
		"Need to provide this, so the '__' Firebase configs can be picked up. The directory does not need to exist."
	]
}
};

I cannot see that this would be the intended behaviour. With Vite 1.0 rc 13 the contents were served as JSON.
Reproduction
I have a repo for testing this out. However, take some 10+ mins to get it set up.

clone the vite-2.0-beta-maybe branch
change VITE_20BETA_JSON_WORK_AROUND in init/main.js to false
follow the README instructions
npm run dev
open browser at http://localhost:3000

System Info

vite version: 2.0.0-beta.10
Operating System: macOS
Node version: 15.5.0
Package manager (npm/yarn/pnpm) and version: npm 7.3.0

Reading the docs, I believe the current behaviour is justified - though it may be surprising and there could be a warning about it in the docs.
If one wants JSON to be served unmodified, it should be under the public folder. I don't need that since my need is only for local development, not deployment.

Reading the docs, I believe the current behaviour is justified - though it may be surprising and there could be a warning about it in the docs.
If one wants JSON to be served unmodified, it should be under the public folder. I don't need that since my need is only for local development, not deployment.


Functional testing doc - beta release

Document the functional testing strategy for the WM extension's beta release.
Related to https://github.com/interledger/web-monetization-extension/issues/215
This ticket focuses on testing that the functional areas of the extension work as expected (target audience: ILF and WM community users who typically have more technical insight into the extension): https://docs.google.com/document/d/1CJOBlQjK1Zmdp1K6Pe2DP83uueTgJsBQSJbmDzYDrWw/edit
Info: We have 2 different docs to guide testing, depending on the type of user:

Functional testing doc
Usability testing doc - please refer to ticket #239 for usability testing (target audience: user testing where the concern is UX and usability).

Peer reviews of draft 1 started today, 30 Jul.

here's the markdown work-in-progress branch: test/TestPlan.md

@tselit this is done right? Can we close this ticket?

@tselit this is done right? Can we close this ticket?

Thanks for checking @RabebOthmani .
Content is complete. I'm busy moving to markdown, so the working GitHub branch is not yet merged.

What's the status on this please?

Hi @RabebOthmani PR596 is still cooking. It has been cycling through review feedback & updates since the last update...there were many many comments 😄
Almost there...should be in for further review 26 Sep.

The test plan is finally approved by 1 reviewer.
Awaiting approval from 1 more reviewer.

Received feedback from 2nd review.
Task was blocked by priority focus on the 2024 Summit, from 16 Oct to 1 Nov.

final round of review-updates in progress


Unexpected behavior of docker-gc

1 Run as a binary
Initialization: no /etc/docker-gc-exclude && /etc/docker-gc-exclude-containers files ( empty EXCLUDE_FROM_GC && EXCLUDE_CONTAINERS_FROM_GC ENV)
Run: After the execution, i would get a /var/lib/docker-gc/exclude_container_ids file containing all of the existing containers, while /var/lib/docker-gc/exclude_ids is empty, which is not expected.
2 Run as a docker container
Simple docker run --rm -v /var/run/docker.sock:/var/run/docker.sock spotify/docker-gc is not gonna work.
How could it possibly function well without accessing EXCLUDE_FROM_GC ENV (sort of stuff)? 'Cause it's located in /etc/docker-gc-exclude-containers.
We need a volume at least.

@dalanlan I think this PR fixes 1 right? https://github.com/spotify/docker-gc/pull/46

It should, which confused me a lot.

Hmm.. good to go then.


Multiple fields in Message may be broken

For example, in previous versions, the Bids field of the Message is defined as following link:
Bids [][]string `json:"bids,omitempty"`

In the latest version, it is defined as link:
Bids [][]SnapshotEntry `json:"bids,omitempty"`

where SnapshotEntry is a tuple of 3 values. Essentially it makes Bids field match [][][]string and it will obviously failed to unmarshal the json message. Is this a bug or I misunderstood the intention?

Thanks for catching this. It was just added recently. Should be fixed in: https://github.com/preichenberger/go-gdax/commit/b9e9c04fb8b4614f02af36fd4eabe81a36bc0eda


Adding DES (Data Encryption Standard) using python

Is your feature request related to a problem? Please describe.
Yes it is.
Describe the solution you'd like
I would like to implement the DES in python.
Additional context
The Data Encryption Standard (DES) is a symmetric encryption algorithm that operates on 64-bit blocks of data using a 56-bit encryption key. It employs a Feistel network structure, dividing the input data into two halves and applying a series of rounds using subkeys derived from the main key. Each round includes substitutions, permutations, and bitwise operations to ensure diffusion and confusion, making the data resistant to cryptographic attacks.

@Kumar-laxmi Please assign me this !

Assigned!
@mochiron-desu : C++ & Python


Devices revert to default room after reboot

Can someone help me? Every time my raspberry/homebridge restarts all my sonos speakers are loaded back in the default room. All other accessories from other plugins stay where i’ve put them, only the sonos zoneplay speakers revert back to default room (and my automations lose the speaker settings too).

How do you restart Homebridge?  What other plugins are you using?
Homebridge ZP is a dynamic platform plugin, that persists the accessories in the user directory under accessories/cachedAccessories.  If that file is lost or corrupted, Homebridge will start its HAP server without exposing the Homebridge ZP accessories, causing HomeKit to remove them.  When Homebridge ZP has discovered the zone players and (again) exposes the accessories, HomeKit will treat them as new.

Restart through the homebridge-config-ui. Other plugins i use are tahoma, lg webos tv, ics-1000 and tado ac. Maybe the cached file gets lost or corrupt. Is there any way to double check it? Or should i do something to make your plugin save the players to the cached accessories? Thanks in advance

cachedAccessories should be saved automatically.  Please capture a debug log file restarting Homebridge and attach that.

I hope this will help.
homebridge.log.txt

homebridge.log.gz

here is my cachedAccessories file, don't know if that's needed, but the more info the better I guess.
cachedAccessories.zip

Looks like it's not happening on evert restart, but sometimes Homebridge doesn't seem to shutdown cleanly.
You should be seeing the following messages on a clean shutdown:
[15/02/2021, 22:53:58] Got SIGTERM, shutting down Homebridge...
[15/02/2021, 22:53:59] [Sonos] closed http://<IP_ADDRESS>:36007/notify
[15/02/2021, 22:54:03] [Sonos] goodbye

And on startup:
[15/02/2021, 22:54:34] [Sonos] restored 3 accessories from cache
[15/02/2021, 22:54:34] [Sonos] restored 1 accessories from cache

However, sometimes the goodbye message is missing, indicating that NodeJS was stopped before Homebridge ZP did its cleanup.  I've only ever seen this when other plugins would break Homebridge's shutdown sequence, by installing their own handler for SIGTERM.

here is my cachedAccessories file, don't know if that's needed, but the more info the better I guess.

Looks like Homebridge ZP is the only plugin using that.

Hmm okay, is there any way for me to correct this?

Run Homebridge ZP as only plugin and check that the issue no longer occurs.  Then re-enable the other plugins one by one to see when the issue re-occurs.  Run the offending plugin in a separate Homebridge instance.  Alternatively, run Homebridge ZP in a separate Homebridge instance, or in a child bridge (new feature in the latest Homebridge beta).

I will put homebridge zp in a child bridge instead when homebridge is out of beta. Looks like the easiest way. Thanks.


Fix IST0144 regression

To fix https://github.com/istio/istio/issues/32474

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
ab6890069cf5a29e16159b0766993c714e2db562
link
/test unit-tests_istio

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

/test unit-tests_istio

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
ab6890069cf5a29e16159b0766993c714e2db562
link
/test integ-telemetry-k8s-tests_istio

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

/test integ-telemetry-k8s-tests_istio

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
ab6890069cf5a29e16159b0766993c714e2db562
link
/test integ-security-multicluster-tests_istio

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

/test integ-security-multicluster-tests_istio

In response to a cherrypick label: new pull request created: #32529


[CLOSED] Cannot find class information for Foldable/Traversable/Monoid

 Issue by sweirich
Thursday Oct 12, 2017 at 19:10 GMT
Originally opened as https://github.com/antalsz/hs-to-coq/issues/26

When I translate ghc/compiler/Util/Pair.v   (in examples/ghc)
I get these messages:
(* Translating `instance Data.Foldable.Foldable Pair' failed: OOPS! Cannot find
   information for class "Data.Foldable.Foldable" unsupported *)

(* Translating `instance Data.Traversable.Traversable Pair' failed: OOPS! Cannot
  find information for class "Data.Traversable.Traversable" unsupported *)

(* Translating `instance forall {a}, forall `{GHC.Base.Monoid a},
  GHC.Base.Monoid (Pair a)' failed: OOPS! Cannot find information for class
 "GHC.Base.Monoid" unsupported *)

Do we need to do something special to tell hs-to-coq where to find these classes?

 Comment by antalsz
Thursday Oct 12, 2017 at 19:15 GMT

We need to add support for this in hs-to-coq as part of #23.

 Comment by nomeata
Thursday Oct 12, 2017 at 19:26 GMT

Temporarily we can do what we do for Make etc.: Hardcode them in the code.

 Comment by sweirich
Thursday Oct 12, 2017 at 19:30 GMT

Where is this hardcoded? This is not urgent (yet).

 Comment by nomeata
Thursday Oct 12, 2017 at 19:49 GMT

https://github.com/antalsz/hs-to-coq/blob/master/hs-to-coq/src/lib/HsToCoq/ConvertHaskell/Monad.hs#L109
(There are partial bits about Monoid and Foldable there from earlier experiments, but they lack some methods, and the name should be fully qualified.)

 Comment by sweirich
Thursday Oct 12, 2017 at 19:52 GMT

Thanks.  We can wait for #23 now, but if it is blocking, I'll know what to do.

 Comment by nomeata
Sunday Apr 08, 2018 at 03:44 GMT

Closing this in favor of #23


Updates to Jakarta Enterprise Web Services spec Chapters 5-8

Signed-off-by: Syed Wadood<EMAIL_ADDRESS>

for #118

...and I'm leaving section 7 for some other day. One thing which came to my mind when I see deployment descriptors - where are their sources? should they be in this project? who is going to update them for EE 9? Should the updated version remove every JAX-RPC related aspect too (I blindly recall there's defined service class name somewhere and probably also type)?

To answer my own question wrt schemas - they’re at https://github.com/eclipse-ee4j/jakartaee-schemas/tree/master/jakartaee9/src

I just committed updates to address all review comments.  Please review and let me know if I missed any updates or if there are any more changes that need to be made. Thanks.

Made some formatting updates and also removed references to "javax.rmi.RemoteException" as it is only specific to JAX-RPC.

* '

Yes, the picture in 5.3.4 was removed intentionally because it only applied to JAX-RPC
I will replace "Java 2 security" with "Java security" in Chapter 6.

I just committed updates to address the last set of review comments from lukasj.


[GSD-2022-1006458] GSD Request

--- GSD JSON ---
{
  "vendor_name": "Apple",
  "product_name": "Mac OS",
  "product_version": "12.6",
  "vulnerability_type": "information disclosure",
  "affected_component": "background photo processing",
  "attack_vector": "social engineering to save an image file",
  "impact": "system loads URL",
  "credit": "@hodgesmr",
  "references": [
    "https://twitter.com/hodgesmr/status/1577650545107533826"
  ],
  "reporter": "kurtseifried",
  "reporter_id": 582211,
  "notes": "",
  "description": "In Apple Mac OS version 12.6 a reported information disclosure exists in the background photo processing (e.g. searching for known faces, indexing files by time and location taken) that can be attacked via social engineering, e.g. if an image with a QR code is saved and then processed Mac OS will reportedly process the QR code data, and if it is a URL it will load the URL disclosing information about the system (user agent, IP address, etc.)."
}
--- GSD JSON ---

/cc @kurtseifried

This issue has been assigned GSD-2022-1006458


About PlaceHolder Token

Hello,
I found you add a placeholder token  to the tokenizer using the follow code:
  tokenizer._add_tokens(["<PH>"], special_tokens=True)
  tokenizer.placeholder_token = "<PH>"

And the placeholder token is used in the follow code:
    encoded_ph = tokenizer.convert_tokens_to_ids(tokenizer.placeholder_token)

    if len(truncated_rewrite) > len(truncated_query):
        truncated_query   += [encoded_ph] * (len(truncated_rewrite) - len(truncated_query))
    else:
        truncated_rewrite += [encoded_ph] * (len(truncated_query) - len(truncated_rewrite))

However, the index of this placeholder token has exceeded the size of the pre-trained vocabulary, so the embedding representation of this token is not available on the embedding table. How can this problem be solved? Do you need to replace placeholder token with existing tokens in the vocab? So what should I replace it with?

Hello, xyltt
Thanks for the detailed question.
As you said, I added the special token to the tokenizer's vocabulary and the model would learn an embedding representation during the training phase by
model.resize_token_embeddings(len(tokenizer))
You can refer to this line. Note that I didn't use this one in the older version of Transformers library (I don't know why exactly but it worked without issues). But it is required in the current versions
Thanks for your attention to our work.

Thanks for your reply!
I also have some questions about the coqa dataset. I want to make sure that this released code is also applicable to the coqa dataset? I found that the "class_num" for coqa isn't equal to "class_num" for quac. So how many are the "class_num" for coqa? And the fourth label is ignored when calculating the "class_loss" as the following code:
else: # coqa
class_loss_fct = CrossEntropyLoss(ignore_index=3)
class_loss = class_loss_fct(class_logits, is_impossible)
I want to know why, and what is the ignored label.
I also noticed that the "class_logits" is not being used during inference for quac dataset. Is the "class_logits" used during inference for coqa dataset?


Small change to monte_carlo.c

It looks like this code is fine? Is there anything left to be done here @berquist ?

I am happy.


Add commandir to filesystem section

commandir is a library offering mkdir and rmdir functions with the following features:

Promise based
Idempotent
mkdir is recursive
They encourage good software design and error handling by communicating exactly which directories were created or deleted, allowing for proper cleanup in the event the program aborts later on.

Other modules offer the first three features, but I am not aware of any modules offering the final feature.
I came across the need for this implementation when I noticed a program I wrote could possibly encounter an error before completing and leave an empty directory (which was going to be populated) on the user's filesystem. That's just not a nice thing to do.

@sindresorhus it would be great to hear your thoughts 😺


Crashlytics contains usage of insecure API calls like memcpy.

Step 0: Are you in the right place?

For issues or feature requests related to the code in this repository
file a Github issue.

If this is a feature request please use the Feature Request template.

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general (non-iOS) Firebase discussion, use the firebase-talk
google group.
For backend issues, console issues, and other non-SDK help that does not fall under one
of the above categories, reach out to
Firebase Support.
Once you've read this section and determined that your issue is appropriate for
this repository, please delete this section.

[REQUIRED] Step 1: Describe your environment

Xcode version: 13.2.1
Firebase SDK version: 8.5.0
Installation method: CocoaPods
Firebase Component: Crashlytics
Target platform(s): iOS

[REQUIRED] Step 2: Describe the problem
Our security team was using static code scanner MobSF for checking our app binary. They have found high secure issue, that .ipa contains memcpy. This is hight vulnerability. Any comments/deadline when it will be fixed?
Steps to reproduce:

Add firebase to your app (we use cocoapods).
Archive
Scan .ipa using mobSF

What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
// TODO(you): code here to reproduce the problem

This is a duplicate of #8454. We haven't see evidence of a vulnerability with those usages of memcpy. Please read #8454 and associated links for additional context.


changing listing preferences has no effect in the content menu

steps to reproduce

go to your local volto build content menu (or volto.kitconcept.com/contents
sort elements by creation date or any other setting
-> has no impact on the listing
-> expected: elements should get reordered depended on your settings

@iFlameing pls check the functionality and write a Cypress test for it.

@steffenri @tisto I tested in my current local environment and it is working fine :)


Add dev dependencies required to run push scripts

Added devDependencies for change-emitter, hoist-non-react-statics, and jest-cli that are needed to run the push scripts. This was approved in a comment in #522 .

Codecov Report

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

@@           Coverage Diff           @@
##           master     #526   +/-   ##
=======================================
  Coverage   88.94%   88.94%
=======================================
  Files          53       53
  Lines         389      389
=======================================
  Hits          346      346
  Misses         43       43

Continue to review full report at Codecov.

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

Why I pushed without any issues before, what changed?

Did you used yarn for install?

As push just run tests and deps above are already exists under recompose package. Also what the need of jest-cli as jest works well without, https://github.com/facebook/jest where here any words about jest-cli?

Maybe you have these deps installed globally, so don't see the issue? I was unable to push until I added these deps.

BTW I tried yarn install and I get what appears to be an infinite loop:

$ node scripts/installNestedPackageDeps.js
yarn install v1.0.2
yarn install v1.0.2
warning package.json: No license field
warning package.json: No license field
yarn install v1.0.2
warning No license field
[1/4] Resolving packages...
warning No license field
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.38s.
success Already up-to-date.
Done in 0.48s.
[1/4] Resolving packages...
success Already up-to-date.
$ node scripts/installNestedPackageDeps.js
yarn install v1.0.2
warning package.json: No license field
yarn install v1.0.2
yarn install v1.0.2
warning package.json: No license field
warning No license field
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.56s.
warning No license field
[1/4] Resolving packages...
success Already up-to-date.
Done in 0.56s.
[1/4] Resolving packages...
success Already up-to-date.
$ node scripts/installNestedPackageDeps.js
yarn install v1.0.2

Which continues to call node scripts/installNestedPackageDeps.js repeatedly.

I have no global deps. Last PR I did yesterday. I saw infinite loop in the past, break it and all will be fiine :-)

Not sure if it matters, but I'm on MacOS. This is what I get if I try to push without jest-cli:
$ git push

> husky - npm run -s prepush
> husky - node v7.8.0

yarn run v1.0.2
$ cross-env BABEL_ENV=rollup rollup --config scripts/rollup.config.js --environment BUILD:es,PACKAGE_NAME:recompose
✨  Done in 4.12s.
module.js:472
    throw err;
    ^

Error: Cannot find module '/Users/achou/Code/recompose/node_modules/jest-cli'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at getJest (/Users/achou/Code/recompose/node_modules/jest/node_modules/jest-cli/build/cli/getJest.js:22:12)
    at Object.run (/Users/achou/Code/recompose/node_modules/jest/node_modules/jest-cli/build/cli/index.js:39:48)
    at Object.<anonymous> (/Users/achou/Code/recompose/node_modules/jest/node_modules/jest-cli/bin/jest.js:14:25)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)

> husky - pre-push hook failed (add --no-verify to bypass)
> husky - to debug, use 'npm run prepush'
error: failed to push some refs to 'git@github.com:acchou/recompose.git'

And Im on mac :-)

I'll check now with latest yarn (I use outdated)

I just checked with latest yarn and clean recompose, all is fine

As you could see npm -g list | grep jest gives nothing

I just tried to re-fork this and a test push worked. I don't know how I got my previous install in a bad state, but in any case I'll consider this closed.


outDir unable to inherit vite configuration

// vite.config.ts

export default defineConfig({
  build: {
    outDir: 'dist-example'
  },
  plugins: [
    banner('/* test */'),
  ],
})

I think if the plugin doesn't have outDir set, it should default to vite's outDir configuration, but the actual result is that the plugin ourDir defaults to dist all the time, and the reason for that is because it's being forced to format to the default value of dist in src/libs/formatConfig.ts
https://github.com/chengpeiquan/vite-plugin-banner/blob/312dec8adbb70e64dd8d5247a0f2e67f8c16a5b6/src/libs/formatConfig.ts#L19
Causes this || code in src/main.ts to be redundant
https://github.com/chengpeiquan/vite-plugin-banner/blob/312dec8adbb70e64dd8d5247a0f2e67f8c16a5b6/src/main.ts#L47-L48
BTW, is the outDir config item really needed, it makes more sense to always use vite's outDir, right?

The plugin's outDir is optional and was previously inherited, so it only needed to be specified when necessary.
I ran the latest vite demo and reproduced this problem. It should be that the configuration was not inherited after a certain version of Vite was upgraded.


Youtube video gets refreshed every time the 'Solutions' tab is clicked

Ideally, we want the youtube video to not disappear when a tab is clicked and the page is dynamically updated.
Maybe a fix could be to track the timestamp before we update the page. Then reload that timestamp, if it exists, into the embedded video's url.

dont think it can be fixed, since we're injecting the video into the solutions tab.


Fix the URL used for the Docker Pull shield

🗣 Description
This PR fixes the image URL for the docker pulls image shield.

💭 Motivation and context
The URL incorrectly referenced cisagov/vdp-scanner-docker when the image is pushed to Docker Hub as cisagov/vdp-scanner.

🧪 Testing

Automated tests pass. I confirm that the image shield works as expected in this branch.

✅ Checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

N.B. The tests on this will fail because of the issue that is resolved in #18 . Since this is a simple URL change in the README I will just merge without passing all the tests since the lint job completes successfully.


Prevent repeated calls of "onComplete"

Once a flow was completed, navigating back through the flow by popping causes the onComplete handler to fire again on every pop.
I can prevent this by manually wrapping my callback code into a check whether the current state is in fact the "last" state before actually executing its logic, but would prefer if this was built-in, e.g. by setting the private _completed property to false automatically anytime a _history state gets restored.
Am I missing something that would make this a bad idea?

Hi @Lootwig 👋
Thanks for opening an issue!
Can you provide a link to a minimal reproduction sample? Thanks!

Run
Press "next"
Press "complete" -> console logs execution of onComplete
Press back button in appbar -> console logs execution of onComplete

import 'package:flow_builder/flow_builder.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key}) : super(key: key);

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  final FlowController<int> _controller = FlowController(0);

  @override
  Widget build(BuildContext context) {
    return FlowBuilder<int>(
      controller: _controller,
      onComplete: (_) {
        print('COMPLETING FLOW');
      },
      onGeneratePages: (state, pages) {
        return [
          ...Iterable<int>.generate(state + 1)
              .map((_) => const MaterialPage(child: FlowWidget())),
        ];
      },
    );
  }
}

class FlowWidget extends StatelessWidget {
  const FlowWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    final flow = context.flow<int>();
    return Scaffold(
      appBar: AppBar(),
      body: Center(
        child: ElevatedButton(
          onPressed: () {
            flow.state < 1
                ? flow.update((state) => state + 1)
                : flow.complete();
          },
          child: Text(flow.state < 1 ? 'NEXT' : 'COMPLETE'),
        ),
      ),
    );
  }
}

@Lootwig I took a closer look and was able to reproduce the issue. Once you complete a FlowController you will not be able to interact with the controller anymore. If you override onComplete then FlowBuilder assumes that you will handle dismissing the flow and handling the result manually. In this case, nothing happens because you're just printing but in practice you should either redirect the user to some other route with the result or remove onComplete and let FlowBuilder handle it for you.
I will push a fix to throw a StateError if you interact with a FlowController after it has been completed since that should never happen.
Let me know if that helps and thanks for reporting this!

Interesting, that's basically saying that for my particular use case, where a user might go back to a particular step of the flow and make changes, completing is not an intended operation in the first place?
E.g. whatever I'm doing in the last step should be a result of just another update?

Interesting, that's basically saying that for my particular use case, where a user might go back to a particular step of the flow and make changes, completing is not an intended operation in the first place?
E.g. whatever I'm doing in the last step should be a result of just another update?

Yup that’s correct! If you don’t want the flow to end, then you can just use the update API 👍


sheet name should not be camelized

https://github.com/randym/axlsx/commit/7f39700f30ffdf7d3933e61bf244a41aeb8dee6c

fixed by the offical: https://github.com/randym/axlsx/pull/494


StatusBar: Code Cleanup

Description

removed StatusBarBranchPicker & StatusBarPullButton since they are no longer implemented.
updated folder structure for more clarity.

Checklist

[x] I read and understood the contributing guide as well as the code of conduct
[x] My changes generate no new warnings
[x] My code builds and runs on my machine
[x] I documented my code
[x] Review requested

What you mean no longer implemented?

What you mean no longer implemented?

The branch picker has been moved to the toolbar and removed from the statusbar.


Windows 10 issue

I know this early but I wanted to point out a problem I got after upgrading to windows 10 (I reinstalled VBox and Boot2Docker to be sure)
When I boot2docker init I have an error message, this is what the machine is saying

With further investigations I found that the machine configuration seems to be a bit brokent

It's broken using boot2docker or docker-machine. If you need me to do more test and show more logs I can do it

Follow instructions on https://www.virtualbox.org/ticket/14040#comment:36


Error with polymorphic record fields and eqtypes

Here is the code snippet
noeq type test = {
  field : a:Type -> a -> a
  }

val foo : test -> unit
let foo t = t.field unit ()

I got Expected expression of type "Type"; got expression [...] of type "Prims.eqtype"

Hi Theo:
The type test is polymorphic in one universe (the universe of the type argument to field. As a result, the declaration val foo is also polymorphic in that universe. However, the let binding is not -- it instantiates that universe explicitly with u#0, the universe of unit. And so, F* gives an error. This happens because F* generalizes the universe of val independently of the universe of let (see #604).
A workaround is to just work with let bindings:
noeq type test = {
  field : a:Type -> a -> a
  }

let foo (t:test) = t.field unit ()

But if that's not possible (e.g. when you are writing val foo in an .fsti file), you can instantiate the universe for test explicitly, like:
noeq type test = {
  field : a:Type -> a -> a
  }

val foo : test u#0 -> unit
let foo t = t.field unit ()

I am closing this issue since #604 covers it already, please let us know if you face more issues. Thanks!

Also, --print_universes flag when running F* on the example would have given a better error message.


Patternfly upgraded to v3.9.0

Now we're back with the proper gem version!
@himdel @epwinchell please review

Looks good

@miq-bot add_label ui

@skateman seems like there was a change in patternfly where selectpicker doesn't set bs-select-hidden on the original select => failing tests ;)
The vmdb failure looks rather unrelated otoh..

I'm looking at the test failures but...

Updated the tests to reflect the new selectpicker structure (and cleaned up those elem[0][2] in favor of jquery selectors and descriptive variables).
The toolbar is still broken though..

.. to track the problems ..

[ ] failing tests caused by different selectpicker structure
[ ] view toolbar not being positioned to the right
[ ] missing margin after separator (also in master, fixed by #9753)
[ ] uneven icon widths in toolbar dropdown causing text not to be aligned (also in master)
[ ] toolbar too tall

Let's wait for the angular toolbar to be merged, then we should upgrade directly to 3.9.0. @himdel @epwinchell ?

@skateman I totally agree.

Sure, no rush :) might be easier to fix the view toolbar after.

@skateman you can replace that last commit by an update of manageiq-ui-components to 0.0.6.

@himdel yup, and also the pf version to 3.9.0 :)

Found one more issue (maybe pf-3.9?) .. hovering over the active menu item (secondary or tertiary) shows a black top border

This also happens in the patternfly 3.9.0 test pages, cc @jeff-phillips-18

https://github.com/patternfly/patternfly/issues/442#issuecomment-243108646

@skateman nice, that's probably everything then..
Should I merge, or do we wait for 3.10 (2 days I guess?)?

@epwinchell can you also check this? LGTM

@epwinchell @himdel pin/unpin buttons fixed

@miq-bot remove_label wip

FYI, we want the pin icon to be used. Currently PatternFly has the arrows rather than the pin - so we should change that once the upgrade is complete

To change to pins for the collapse button in the header you can override with:
.secondary-collapse-toggle-pf {
&:before {
content: '\f08d';
}
&.collapsed {
&:before {
-ms-transform: rotate(45deg);
-webkit-transform: rotate(45deg);
transform: rotate(45deg);
content: '\f08d';
display: inline-block;
}
}
}

👍

Not seeing any more UI breakage, merging..
@skateman We should however upgrade to 3.10 soon because of that active menu item bug :)

@jeff-phillips-18 @serenamarie125 any idea when that pin change will get into patternfly?

@himdel I will talk to Leslie this week.  There was some reluctance to taking this, but based on the user feedback that I've been getting from CloudForms customers, I'm still suggesting we go with it.  I'll get back to you


Unrecognized labels cancel entire workflow

From https://github.com/CloudSnorkel/cdk-github-runners/issues/72#issuecomment-1289480905

In your case it sounds like it's because we expect every job with the self-hosted label to also have a label we recognize. It sounds like you have multiple installations of cdk-github-runners in different accounts, each implementing different labels. That means some of the installations will not recognize the label and cancel the job. We can probably add a flag to disable this behavior. Let's do this in a separate ticket.

@laxgoalie392

thanks for opening this up!
you're assumptions are correct. I actually have multiple installations in multiple aws accounts (multiple github orgs needing to deploy to multiple aws accounts). i thought the label would appropriately isolate them, but it seems to have caused more of a mess.

i've validated that this fix works for me! you are lightning fast, once again!

@kichik when do you think you will cut another release?

I just cut a release for you. I was under the impression you can use my changes without a release so I was waiting for a few more things to make it bigger. I'm curious, how do you test it usually without a release?

thanks! i usually just look at the changes in the PR and apply them manually. not a perfect verification method but quickly does a good enough job i think

:O thanks @laxgoalie392 - had the same issue - we had pretty weird issues because it even cancelled the jobs for other runners that were not created via this solution ...


[PrintAsObjC] Add SWIFT_METHOD_FAMILY(init) when required

Initializers that don't look like init methods to ARC need to have
SWIFT_METHOD_FAMILY(init).
Also tighten up the check for init-like methods to not consider e.g.
initializeFoo to be an init-like method.

Resolves SR-3468.

@swift-ci Please smoke test

@swift-ci Please smoke test


Resolving "(node:58407) UnhandledPromiseRejectionWarning: TypeError […

…ERR_INVALID_OPT_VALUE]: The value "undefined" is invalid for option "saltLength""
This is probably not the correct solution, but it seems that this function (sign) is often receiving an invalid salt length and causes a failure of the entire arweave / smartweave javascript library.

@cedriking this is a very bad solution for Issue #78. Probably not something we should merge - just wanted to show you what we've been doing as a workaround.


crash when field package goes through port

Exact error message

undefined is not an object (evaluating '_v0.summary')
Open the developer console for more details.

Minimal code I could produce that would cause the error
This only happens when the initial model came through a port.
If an equivalent model is defined in elm itself it works just fine (see repository)
I am not sure it has something to do with the field called 'package' but changing the name of the field to something else fixes the problem.

Is it fair to summarize this as "sending a record with field package through a port causes a crash"?
If so, can we get the example down smaller? Or can we refine the summary? Maybe the field must be in the outermost record, but it does not matter if it is in a subrecord? What does the relevant generated code look like?

I have tested a little more:

The data at package key does not need to be complex, aka a record, I tried it with a String and that didn't work either.
The reason it crashes is that instead of returning whatever was at that package key it returns undefined. (Or at least that's what it prints if you print is)
It is not limited to keys of the outer record, that same happens in sub records.

I've simplified the code for the example with the String at the package key in the subrecords branch.

So if I understand this correctly,
port doesNotWork : { package : Int }
port doesNotWork = { package = 5 }

port works : { packag : Int }
port works = { packag = 5 }

This implies that package should be added to this list of reserved words. If the misspelled packag doesn't work either, then the bug is completely different. What happens with this code?
port package : Int
port package = 5

No @mgold, read the original code I submitted. All of these work. In pure Elm there's no problem at all with using package as a record field name.
The only instance where it doesn't work, is if the data itself is a JavaScript object and comes through a port. (Again, look at the original code).
Aka
port works : { package : Int }
port works = { package = 5 }

works without fail
but
port externalPort = { package : Int }

and
Elm.fullscreen(Elm.ModuleName, { externalPort: { package: 3}});

Ah, sorry about that. For incoming ports, it works if you misspell it as packag or whatever?

Yes.

Can we try to find out why JS is doing this? What browser are you using? Is it only a node.js thing? Is there some doc describing this behavior?

Tested it with Firefox, Safari, Chrome and Phantomjs. All display the same behaviour.

Seems like we can merge this with #1010. In that case we built a list of known reserved words based on some JS docs. What is the documentation here so we can understand why package is reserved?
Once we find that, maybe we can merge with the other issue.

Well, it is a slightly different issue since #1010 causes runtime crashes even when defined within Elm, whereas this particular issue only occurs if the object was instantiated in javascript directly.

Also the object can be evaluated in JavaScript itself. (I tested this just now)

Is this still true in 0.17? If so, can we reopen with all the crucial information from the comments here consolidated in a clear way.


Polish translation (little fixes)

Thanks for contributing!
Your translation will be in the next update [Could take very long until then]


Created LICENSE.html

Created LICENSE.html with MIT-License text. Added Home-Button.

Seems like i have withdrawn another commit from another project. However, it doesn't have any effects.


Leaf Tags for common Form elements

https://laravelcollective.com/docs/5.3/html
Required:

[ ] - Form Open / Close
Missing: Form open should be able to print out CRSF tokens

[X] - Text Input
[ ] - Textarea Input
[X] - Email Input
[X] - Password Input

[ ] - Number Input
Missing: Proper parsing of input value
[ ] - Range Input

[ ] - Checkbox
[ ] - Radio Button
[ ] - Radio Buttons Group

[ ] - Select
Should support both singular and multiple selections

[ ] - Nodes UI Date Input
[ ] - Nodes UI File Input
[ ] - Nodes UI Range Input
[ ] - Nodes UI Color Input

[ ] - All inputs must support an additional "attributes" array of key/values

Nice-2-have:

[ ] - Hidden Input

[ ] - Buttons
_Should support types "submit", "reset" and "button"

[ ] - Native Date Input
Currently the "native" html5 date input is not supported in all browsers
[ ] - Native Color Input

[ ] - Non-groups (no wrapping of form elements with labels / validation errors)
[ ] - Labels
[ ] - Validatin Errors (.help-blocks)

FormNumberGroup
//TODO Does this use fieldset?["value"]?.string ???

argumentToHtmlAttributes has force unwraps


Documentation not updated?

Your documentation link points to https://google-cloud-python.readthedocs.io/en/latest/monitoring/index.html . The Stackdriver examples there do not work with 0.29.0. Specifically, I am looking for API documentation/examples for fetching time series data for Stackdriver agent metrics.
Elsewhere, I have run into cases where the documentation is marked as Alpha whereas the product is marked as beta.
I'm using google-cloud-monitoring 0.29.0

@talonx Thanks for the report!
For the record, google.cloud.monitoring is still in alpha status as of the 0.29.0 release.

@crwilcox Can we call this good with the redirect to https://googlecloudplatform.github.io/google-cloud-python/?

@tseaver , these automagically redirect to github.io so this issue should be resolved
@talonx if you still have issues feel free to reopen.


How to use Web Share API?

Title: How to use Web Share API?
Outline
Many modern developers are unaware of the web share API. Using the Web Share API, you can make your content shareable. It enables us to use native share dialog of a device directly from a website or web application. This API can also be used to share files. In this tutorial, you'll learn what is Web Share API and how to use it with some examples.
Key takeaways:
By the end of this tutorial:

one can discover about web share API.
one can add share button to their application and make their content sharable.
one can understand how to enable sharing the elements of their web page.

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

To help avoid a backlog queue (and longer review times) we are currently only accepting ONE article TOPIC/PR approved at a time 👍. We can re-open this topic - once the 1st one has been merged/published.


WASAPI Input Support for CNFA

It's finally in a state where I'm comfortable making a pull request. :tada: There are definitely still issues and shortcomings in this driver, but all of the ones I'm aware of are documented in comments (marked TODO).
As of now, only input (WASAPI -> CNFA) is supported, from capture devices (e.g. microphones), and render devices (e.g. speakers) operating in loopback mode. Output (CNFA -> WASAPI) is currently not supported, but I will work on getting this done as well.
So far I have only tested this with ColorChord, and it seems to work well there. Thanks to Sam, it also compiles and runs fine with TCC. ColorChord needed a few tweaks to get some stuff working right, I'll submit a PR for those changes soon as well.
Take that, past me. Also, funny Charles, 50-60 lines?
Many thanks to @sellicott for his help!

This looks good.  I will try to fix the WinMM stuff later.


0.32.0-b15

Beast changes and corresponding rippled changes

[Current coverage][cc-pull] is 69.04%

Merging [#1722][cc-pull] into [develop][cc-base-branch] will increase coverage by <.01%

2 files in src/ripple were modified. more

Misses -5

2 files (not in diff) in src/ripple/websocket were modified. more

Misses -7
Hits +7

3 files (not in diff) in src/ripple were modified. more

Misses +4
Hits -6

@@            develop      #1722   diff @@
==========================================
  Files           863        864     +1
  Lines         61973      61973
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          42770      42786    +16
+ Misses        19203      19187    -16
  Partials          0          0

[][cc-pull]

Powered by Codecov. Last updated by [846cbf8...1fe9839][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ripple/rippled/branch/develop?src=pr
[cc-compare]: https://codecov.io/gh/ripple/rippled/compare/846cbf8c780c479ed115a2b0fc2ff41e90e2209c...1fe983948fee4e0e398e76432ced6954eb073161
[cc-pull]: https://codecov.io/gh/ripple/rippled/pull/1722?src=pr


details question about attention map in Figure.3 (a)

Congratulations for publishing your work in ICLR2024! I have seen your figure.3(a) said original DT cannot focus on local information. However, I run your released code with your env, and my attention heatmap in DT is similar to figure.3(b). Can you release more details (code is better) to reproduce the heatmap in you figure 3?

Thank you for your interest in our work.
Regarding the attention map in Figure 3(a), we visualized it during the evaluation phase with a single batch size in the hopper-medium environment. Additionally, we used the default hyperparameters from https://github.com/kzl/decision-transformer (note that the default hyperparameters in our code differ slightly in terms of activation function and learning rate).


Custom View should take all available space + Sample

Set needed constraints when there is a custom view.
Added a crazy sample (not real application)

Hi @dzenbot,
I agree, but currently the developer cannot make it full height, right? And with this change he has the choice.
It was discussed here https://github.com/dzenbot/DZNEmptyDataSet/issues/141


Avoid installing setuptools 45 on Python 2.

Because Requires-Python is disabled for Python 2 to allow this declared-incompatible version to install on Python 2, the build-requirements must exclude installing setuptools 45 during the build-system setup.
Because Python 2 tests are only needed for internal validation, and because the latest pip is already installed, the build-system can rely on backend-path = ["."].
Fixes #1996.

I note this test also illustrates that the backend-path is working as intended and it should be possible to remove setuptools from the build-requires altogether once Setuptools can drop support for sdist installs from older pips.

I don't understand why the tests are failing (example). "no module named posixpath" is the error reported  by 3 failing tests. These tests don't fail on my local macOS runs.

The 3 failures also exist on maint/44.x, indicating a regression in some aspect independent of this effort, so I've filed #1998 to track that separately.


runsd plugin for Dapr?

There is an interesting project, Dapr, that provides some common interfaces for typical microservices work. It's not crazy unique, but it has potential.
Like runsd, dapr uses a sidecar architecture. They have "Pluggable service discovery" but I don't see something that works super well with Cloud Run fully managed right out of the box. I suppose I could make it work with GCP Service Directory.
But then, I thought it should be pretty for you to drop runsd as a plugin. I mean, the basic DNS package they have looks like:
func (k *resolver) ResolveID(req nameresolution.ResolveRequest) (string, error) {
	return fmt.Sprintf("%s-dapr.%s.svc:%d", req.ID, req.Namespace, req.Port), nil
}

I'm throwing this out there because I do not currently have time to dive into Go and figure out how to add this as a plugin there. And while I'm not a huge fan of ORMs, I can appreciate a lot of the abstraction Dapr is offering.

Good idea but probably not in the scope for this repository. This repo is a standalone tool that does the job by reimplementing a lot of stuff from scratch.
You should feel free to run with that idea and contribute it to Dapr. I assume Dapr also can add authentication tokens to outgoing requests. If that is pluggable as well, you can also automatically get a token from the metadata service and augment the Cloud Run-to-Cloud Run request with that as well.
I'm closing since it's not something we'd do in this repo plus I do not know much Dapr myself. Thanks for bringing it up. 👍🏼


Address TODOs in tests

Codecov Report

Merging #873 into dev will decrease coverage by 0.3%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev     #873      +/-   ##
============================================
- Coverage     48.98%   48.67%   -0.31%
+ Complexity     2821     2798      -23
============================================
  Files           116      116
  Lines         27877    27877
  Branches       4650     4650
============================================
- Hits          13655    13570      -85
+ Misses        12104    12102       -2
- Partials       2118     2205      +87

Flag
Coverage Δ
Complexity Δ

#JDBC42
48.13% <ø> (-0.06%)
2747 <ø> (-3)

#JDBC43
48.61% <ø> (-0.31%)
2795 <ø> (-21)

Impacted Files
Coverage Δ
Complexity Δ

...om/microsoft/sqlserver/jdbc/ReaderInputStream.java
40.65% <0%> (-4.4%)
13% <0%> (-2%)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
56.14% <0%> (-2.11%)
0% <0%> (ø)

...rc/main/java/com/microsoft/sqlserver/jdbc/DDC.java
44.2% <0%> (-1.54%)
107% <0%> (-1%)

...m/microsoft/sqlserver/jdbc/SQLServerException.java
77.44% <0%> (-1.51%)
31% <0%> (-2%)

...c/main/java/com/microsoft/sqlserver/jdbc/Util.java
60.99% <0%> (-1.08%)
89% <0%> (-4%)

...n/java/com/microsoft/sqlserver/jdbc/tdsparser.java
68.1% <0%> (-0.87%)
0% <0%> (ø)

...ncurrentlinkedhashmap/ConcurrentLinkedHashMap.java
38.14% <0%> (-0.65%)
42% <0%> (-1%)

.../microsoft/sqlserver/jdbc/SQLServerConnection.java
48.09% <0%> (-0.54%)
335% <0%> (-15%)

...m/microsoft/sqlserver/jdbc/SQLServerStatement.java
59.57% <0%> (-0.29%)
135% <0%> (-6%)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
52.85% <0%> (+0.12%)
264% <0%> (+1%)
:arrow_up:

... and 1 more

Continue to review full report at Codecov.

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


Exception fix

Just a quick exceptions fix.

Coverage decreased (-0.3%) to 91.163% when pulling d6fb4939c99c1af739feba7ad903b9d053b3ab2f on aklein13:master into 84adb218b7348d3518f6eb8ba386d440cb85d193 on limebrains:master.


chore: update permission to root label-conflict

Description
Explain what you have changed, and why.
Checklist:

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

@kenjis I think same as label-signing permission still PullRequests: read
https://github.com/codeigniter4/CodeIgniter4/actions/runs/6220724155/job/16881305240?pr=7952

#7950 better tested


Rewrite default filter docs

I think this way is a little bit clearer.

@davidism, what do you think?

Thanks, but this doesn't seem to improve what's being said, it just moves it around.


Modify Login App to only display relevant tags

Describe the Issue
We need to modify the login app to ensure that the account coding is not displayed to users. However, the account coding tag should still remain visible within AWS itself. We also realized that other tags that are not relevant to the login app users may be displayed and so we want to limit the the tags displayed to useful information.
Additional Context
During a conversation, it was discussed that modifying the login app to hide the account coding would be beneficial. The account coding is classified as low sensitivity and is only used within the government. Revealing the account coding wouldn't have a significant impact. Therefore, we want to implement this change to enhance security and privacy.
Please note that while the account coding should be hidden in the login app, it should still be visible within AWS for administrative purposes.
Acceptance Criteria
To consider the user story as "done," the following requirements must be met:

The login app should be modified to hide the display of the account coding for users.
The account coding tag should remain visible within AWS for administrative purposes.

Extra Template Info
Definition of Ready
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.
Acceptance Criteria
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for

managing expectations
defining scope
reducing ambiguity
establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

Definition of Done
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.

Documented = Captured in Community Update (CU) deck
Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU

https://github.com/BCDevOps/aws-login/pull/20


Protractor unable to locate element though it is present in the DOM in angular 4 app

Hi Everyone,
Iam using protractor in  an angular 4 app.I am trying to find an element by css.Iam unable to locate the element though it is present in the DOM.I had tried to fix this in multiple ways like adding delay and using browser.wait(browser.ExpectedConditions.presenceOf(elem8),10000,"Waiting for textarea") but failed to fix this. i had verified mutiple times that the element is present in DOM during the runtime.Iam attaching the runtime log here.Please help me in fixing this.
element locator: element(by.css('textarea');
webdriver-chrome:v2.40
Message:
Failed: Timed out waiting for asynchronous Angular tasks to finish after 21 seconds. This may be because the current page is not an Angular application. Please see the FAQ for more details: https://github.com/angular/protractor/blob/master/docs/timeouts.md#waiting-for-angular
While waiting for element with locator - Locator: By(css selector, textarea)
Stack:
ScriptTimeoutError: asynchronous script timeout: result was not received in 21 seconds
(Session info: chrome=67.0.3396.99)
(Driver info: chromedriver=2.40.565498 (ea082db3280dd6843ebfb08a625e3eb905c4f5ab),platform=Windows NT 10.0.17134 x86_64)
at Object.checkLegacyResponse (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\error.js:639:15)
at parseHttpResponse (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\http\index.js:538:13)
at client_.send.then.response (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\http\index.js:472:11)
at ManagedPromise.invokeCallback_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:1379:14)
at TaskQueue.execute_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2913:14)
at TaskQueue.executeNext_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2896:21)
at asyncRun (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2820:25)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:639:7
at
at process.tickCallback (internal/process/next_tick.js:188:7)
From: Task: Protractor.waitForAngular() - Locator: By(css selector, textarea)
at Driver.schedule (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\webdriver.js:377:17)
at ProtractorBrowser.executeAsyncScript (C:\Users\awdev1\Desktop\mm-ngx\node_modules\protractor\built\browser.js:235:28)
at runWaitForAngularScript (C:\Users\awdev1\Desktop\mm-ngx\node_modules\protractor\built\browser.js:266:30)
at ProtractorBrowser.waitForAngular (C:\Users\awdev1\Desktop\mm-ngx\node_modules\protractor\built\browser.js:269:16)
at ElementArrayFinder.getWebElements (C:\Users\awdev1\Desktop\mm-ngx\node_modules\protractor\built\element.js:167:29)
at ElementFinder.isPresent (C:\Users\awdev1\Desktop\mm-ngx\node_modules\protractor\built\element.js:1037:46)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\webdriver.js:716:14
at TaskQueue.execute_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2913:14)
at TaskQueue.executeNext_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2896:21)
at asyncRun (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2820:25)
From: Task:
at pollCondition (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2359:16)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2355:9
at new ManagedPromise (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:1082:7)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2354:14
at TaskQueue.execute_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2913:14)
at TaskQueue.executeNext_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2896:21)
at asyncRun (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2775:27)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:639:7
at
From: Task: Waiting for textarea
at ControlFlow.wait (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2352:17)
at Driver.wait (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\webdriver.js:712:29)
at ProtractorBrowser.to.(anonymous function) [as wait] (C:\Users\awdev1\Desktop\mm-ngx\node_modules\protractor\built\browser.js:62:29)
at Object. (C:\Users\awdev1\Desktop\mm-ngx\dist\e2e\specs\specs\app.component.e2e-spec.ts:68:13)
at Generator.next ()
at C:\Users\awdev1\Desktop\mm-ngx\dist\e2e\specs\app.component.e2e-spec.js:7:71
at new Promise ()
at awaiter (C:\Users\awdev1\Desktop\mm-ngx\dist\e2e\specs\app.component.e2e-spec.js:3:12)
at Object.it (C:\Users\awdev1\Desktop\mm-ngx\dist\e2e\specs\specs\app.component.e2e-spec.ts:16:43)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\jasminewd2\index.js:94:23
From: Task: Run it("Should test functionality") in control flow
at Object. (C:\Users\awdev1\Desktop\mm-ngx\node_modules\jasminewd2\index.js:79:14)
at C:\Users\awdev1\Desktop\mm-ngx\node_modules\jasminewd2\index.js:16:5
at ManagedPromise.invokeCallback (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:1379:14)
at TaskQueue.execute (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2913:14)
at TaskQueue.executeNext_ (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2896:21)
at asyncRun (C:\Users\awdev1\Desktop\mm-ngx\node_modules\selenium-webdriver\lib\promise.js:2775:27)
From asynchronous test:
Error
at Suite.describe (C:\Users\awdev1\Desktop\mm-ngx\dist\e2e\specs\specs\app.component.e2e-spec.ts:16:3)
at Object. (C:\Users\awdev1\Desktop\mm-ngx\dist\e2e\specs\specs\app.component.e2e-spec.ts:4:1)
at Module._compile (module.js:635:30)
at Object.Module._extensions..js (module.js:646:10)
at Module.load (module.js:554:32)
at tryModuleLoad (module.js:497:12)

Hi, @chandu379 ! Try to use browser.ignoreSynchronization = true.

First of all thanks for the help @IgorSasovets .Can you detail it more and relate how it can help me and what exactly it does??In the mean while i will try it out!!

Thanks for the help @IgorSasovets. It fixed my issue but raised several other errors, anyhow i fixed them.
I have couple of questions
1)If i have a console.log without appended to promise they get printed before even the actual test starts.Why??
2)Protractor inbuilt method like is presenceof all of these are not waiting till the delay given but throwing error immediately as "StaleElementReferenceError: stale element reference: element is not attached to the page document".Why?
3)Other protractor methods such as visibilityof or stalenessof are immedialtely throwing error without even waiting for the given delay argument.What may be the cause??

I need to review code because it can be caused by few reasons main of which is log location in test.
As I said, some elements are always in pending state and it causes such errors.
I recommend you to use elementToBeClickable instead or in combination with visibilityOf. I also had similar issues and even implemented custom synchronization for some parts of application.

Also, please close this issue if it's fixed.


Change visible duration of graph

Closes #6
Supports the following durations: 10m, 30m, 1h, and 24h (based on https://www.purpleair.com/map)
The 24h duration is slow to load (lots of data), so we might want to sample one data point every minute (instead of every second, or whatever the current interval is)

This looks excellent to me!


Applescript third pane

Fixes the stuff in #2071
Thanks @Sesquipedalian for reporting this and and also Mike Petonic for alerting me to this on the dev forums. Quite a big usability problem.
There is now an addition of a '3rd pane not-optional' choice for 3-pane actions.
That is, if you set the 'get argument count' part to return -3 then the 3rd pane is optional. If it returns 3 then the 3rd pane is not optional (and will display by default).
I used -3 and 3 as I thought it was kind of intuitive -3 meaning optional, 3 meaning not optional.
Open to other suggestions though

@skurfer any idea why the testEquality test is failing?

There is now an addition of a '3rd pane not-optional' choice for 3-pane actions.

I don’t know this code at all, but there’s a comment that says “1 = dObj only. 2 = dObj + iObj. 3 = indirect Optional”. So didn’t 2 already mean that the third pane was required?
Personally, I think I’d make 1 and 2 the only valid values, and have a separate thing you could put in the AppleScript that returns a BOOL to indicate whether or not the third pane is required. But maybe we should get opinions from people writing AppleScript actions. 😃

any idea why the testEquality test is failing?

Probably the same reason it always has. combined1 are combined2 are literally the same object when you run the test the first time (and that really shouldn’t be possible). If you run the test again, it will work correctly, but of course Travis only does it once.
This might be moot soon. If XCTAssertEqualObjects and XCTAssertNotEqualObjects are checking hash before they check isEqual:, the test will need to be adjusted.

I suspect that this isn't really going to help. The problem in #2071 is not a matter of controlling whether the third pane is optional or required (as @skurfer already noted, setting get argument count to either 2 or 3 already does that anyway). The problem is that the third pane is being populated with random junk for AppleScript actions. To fix #2071, the third pane should cleared whenever the user selects an AppleScript action in the second pane.

The problem is that the third pane is being populated with random junk for AppleScript actions.

That's what this PR mainly fixed, I added the indirect option code (which Rob's pointed out isn't needed) as an addition. I'll just remove that 2nd commit then we'll be good... (done. Force pushed)

Oh, okay. I guess I misunderstood your initial post. :)

I'll just remove that 2nd commit then we'll be good...

Yeah, just looking at the code @Sesquipedalian, I think the stuff that ends up in the third pane should be greatly improved.

(what I was trying to fix in that un-needed commit was a bug where the 3rd plane closes when you enter text mode, but I've found this is universal, not just with AppleScripts).
What this does for your first script (indirect optional, when you tab to the 3rd pane) is to cause the pane to open, go into text mode, close, then reopen again

Already said thanks on the dev forum, but THANKS again.  I'll check it out on the next release of QS.

You're welcome. Thanks to you for bringing the issue to our attention :)


Update fullcalendar

Hey @vsoch! I got it working. The problem was, that minimal-mistakes defines
table {
    display: block;
}

which apparently breaks the daygrid view. Therefore I am overriding this for the fc-daygrid class and it works now (see https://433-267395254-gh.circle-artifacts.com/0/SORSE/programme/calendar/index.html)

Looks great!


Bump version

GAME_VERSION = '2.8.0' GAME_VERSION_DATE = '2016-06-08_00' # in JST

Before bumping the version, need to implement Sheldon's Picks Vol. 2.

396880455084d52c76ee688318d1f1b1aba0722b


Docs loose ends

[x] Remove the cloning of repo and Python environment from installation page. Reference the Local infra setup page instead.

[X]  Many of the bullet lists in our docs aren't rendering in Sphinx properly because Sphinx expects spaces before and after the bullet list (Github and Jupyter render correctly without the spaces). This PR adds spaces to our bullet lists in notebooks so they render properly in sphinx docs.

[X] The experimental tutorials shouldn't be prefixed with "experimental". Shorten those filenames.

@IceKhan13 , there was some Sphinx weirdness with bullet lists to take care of. I also tidied up the installation page, which was another part of that PR that didn't make it in for some reason. This should actually be my last major input to the docs before next release :)


fix apt-cyg URL

The old URL responds with a 301 Moved Permanently, failing the installation instructions.
This pull request fixes the URL to the new location.

wow that's great! I failed in download the apt-cyg and you helped me!


Enhancement - Support for Open ID

Describe the bug
Support for Open ID needed
To Reproduce
Create TM1 model with Open ID security mode and TM1Py cannot connect

Hi,
Is there any update on this issue? Trying to connect to Azure AD (open ID connect) and facing the same issue. Please let me know if any updates.
Thanks

To be honest, it's no the highest item on our list currently. If you are using OpenID with CAM it should work though.

I recommend that we push IBM to actually document the feature.
I have had a few discussions with IBM about it, they said since paw and Pax do not support it they don't offer public documentation.
Ryan Clapp
Sr. Manager
AWS FinTech
Sent from my mobile device
On Jul 12, 2020 1:13 PM, Marius Wirtz<EMAIL_ADDRESS>wrote:
To be honest, it's no the highest item on our list currently. If you are using OpenID with CAM it should work though.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/cubewise-code/tm1py/issues/184#issuecomment-657269538, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEK7GZVMTXNQ264JKFOPFKDR3IKOPANCNFSM4JCZY73Q.

We had a workaround on CAM side by setting up another authentication provider, can be Active Directory, OpenDJ, ApacheDS, etc.....
On Cognos Configuration side, make this new namespace Hidden or Invisible, while all other users are using OpenID or AzureAD to connect, end users do not have visibility to this hidden namespace at all.

Any plans to implement that in tm1py in the near future without the need for CAM?


Normalize the LLVM cmake path before appending it to the module path

LLVM_CMAKE_PATH has backlashes in it. CMake then tries to append this to CMAKE_MODULE_PATH but gets confused and errors out as it thinks we're providing an escape sequence (that's unknown, causing generation to fail)
E.g "C:\Users\hugh..."

@jimingham PTAL, should this go to upstream LLDB?

and @llvm-beanz 'cause you're the CMake guy, at least looking at commits

This change looks fine, but should definitely go to LLVM.org. The CMake logic being changed here is identical upstream.

By default, all commits that are in non-swift code should go into llvm.org and get merged back to the swift lldb.  That way they everybody gets the benefit of the changes, and they won't cause later merge conflicts if they get fixed differently upstream.

@swift-ci please test

I've updated the PR to cherry-pick my commit from upstream lldb

LGTM!


Auto publish artifacts via build server

This includes making a working script to build the mod.

Done in 19b4288.


v6 create index goroutine problem

when the number of request growing, goroutine number keeps growing.
b, _ := json.Marshal(order)

resp, err := o.es.Index(
	order.GetCertainIndex(),
	bytes.NewReader(b),
	o.es.Index.WithDocumentID(order.ID),
	o.es.Index.WithDocumentType(order.GetType()),
	o.es.Index.WithRefresh("true"))

Hey, I'm afraid I need more information and context to understand the problem you're having...

I think the problem is caused by
req, _ := newRequest(method, path.String(), nil)

func newRequest(method, path string, body io.Reader) (*http.Request, error) {
	r := http.Request{
		Method:     method,
		URL:        &url.URL{Path: path},
		Proto:      "HTTP/1.1",
		ProtoMajor: 1,
		ProtoMinor: 1,
		Header:     make(http.Header),
	}

	if body != nil {
		switch b := body.(type) {
		case *bytes.Buffer:
			r.Body = ioutil.NopCloser(body)
			r.ContentLength = int64(b.Len())
		case *bytes.Reader:
			r.Body = ioutil.NopCloser(body)
			r.ContentLength = int64(b.Len())
		case *strings.Reader:
			r.Body = ioutil.NopCloser(body)
			r.ContentLength = int64(b.Len())
		default:
			r.Body = ioutil.NopCloser(body)
		}
	}

	return &r, nil
}

when the request comes, Do func new a new http client. it cause the goroutine number growing when there are many request.

I use pprof to analyze the program, and I found that the http/transport is the main problem.
goroutine 706 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc001f6cfc0)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 1054 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc001d94900)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 778 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc00238ea20)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 1138 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc001b506c0)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 745 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc001f6d7a0)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 746 [select, 3 minutes]:
net/http.(*persistConn).writeLoop(0xc001f6d7a0)
	/usr/local/go/src/net/http/transport.go:1885 +0x113
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1339 +0x966

goroutine 733 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc0022f6360)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 719 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc001fb3e60)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 838 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc00233b8c0)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

goroutine 705 [select, 3 minutes]:
net/http.(*persistConn).readLoop(0xc0023687e0)
	/usr/local/go/src/net/http/transport.go:1761 +0x6b9
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:1338 +0x941

Thanks for the additional info. Can you post the code you're using with the client? There are subtleties when it comes to HTTP in Go, like closing the response body, draining it to make it use persistent connections, etc.

var err error
	once.Do(func() {
		Es, err = elasticsearch.NewClient(elasticsearch.Config{
			Addresses: config.Setting.ES.URLs,
			Transport: apmelasticsearch.WrapRoundTripper(&http.Transport{
				MaxIdleConns:        config.Setting.ES.MaxIdleConns,//10
				MaxIdleConnsPerHost: config.Setting.ES.MaxIdleConnsPerHost,//2
			}),
		})

		if err != nil {
			logrus.Panic("elastic.NewClient error: ", err)
		}
	})

... but this is just the client initializer, not executing any requests?

b, _ := json.Marshal(order)

resp, err := Es.Index(
	order.GetCertainIndex(),
	bytes.NewReader(b),
	Es.Index.WithDocumentID(order.ID),
	Es.Index.WithDocumentType(order.GetType()),
	Es.Index.WithRefresh("true"))

this one.

Right, then it figures — you're not closing the resp.Body, which triggers the errors you've posted in the backtrace.
So add something like:
if resp.Body != nil {
  resp.Body.Close()
}

before the last line, return nil.

Thank you. Add the resp.Body.Close() and problem solved.
That's strange.
In some case, we don't need to deal with the resp.

Glad to hear that!
And yes, the body needs to be closed even when you don't use it. It's specific to Go itself, not the client, but it's maybe a good thing to add to the documentation.


Make symfony bundle optional

I moved all the symfony bundle specific files into a new namespace Bundle. Also I removed the requirement for symfony/framework and instead added the necessary symfony components as dev-dependencies and suggestions.
See this conversation: https://twitter.com/jkrzefski/status/1402881774535970817

Hey, this is great :)
What about having the following namespace structure instead:

Sourceability\Instrumentation\

Sourceability\Instrumentation\Profiler\
Sourceability\Instrumentation\EventListener\
Sourceability\Instrumentation\Bundle\

Sourceability\Instrumentation\Bundle\DependencyInjection

Also renaming:

the composer package to sourceability/instrumentation
the repository to sourceability/instrumentation

Hey, this is great :)
What about having the following namespace structure instead:

Sourceability\Instrumentation\

Sourceability\Instrumentation\Profiler\

Sourceability\Instrumentation\EventListener\

Sourceability\Instrumentation\Bundle\

Sourceability\Instrumentation\Bundle\DependencyInjection

Also renaming:

the composer package to sourceability/instrumentation
the repository to sourceability/instrumentation

I like this a lot. I just updated the PR to include these changes. But of course I cannot change the repository name nor can I change the name on packagist. I leave that to you. Don't forget the entries homepage, support.issues and support.source in the composer.json file.

Thank you! I'm going to take care of the composer/packagist/repo last steps

https://packagist.org/packages/sourceability/instrumentation-bundle has been marked as abandoned
https://packagist.org/packages/sourceability/instrumentation has been created
0.2.0 has been tagged
the repository url has been updated to https://github.com/sourceability/instrumentation

Thank you again!

Wow, that was fast 🚀
Thank you so much for your awesome work.


Netlify Rewrites does not work in Netlify App but works when using netlify dev

Describe the bug
I have a simple Next.js App with a  [slug].js and I have no index.js file. Instead I have added an option to rewrite / to /home using rewrites. It worked perfectly on netlify dev but when I updated in netlify app, It doesn't work.
This is what I written on _redirects
/  /home  200!

The rewrites works as expected in dev cli, but in netlify app, its not working.  This has also been discussed on https://answers.netlify.com/t/next-js-rewrites-not-working/40017/ before adding it as an issue here.
To Reproduce
Steps to reproduce the behavior:

create next.js app
delete pages/index.js and add [slug].js which can handle /home
Run netlify dev and see / redirects to /home as expected
Now Push the project to Netlify
See the / no more rewriting.

Configuration
Issue is in Netlify Production server.
Expected behavior
/ should redirect to /home dynamic path same as netlify dev for Netlify Server as well. If the feature is not supported, then netlify dev should throw error.
netlify dev CLI Output

Hi @surjithctly, thanks for reporting this issue.
Can you share a public repo as a reproduction?
If not can you answer the following questions:

Are you using the Next.js plugin? If so, which version?
What are your build command, publish directory and functions directory as configured in Netlify?
Can you share your netlify.toml file if exists?
Can you add the output of the following command npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli?

Thanks!

Hello,

Yes, Next plugin is added automatically, so It should be latest 3.5.0
Build command is also default. No changes made. All set by netlify
file does not exists but I have _redirects with above code
Not sure how to run this command on netlify dashboard, And I think I don't need to run it in my system since there is no issue here. The issue is on the Netlify Server. Local machine works fine.
/pages contains [slug].js which has getstaticprops & getstaticpaths with fallback true.

Let me know if you need anything else.

Marking this as stale as it is is several years old. Please feel free to reopen if you are still having issues.


🐞 - "addon-doc" incompatible with Angular v13

Which @taiga-ui/* package(s) are the source of the bug?
addon-doc
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/edit/taiga-starter
Description
Trying to update Angular to v13 with ng update @angular/core@13 @angular/cli@13 throws following error when using @taiga-ui/addon-doc:
Package "@taiga-ui/addon-doc" has an incompatible peer dependency to "@angular-devkit/schematics" (requires "^9.0.0", would install "13.2.0").

While you are at it, it would be nice if all other addon-doc peer dependencies would be updated to the latest version as well and their version range would be extended to at least include minor releases (^1.0.0).
Angular version
13.2.0
Taiga UI version
2.31.0
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

There is also another issue with addon-doc.
After updating to the latest version, I get the following error during compilation:
@angular/compiler-cli/bundles/chunk-5CHRTEXL.js:941
      throw new Error(`The target entry-point "${invalidTarget.entryPoint.name}" has missing dependencies:
            ^

Error: The target entry-point "@taiga-ui/addon-doc" has missing dependencies:
 - markdown-it

Oh, sorry about that, needs to be added to dependencies markdown-it, i will add this! And as long as you can manually install it yourself

We need to probably move some peerDeps to deps anyway:
https://github.com/Tinkoff/taiga-ui/issues/667


problem with undefined: unsafe.Slice in oref0-setup.sh script

Describe the bug
During instalation (or reconfiguration) of OpenAPS (thru oref0-setup.sh script) I was facing issue with  "undefined: unsafe.Slice" it happen right after  "golang.org/x/sys/unix" processing.
Few lines after "undefined: unsafe.Slice" scripts ends throwing out below text: "Couldn't go get medtronic"
Unfortunately I do not have exact screen because I manage with this problem
To Reproduce
run master version of oref0-setup.sh script
Expected behavior
Normally script should process and install OpenAPS
Screenshots
Unfortunately I do not have screens
Smartphone (please complete the following information):
This is not related to smartphone
Setup Information (please complete the following information):

Pump type ( Medtronic 722, v. 2.4A firmware
CGM type (Dexcom G6 via xDrip+)
Rig type ( This problem appear on Edison/Explorer Board  and on Raspberry Pi with ADAFruit
oref0 version (0.7.1 [master])

Additional context
In my case I was able to solve this problem by upgrading "go" version to from 1.12.5 to 1.17 (in line 1194 in oref0-setup.sh)

I assume you were using master? I think we fixed this in dev. If you can confirm, we should probably try to get dev ready for another release.

Hi Scott,
Yes, that's true. I built it for my 11 years old son, so I always prefer to
use the master (stable) version.
Thanks and regards,
pon., 12 gru 2022 o 02:30 Scott Leibrand @.***>
napisał(a):

I assume you were using master? I think we fixed this in dev. If you can
confirm, we should probably try to get dev ready for another release.
—
Reply to this email directly, view it on GitHub
https://github.com/openaps/oref0/issues/1440#issuecomment-1345743286,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4WCMC3QLRSOWZUSNICHLSDWMZ54BANCNFSM6AAAAAAS3EYINI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I had this issue yesterday trying to do the upgrade from 0.7.0 to 0.7.1 on the master branch. Switching to the dev branch fixed it for me. I initially had some issue with some missing go packages, but after running rm -rf /usr/local/go/* and trying again, it worked just fine.
Here's my setup info:

Pump: Medtronic 722, firmware 2.4A
CGM: Dexcom G6 via xDrip+ on Android, plus Logger on the rig
Rig: Edison + Explorer board

For the record, this missing packages issue could easily be a one-off thing with my setup; my rig kept dying in the middle of the setup process, both on the master and dev branches. I think it was either due to watchdog and some other things I have running on my rig, or some intermittent issues with my network or internet connections that affected SSH. After I connected directly to the UART port, and stopped the cron and watchdog services, the setup finished without issues.

Hi @inventor96  I ran into this same issue, used the DEV as suggested above and worked. Im running the same set up as you mentioned above except "logger on the rig"
Are you sending your data collected in xdrip to Nightscout via Railway instead of Herokuapp? and are you looping with OpenAPS?

Are you sending your data collected in xdrip to Nightscout via Railway instead of Herokuapp?
I use Nightscout hosted on Google Cloud Platform. Both xDrip+ and my rig are configured to sync with Nightscout.

are you looping with OpenAPS?
Yep. As far as I know, the only project that uses this oref0 is OpenAPS.

@inventor96 I believe FreeAPSX also uses oref0 directly, and AndroidAPS uses a port of it.

@inventor96 I believe FreeAPSX also uses oref0 directly

Yes