.env keys and values with $ are not parsed

Expected Behaviour
A line with an escaped $ character should be read into the environment.
Actual Behaviour
A line with an escaped $ character is not read into the environment.
Reproduce Scenario (including but not limited to)
Put this into an .env file:
AIO_\$ims=foo

Observe that process.env.AIO_$ims is undefined.

We are using dotenv to parse the .env file. The regular expression needs to be updated to:
const RE_INI_KEY_VAL = /^\s*([\w.-\\$]+)\s*=\s*(.*)?\s*$/
The line affected: https://github.com/motdotla/dotenv/blob/e8744104cd3c8b87d258dc153f72b5216ecb4fac/lib/main.js#L32

Closed with #28. This is a temporary patch until we can patch dotenv itself.

Environment variable names don't support special chars like $, see https://stackoverflow.com/questions/2821043/allowed-characters-in-linux-environment-variable-names, that's why dotenv is not supporting these.
In Bash:
> export TEST\$VAR=hallo
bash: export: `TEST$VAR=hallo': not a valid identifier

> export TEST\\$VAR=hallo
bash: export: `TEST\=hallo': not a valid identifier

Is there a need for this?
I am asking because this little change makes this library extremely big as it pulls in patch-package which makes up 6.2 MB out of 6.6 MB total cost of @adobe/aio-lib-core-config and pulls in over 200 extra libraries of all kinds, which should not be needed at all for a config reading library.

This is currently needed for the ims config (.env variables needed to have credentials from the downloaded Dev Console project mapped to aio config) which unfortunately uses a $ prefix ($ims). See the example config: https://github.com/adobe/aio-lib-ims
I've already discussed this with Jesse regarding changing this, and we want to change this but didn't have time without impacting everything. This will be a breaking change, but since we are at Developer Preview this change wouldn't be a big impact if we change now.

Yeah. This needs some priority. I didn’t realize the size of the change to config-lib ...
This impacts every core plugin.

I didn’t realize the size of the change to config-lib ...

Well, one could state that using such a huge library and dependencies for such little effect is overkill ;-)
But I get the point. Let's consider why $ has been used as a prefix in the first place, and fix that problem going forward.
$ was chosen as a prefix to internal names such as $ims, $current, and $plugins. As a side-effect this knowledge is also leveraged to filter the $current and $plugins properties out of the context listing.
On option would be to restructure the config as follows:
{
  "ims": {
    "config": {
      "plugins": [ "p1", "p2" ],
      "current": "sample"
    },
    "contexts": {
      "sample": {},
      "another": {}
    }
  }
}

This is just a thought, apart from migration concerns which must be taken care of, I am not really hung up to this.

@shazron @purplecabbage are you fine with @fmeschbe 's proposal or do you have other suggestions?
If so I'm also in for solving this with a high priority. We should also have a clear documented migration approach for the users that would be impacted.

+1 on Felix's proposal

Yeah, apart from the size issue (which is just due to the way the patching of dotenv is done, and could probably be done more lightweight) it‘s probably not ideal to use a character in environment variables that is usually not supported (even if this is only somewhat indirectly IIUC). It would probably create issues in other tools/libraries than dotenv as well.
If that is addressed, and the standard dotenv library can be used again, the size issue is automatically resolved as well from what I can see.

Changes will be part of https://github.com/adobe/aio-cli/issues/191


Add 4.1; First Azure test

In ref #169 adding in Azure Diagnostic Settings validation for log forwarding CISA control 4.1.

Thanks for the call out here @merill. I reworked the function and tested in Pwsh and Windows PowerShell. Hoping it is more consistent now.
I added some additional content to the docs too. I wasn't positive how MDX would handle nested code blocks so I added it just as fenced text instead.


Mass hiding TUYA devices

Device Infomation JSON File
It's possible to add this feature?
For example, i need to hide all tuya devices in HK instead of TH sensors, now i have to do 70+ "deviceOverrides" sections ;)
Maybe it would be easier to add one long list?
Thanks!

Detail Informations
subj

It's possible to add this feature?
For example, i need to hide all tuya devices in HK instead of TH sensors, now i have to do 70+ "deviceOverrides" sections ;)
Maybe it would be easier to add one long list?
Thanks!

you can use product id as id if they are the same product, can it solve you problem?

It can't be like this. {} is a key-value pair, the key is unique. have you tried using product id? I think that's enough to do so.


Expose to all network in docker system and configure IB system close …

…down time

You pretend fix this PR, or should we close it for now?

closing due inactivity.


Switch from ClickOnce to Squirrel for installer

(originally created by @dsplaisted)
Squirrel

@dsplaisted van you tell something about Squirrel?

https://github.com/Squirrel/Squirrel.Windows

I'm not super familiar with either Squirrel or ClickOnce.  I know that Squirrel is supposed to be like ClickOnce but better.
Squirrel installs apps to your user folder so you don't need elevation to install them.  It can automatically keep them up to date.  (As far as I know ClickOnce also does these things).
One cool thing about Squirrel is that it handles updates by creating packages that are binary diffs between different versions.  So when upgrading from one version to the another, only what's changed needs to be downloaded instead of the whole app.

Squirrel installs apps to your user folder so you don't need elevation to install them. It can automatically keep them up to date. (As far as I know ClickOnce also does these things).

Yes, that's indeed possible with ClickOnce
I'm curious if we can host the Squirrel version in Github (pages). I tried with ClickOnce, but failed (the install step always failed, dunno why)

One extra benefit is that is that it can easily be pushed to any blob storage...probably with less hassle than ClickOnce.

could you show me the details where you failed to host the ClickOnce deployment?

@Licshee do you mean failing to publish on github or what is described in #27?

@304NotModified on github.io

Clickonce won't install from Github, because Github won't send the correct headers. You get a fatal error when installing.

related to Content-Type?

Have to check that. Could be possible.

The required clickonce headers:

https://msdn.microsoft.com/en-us/library/ms228998.aspx#Anchor_5

Hi, the help about mime types for github pages : https://help.github.com/articles/mime-types-on-github-pages/
Mime types supported : .application, .deploy (from apache definition)
Missing defined mime types for .manifest, .msu, .msp
I don't know what is the github pages behavior for undefined mime types.

Thanks, but it think there is no problem to keep it on CodePlex for now.

label "install error", as this could fix the install error

Helper tool
https://github.com/flagbug/ClickOnceToSquirrelMigrator

Nevermind squirrel, how about using a Centennial app in the Windows Store for those of us on Win10? :)

Sounds great!
Any idea if this will support everything we use now? (e.g. file extension registration etc)

It should support anything a user process can do.
What I'll do is the following:

Create the packaging project or whatever is needed to support this.
Create a store submission
Figure out how to do a CI build to package and publish to the store (if possible)

I'll submit the changes as a PR initially. Depending if we can get CI/CD going, I may just need a head's up on when it's time to create a new release to the store. How's that sound?

Sounds very good! Thanks in advance! !

@304NotModified happy to help. can you pls drop me an email - I don't think I have yours. Mine is first at last dot org.

The app is now in the Windows store for Windows 10 Anniversary Update and later users: https://www.microsoft.com/store/apps/9wzdncrdmdm3
I recommend switching to that version as it does not have any installer issues and auto-updates.


Error installing elementary OS

Hello, I'm having a error installing elementary OS on top of Ubuntu running the XFCE desktop environment, I've did everything a tutorial explained, although when I'm starting the script I come up with the following error:
/etc/X11/Xsession.d/99x11-common_start: line 5: exec: init: not found
Running exit commands...
/usr/bin/xinit: connection to X server lost
If anybody could fix this error within the hour, I'd gladly be able to reward them.

Use the MyDearWatson script.

See #1571


Preventing Selecting "Disabled" items?

downshift version: 1.21.1
node version: 6.9.1
npm (or yarn) version: yarn 1.20

Relevant code or config
  handleSelection = (selectedItem, stateAndHelpers) => {
    if (!selectedItem) { return; }

    if (selectedItem.disabled) {
      stateAndHelpers.clearSelection();
      return;
    }

    if (this.props.clearOnSelect) { stateAndHelpers.clearSelection(); }
    stateAndHelpers.closeMenu();
    this.props.onSelect(selectedItem);
  }

...
  render() {
    return (
      <Downshift
        defaultHighlightedIndex={0}
        onSelect={this.handleSelection}
        itemToString={item => (item ? item.name : '')}
        render={this.renderAutocomplete}
      />
    );
  }

What you did:
I have a list of items, users in this case, some of which are disabled. I'm trying to prevent downshift from allowing them to be selected.
What happened:
So far, this works OK, except it also clears the input value -- which is what clearSelection was designed to do.

Reproduction repository:
I'll try to extract some code later, but I think this makes sense. This is a feature request /question and not a bug. :)

Problem description:
I'd like to be able to support disabled items. I think I might be able to get around this by managing the selectedItem state myself, but that seems like more than I'd like to do if possible.
Suggested solution:
It would be nice if a disabled attribute on an item in a menu prevented any selection from happening. Optionally, arrow keys could skip over them.

Hi @cycomachead!
I wonder if you could simply not apply the getItemProps to the menu items you wish to have be disabled? For example :smile:
Though your suggestion does seem interesting, I prefer to keep downshift lean and primitive to avoid baking in too many opinions/functionality that others don't need. So I'll go ahead and close this, but feel free to convince me otherwise (a PR with tests is a good way to do that, though I can't promise it'll be merged).
Good luck!

Hi Kent,
Thanks so much for the quick response! I hadn't yet considered not sending item props. That's brilliantly simple! :)

That's brilliantly simple! :)

😊

That actually makes sense as a default. I'd be interested to see a pull request that implements this if you'd be willing to open one up.

Actually, thinking about it I just realized that this is not necessary. Just don't call getItemProps for an item which you render which is disabled. Like in this example: https://codesandbox.io/s/v666z3o6ml

uh indeed it works already, my highlighting logic for getIsActive was wrong :) I thought highlightedIndex === index would be enough. Thanks Kent!


Cirrus: Switch CI testing to VMs

Prior to this commit, CI ran entirely in a container environment.  This
was very much less than ideal, since actual network/firewall
manipulations could not be exercised.  With this commit, everything will
execute on the same VM images and image-build workflow used by all the
other containers-org project automations.
Note: Given all other projects generally use golang, the VM images here
are NOT tailored to a rust project.  Unfortunately that means
performing runtime updates/installs and using cache to reduce the dnf
repo. Metadata/package downloading.  These aspects can be removed once
dedicated netavark VM images are realized and implemented in a future
commit.

(Failure is expected for now)

Okay, I think this is ready for review at least.  There's certainly room for more optimization but this should be good enough at least for the near-term.

I cannot really review this but I would like to get this merged, @baude @mheon @edsantiago PTAL

WIP Add netavark integration tests #94

Oh you've got some tests ready to go.  Let me rebased that PR into here, so we can see them run in this environment...

I cannot really review this but I would like to get this merged, @baude @mheon @edsantiago PTAL

Heads up, I've got a rebase/force-push incoming along with some mostly cosmetic changes (better commit message, new comments, and renaming 'test' -> 'unit' task).

@cevich It looks like dbus-daemon need to be installed in the VM. The other test errors are expected

@cevich It looks like dbus-daemon needs to be installed in the VM. The other test errors are expected

Thanks, that helps.  Trying again...

Note: I'm not so happy with the 10minute build-task runtime, I was hoping caching $CARGO_HOME would help more than it appears to be.  It's certainly an improvement vs completely cold-cache, but still longer than I'd like.

(Rebased/force pushed w/ #94 + moved display of toolchain/env. var details into runner.sh for better visibility)

Seems we're missing all the firewalld stuff as well, and there's a Makefile bug that needs fixing...

@cevich Is this a fedora 35 VM? I thought firewalld is shipped by default.

Is this a fedora 35 VM? I thought firewalld is shipped by default.

It is, the cloud images are different.  It's typical to not run a local firewall and pass this responsibility off to the cloud-provider.  Speaking of which, there's going to be a bit of a likely chicken-vs-egg conflict with the PR/CI workflow here:

Cirrus-CI depends on local networking (and firewall) allowing outbound traffic to stream output from CI and execute things.
If the tests break either networking or the local firewall, this fact will not be observable.
Cirrus-CI will automatically re-try (once) any task where communication to the VM was lost.
The only signal you'll get this is happening is in the Cirrus-CI WebUI, it will say (in red): CI Agent Not Responding.

In the case of a non-GCP privileged user's PR, they will need to be assisted with debugging, possibly with manually adding their ssh key to a VM from hack/get_ci_vm.sh - in other words, it could be an ugly, frustrating situation to deal with :confused:

@cevich These test do not touch the host network at all. Each test run in their own network namespace to prevent any leaking iptables or network interfaces.

These test do not touch the host network at all.

Good thinking.  Still, kernel bugs or test-goofs happen.  The frustrating thing is you'll get zero clue this has occured: Cirrus-CI output will just "stop", the VM will go down (destroying the logs), and the task will restart (once).  I know from past-experience this is a very (VERY) frustrating situation to deal with.  So after this merges, please make sure you can successfully use hack/get_ci_vm.sh, assuming the problem is reproducible, that will be your only hope.

Okay, last update I'm going to make for now: I commented out execution of the integration tests, but left all the bits in there.  I think this PR is ready for review and merge - Unless there are horrible problems with my bash (mostly copy/pasted from other projects).

/lgtm

/approve


Remove dynamic detection of pipelining support

Pipelining has made its way to stable so no need to check that any
more.

r? @nrc
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 0afe1b116ef8799470209eee341efea606d85b69 has been approved by ehuss

:hourglass: Testing commit 0afe1b116ef8799470209eee341efea606d85b69 with merge 494cbd8c8d066572fcee6e41ffa3aca8ee316104...

:sunny: Test successful - checks-azure
Approved by: ehuss
Pushing 494cbd8c8d066572fcee6e41ffa3aca8ee316104 to master...


Use OMAS instead of IDSMapping

I just checked out OMAS, and it seems like it solve a couple of things we are also trying to solve, like mapping the IDS tree. It's available from pypi and does not immediately depend on IMAS either.
e.g.
from omas import load_omas_imas

ods = load_omas_imas(user='g2aho', machine='jet', pulse=92432, run=1, consistency_check=False)

# IDSMapping.fields
ods['core_profiles']['profiles_1d'][0]['zeff']

# IDSMapping.flat_fields
ods.flat()['core_profiles.profiles_1d.0.zeff']

github
examples
slides

Apparently this code loads the data correctly with verbose=True...
>>> from omas import load_omas_imas

>>> ods1 = load_omas_imas(
>>>     machine='jet',
>>>     run=8000,
>>>     pulse=94875,
>>>     user='g2ssmee',
>>>     consistency_check=False,
>>>     verbose=True,
>>> )
Opening existing IMAS data for user='g2ssmee' machine='jet' pulse=94875 run=8000
dataset_description.imas_version is missing: assuming IMAS version 3.34.0
got IDS
- amns_data                  IDS is empty
- barometry                  IDS is empty
...
- waves                      IDS is empty
- workflow                   IDS is empty
summary.volume_average.zeff.value: 100%|█| 73287/73287 [01:28<00:00, 831.81it/s]

>>> print(ods1.keys())
['core_profiles', 'core_sources', 'core_transport', 'dataset_description', 'equilibrium', 'summary']

>>> ods2 = load_omas_imas(

>>>     machine='jet',
>>>     run=8000,
>>>     pulse=94875,
>>>     user='g2ssmee',
>>>     consistency_check=False,
>>>     verbose=False,
>>> )

>>> print(ods2.keys())
['dataset_description']

#201

The way to use it seems to be to only grab the required data (in which case it is not so slow).
ods = omas.load_omas_imas(
   pulse=94875, run=250, user='g2ssmee', machine='jet',
   paths=['core_profiles.profiles_1d.0.t_i_average']
)

Going to close this for now, since OMAS does not offer anything we need at the moment.


Use '@container': '@language' in the @context to define the structure of the generated classes

Issue type:

:heavy_plus_sign: Feature request

Description:
We're using the @oslo-flanders/ea-converter package to generate an RDF-file which works well. However, we have some questions in regards to the flexibility of the generated output.
A lot of the key/values have the same structure. For example, if we look at apLabel, this is the structure:
"apLabel": [
    {
        "@language": "nl",
        "@value": "Oplegger"
    }
]

The output itself is correct, however it deviates a bit from the existing output that got generated from the previous toolchain version. The old output was this:
"ap-label-nl": {
    "nl": "Oplegger"
},

The fact that the name from the key changed from ap-label-nl to apLabel is no problem, however we are looking to replicate the behaviour from the old toolchain where the nested key of the label-object is the language for which the label got generated with the value of the label. In order to achieve this, we tried to change the predefined @context that is passed to the generated RDF from here to something like this:

    apLabel: {
      '@id': 'oslo:apLabel',
      '@container': '@language',
    }

We replaced the previous @container value from @set to @language but that does not seem to have any impact on the generated output.
I looked a bit deeper into the code and found out that the generated output seems to be constructed manually using this method. This lead me to believe that the passed @context file doesn't have any impact on the generated output (at least for this specific use-case).
My question is:
Is there a way that we can make the generated output @context-dependant to generate the apLabel in the same format as the previous ap-label-nl or is that not possible without reworking the mapToLiteral method as mentioned earlier? We hoped that it would be possible to change the generated output using the @context but that might be a wrong expectation from our side.
Thanks in advance for any insights!

@ddvlanck I would love to have your insights on this issue. Feel free to answer whenever you deem it possible. Thanks for any help!

Hi Kristof,
First some background information. There is a reason why we did not use a JSON-LD serializer package as there are multiple packages available on NPM and it is simple: debugging purposes. We construct our own OSLO-specific JSON-LD output, with keys as classes, properties, ... so that developers, but also editors can easily verify the output and spot mistakes if there are any. This OSLO-specific format can not be created when you use one of the available packages.
By using of our own OSLO-specific JSON-LD format, we have to create our own JSON-LD context, but also our own objects. You're correct that only changing the @container value from @set to @language in the context will not provide the correct output. So if you want to accomplish the same behavior as in the previous toolchain, you will have to update the JSON-LD context as shown in your example, but also update the mapLiteral function.

@ddvlanck Thanks for the answer! That was indeed what I expected the outcome to be based on the code. Just wanted to see if there was something that I might have overlooked? Thank you for taking the time to answer this one! Will close this as it's resolved in a way 👍


Fix restorePlayingTweens

After loading a website using MoJS within an inactive tab, an error is thrown.
"Cannot read property 'length' of undefined"
The error is due to the _savedTweens prop not being set unless savePlayingTweens has been called. This patch ensures that _savedTweens is always an array, preventing the error.
This bugs has been known of for a while, and has been fixed in dev branches, but for some reason this has not been patched on the master version, despite this being a massive issue for any production website, with an incredibly simple fix.

We are experiencing this very same problem with _savedTweens not being set. We'd really appreciate if this fix could be merged to master. Any updates on when a new release is scheduled?

@talb-senexx sorry about that, trying to kickstart new release soon, it is fixed in mojs2 already, but the v2 wasn't released yet also.

@legomushroom I understand that this is fixed in the next version, but right now we don't even have an ETA on that. I'm stoked to hear that there should be a new version coming, but I think a lot of us here are eager to use this fantastic lib you've created - infact, I've already got it running on a production website.
As much as I want to use it again on the next project and continue singing your praises, it's hard when I have to tell my clients and managers "Oh, sorry about that bug which occasionally stops the content from rendering at all, but I promise, there's a new version coming which will fix the bug!". From a business perspective, this just isn't a viable approach - especially as I would expect v2 will come with other breaking changes that prevent a clean upgrade.
Surely, while we wait for v2, it would be a rather rudimentary exercise to just merge this PR onto the master branch, and publish a minor NPM version to fix this issue which is preventing MoJS from being feasable for production environments?
At the same time, as an avid fan it's worrying, and as someone looking to contribute, it's disheartening, seeing such a delay on implementing a one-line fix for a chronic bug. It's been several months since I created this PR, and many more since the original issue was filed. As users, are we simple expected to just wait in limbo?
I'm sorry for the essay, but this could be the start of a very worrying trend. I've seen this before in inspiring open source projects, and I'd hate to see it happen again.

@SudoCat @talb-senexx
You are right, there is the new release: https://github.com/legomushroom/mojs/releases/tag/0.288.2 , it should be on npm immediately, and will pop up on the CDN and bower very soon.
Cheers!

Thank you, @legomushroom, this is great.


[VS Code] Joining collaboration session: Unable to connect to the host. Verify both you and the host are online.

Error:
Joining collaboration session: Unable to connect to the host. Verify both you and the host are online.
Steps to Reproduce:
1.
2.

Version Data

extensionName
VSLS

extensionVersion
1.0.488

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.35.1

platformName
Windows

platformVersion
10.0.17134

Hey @newvishal , could you provide some more information about what you were doing when this happened? Does this consistently happen for you?

Closing due to inactivity. Please reopen if you can provide us with more info.


Image2Image, Inpaint pipelines?

Can you also add the remaining pipelines for Image2Image, Inpaint, and ControlnetInpaint?

I'm wondering where is inpaint code?


Add comment section

Created a comment section for users to post their opinion of my webpage... or just me in general.

Ability to do post request
Display user comments on webpage

Can you please merge "Week 3 Walkthrough Part 2" to master and rebase this branch from merged master? ---> This way changes in previous pull request won't show up here.
Also, think about giving a more meaning full name for the pull request. Eg. "Adding comment section".

Done. Rebased, merged and changed the name of the pull request.

Resolved comments.

Got rid of unnecessary vars


POST api-key route returns 500 Internal Server Errors instead of a meaningful error

Description

POST /service/{{service_id}}/api-key route to create a new API key requires a property 'key_type', which must be in an enum [ normal, team ].
POST /service/{{service_id}}/api-key route to create a new API key requires a property 'name', which must be unique.

When posting to this route to create a new api key with the above properties set with bad values, since we know the problem, we should return 400 Bad Request and a meaningful response message.
There is a though that this was done for 'security by obscurity reasons,' but we can still return a 400 instead of a 500 with an obscured message directing them to the API Docs if we are concerned about returning the real reason.
Steps to Reproduce
Bad key_type value: POST /service/{{service_id}}/api-key with the following payload in Postman
{
  "name": "some_unique_string",
  "created_by": "{{user_id}}",
  "key_type": "foobar"
}

Bad name value: POST /service/{{service_id}}/api-key with the following payload in Postman, replace "some_not_unique_string" with a real APIkey name from that service.
{
  "name": "some_not_unique_string",
  "created_by": {{user_id}},
  "key_type": "foobar"
}

Observe that the response is a 500 Internal Server Error
Workaround
Is there something we can do to work around this issue in the meantime? Leave blank if n/a.
Impact/Urgency
Required. Describe the impact this bug has on our system, clients, and/or team.

Low but annoying

Expected Behavior
When I post to create a new API Key
Using a bad value for name or key_type,
Then I expect a meaningful 400 Bad Request response and a meaningful if possibly obscurred error message.
QA Considerations

[ ] POST returns 400 Bad Request when a string not defined in the enum for key_type is in payload
[ ] POST returns a meaningful error message for same
[ ] POST returns 400 Bad Request when a non-unique string for the name is in payload
[ ] The above should only be true if the authentication was successful, otherwise return auth failure regardless of body
[ ] Update the QA Suite to unskip this test

Additional Info & Resources
If applicable, include extra information to assist with troubleshooting, like screenshots, log snippets, links to applicable code files, and/or articles/websites that have relevant info on the issue. Leave blank if n/a.
Note that the 400 Bad Request error responses for all of the api-keys routes are not the same as the Not Found error responses for other service routes nor do they match the swagger responses for 400s.
For now, the 400 Bad Request  message should at least match what the rest of the api_keys Bad Request responses are, which should be more or less
{
  "message": {
    "key_type": ["String not defined in enum: [ normal, team ]."],
    "result": "error"
  }
}

and
{
  "message": {
    "name": ["This name already exists."],
    "result": "error"
  }
}

Several people have suggested that the existing behavior might be intentional for security purposes.  At a minimum, we should log the actual error.

Just to clarify: The name needs to be unique per service

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @jakehova @justaskdavidb2 @k-macmillan @kalbfled @ldraney

Still valid/keeping for when we do V3 route work.


Turn into an Arduino library

Turning this into an Arduino library could lead to exponentially more users, as it would make the code more MCU independent. A target that may be especially worthwhile is the Arduino Core for Nordic Semiconductor nRF5 based boards that use Bluetooth Low Energy (e.g., search ebay.com for NRF51822-04).
By the way, there is an Arduino core for the ATtiny2313, too.

Using Ardiuno feels cumbersome to me. So usually I'll just go bare metal. Right now I don't have the time to work on this but I'll probably make an Arduino lib out of this.
Btw on the security of the in-home-bus: there is none. Replay attacks work just fine.

Btw on the security of the in-home-bus: there is none. Replay attacks work just fine.

Interesting. I feel a 35C3 talk coming; security by obscurity never works.

https://github.com/mbs38/siedle-in-home-bus-arduino
A hardware adaptor has already been designed. Some resistors still need to have their values calculated though.

Thank you. Great work!

The ino sketch appears to be missing from https://github.com/mbs38/siedle-in-home-bus-arduino, maybe it was not uploaded?

Update:
I've decided that I won't do this as I don't have any use for an arduino based solution myself.

Update: I've decided that I won't do this as I don't have any use for an arduino based solution myself.

i saw you deleted the Repo. Would it be possible for you to share your arduino library again?

Update: I've decided that I won't do this as I don't have any use for an arduino based solution myself.

i saw you deleted the Repo. Would it be possible for you to share your arduino library again?

Hi Lukas,
I only started doing the hardware part and never even began implementing a library for Arduino so there really is nothing I can share.
Max


No nonbinary, transgender or cisgender only male and female in entities.cr

The file src/html/entities.cr I have noticed that it has male & female. But where is nonbinary and transgender. This is very concerning to me and many others.
Line 1309 it says male
"male;"                            => '\u{002642}',
Line 974 it says female
"female;"                          => '\u{002640}',
The file does not make any mention of cisgender, transgender, nonbinary this can be seen to many people as transphobic and homphobic to a lot of people including myself.  i would like to make a request that you add the genders it doesn't mention or completely remove male and female from the file. thank you for listening i hope something can be done in the name of equality

I had to create a github account...
@girng what the hell is your problem, these words are offensive. Theres no such thing as a "gender".
I'm literally shaking right now.
Its 21. th century. move on and stop being so intolerant.


multilevel menu

Is it possible that create multilevel menu in this project?

Sure, you may edit on Drawer.vue then within items add children like this
{           icon: 'mdi-account',           title: 'user',           children: [             {               title: 'Add New',               to: '/pages/user',             },             {               title: 'Show All',               to: '',               children: [                 {                   title: 'Removed Users',                   to: ''                 }               ]             }           ],         },

i tried doing this and found two things

the url the submenu tries to go to includes a /undefined/ part in the path which is weird

i.e http://localhost:8081/#/undefined//clientname-setup

even though i defined an icon, the submenu still displays the first characters of each subitem title words as shown in the example above. is this by design or is there a way to display an icon?

this is an example of how i have the data setup:

data: () => ({
      items: [
        {
          icon: 'mdi-view-dashboard',
          title: 'dashboard',
          to: '/',
        },
        {
          title: 'schema-builder',
          icon: 'mdi-clipboard-outline',
          to: '/schema-builder',
        },
        {
          title: 'client-data-setup',
          icon: 'mdi-account-cog-outline',
          children: [
            {
              title: 'clientname-setup',
              icon: 'mdi-account-details-outline',
              to: '/clientname-setup',
            },
          ],
        },
      ],
    }),


Laggy transition between controllers/Looping animations are completely broken

I tested versions 3.0.49/3.0.50 and 3.1.31/3.1.32 and in both, when transitioning between controllers, a frame of the default pose will appear in between.
This persists between all the versions that I tested in multiple projects. Also, looping animations will either not stop or not start at all. I've tested the example car model and the issue is present, so I know it is neither my code nor models that are causing this. (only on versions 3.0.50 and 3.1.32)
Reverting back down to 3.1.30 or 3.0.48 seems to fix everything.
https://imgur.com/9hRQKTe.mp4
This was recorded in a new, completely clean 1.19.2 project with version 3.1.32

Same issues and more https://imgur.com/NEkpcuz.mp4
3.1.29 breaks model parts
3.1.31 breaks animation controllers (laggy transition)
3.1.32 (not shown in the video) broke all of my looping animations even after updating to the new methods

Actually, in 3.1.32 my poor model was even more broken with some parts not even being part of the body anymore...

This is fixed in dev with more fixes coming, no ETA on release.


node full stackserver

trying to depoy it on heroku

This app does not require a server to run. It's used for development purposes only.


HTML Select element has bad background on dark theme

Describe the bug
The Select input element in the New/Edit trigger page has a background not in line with the website theme: in my case I have a dark theme and the select menu has a white background with white text
To Reproduce
Steps to reproduce the behavior:

Create a pipeline
Create a trigger
Go to the trigger settings
Open the Frequency menu and observe the background

Expected behavior
The background should be in line with the current website theme
Screenshots

Desktop (please complete the following information):

OS: Microsoft Windows 10 Enterprise
Browser: Chrome
Version: 108.0.5359.125

Additional context
My OS preference is to use a dark theme, so I see mage with a dark theme, I don't know if there's a light theme as well

Thank you so much for sharing, will fix this.

Hi @lucafaggianelli! We've added this to the roadmap and should be released in the upcoming week. You can see our current roadmap here: https://airtable.com/shrJctaGt4tvU27uF/tbl5bIlFkk2KhCpL4
Thank you for your patience and we'll keep you posted!

Fixed by https://github.com/mage-ai/mage-ai/pull/1965


Hyperion on OpenElec 5.0.5

I recently received the new Raspberry PI 2 and loaded it with OpenElec 5.0.5.  Installation of Hyperion went fine, copied the config from my RPI 1, which is currently working fine, but I cant seem to get output to the RPI 2.  Running ps shows hyperiond.sh is running with the correct config.  LEDS have power.  I am using WS2812b and GPIO18 to drive them.

OpenELEC:/flash # ps
< Some stuff removed>
357 root       0:00 {hyperiond.sh} /bin/sh /storage/hyperion/bin/hyperiond.sh /storage/.config/hyperion.c
< Some stuff removed>
OpenELEC:/flash # /storage/hyperion/bin/hyperion-remote.sh  --effect "Rainbow swirl fast" --duration 300000
Connected to localhost:19444
Start effect Rainbow swirl fast

Possibly to do with the increase frequency of the processor?
I don't have a scope nearby

Used a scope and could not find any output on GPIO18.
Possibly the change of the PWM address on the DMA controller?

Have you turned SPI on in config.txt?
pt., 6 mar 2015, 05:07 r3dr4bbit użytkownik<EMAIL_ADDRESS>napisał:

Used a scope and could not find any output on GPIO18.
Possibly the change of the PWM address on the DMA controller?
—
Reply to this email directly or view it on GitHub
https://github.com/tvdzwan/hyperion/issues/277#issuecomment-77503667.

Correct me if am wrong, but the WS2812b implementation does not use SPI.  Rather it uses a PWM signal generated on the PCM_Clock.

As suspected, it is a problem with the new memory address.
See fix here: https://github.com/tvdzwan/hyperion/issues/6#issuecomment-77109750


PHP-FPM for Sail in production

I'm started to use Sail in production and it's great!
But it lacks of one thing – an ability to use PHP-FPM as server instead of php development one (with artisan serve).
Development team, please, update dockers build file to have an ability to work through php-fpm.

Hi @dbelyaeff. Sail is meant as a development tool and not as a production tool.

sometimes I need testing api some services, and they want https. If you will add nginx + php-fpm will great

@driesvints are there know dangers of using Sail in production env?

@dbelyaeff, you can publish and override Dockerfile and docker-compose.yml or using traefik

@driesvints: would you answer to above questions, please? specific @alagiesellu question.

@mmdglmr I already answered those. Sail is a development tool, not a production tool.

Acceptin that sail is a development tool, is there a tutorial, howto, dummys guide to transitioning from sail to production?
I, like many others, have such limited expeience with docker, we use sail to develop on. now, once we are in a position to push to production, I for one, have no idea where to start the transition.
do i rip sail out?
do i edit the sail docker file to include nginx and other bits?
*is sail just the CLI part and so not actually part of the docker thing anyways?
please help demistify this for us. ty.

a very kind & open request...
Accepting that Sail is a development tool, is there a tutorial, howto, dummys guide to transitioning from Sail to production?
I, like many others, have such limited expeience with Docker, we use Sail to develop on. now, once we are in a position to push to production, I for one, have no idea where to start the transition.
do i rip Sail out? do i edit the Sail docker files to include nginx and any other bits needed like ffmpeg, gmp etc?
*is Sail just the CLI part and so not actually part of the docker thing anyways?
Would you or someone who understands please help demistify the process for us. ty.

Sail has nothing to do with the production environment. It uses php artisan serve command to run the webserver so you can't use Nginx config files.
If you need docker for production you can build your own image. If you don't need it at all, you can use Nginx for production.
The following link documents the needed configurations:
https://laravel.com/docs/8.x/deployment

We are currently using sail for development and docker based deployments on Laravel Vapor. We have a requirement for FFMPEG so we've updated our sail container to build FFMPEG. This works well and we have spent a lot of time ironing out issues during development. We also followed the advice at https://blog.laravel.com/vapor-docker-based-deployments to add ffmpeg to our vapor container.
Our problem is that we have different versions of ffmpeg installed on development and on vapor. These version mismatches are causing intermittent errors on staging and production that are extrememly difficult to debug.
We are relatively new to docker and thats why we used Laravel Sail. We chose this as we believed the benefits were that our production, staging and local environments would behave exactly the same.
Some potential options below

Can we deploy the sail 8.0/Dockerfile so that our production environment is exactly the same as our local?
Can we use the laravelphp/vapor:php80 locally within sail so that our local environment matches our production and staging?

If I am missing something please point me in the correct direction to understand my options here.
TIA

Sail really should have an option to convert it to a production-ready container, or at least to publish Sail's dockerfiles or something similar. Making it development-only largely defeats the purpose of having a containerized workflow. One of the key selling-points of containerization is to have consistent and predictable environments. Not giving users the ability to deploy their Sail-based applications directly is a huge miss, imo.

what is the purpose for containerization then :D

I found a very amazing tool for Laravel deployment LaraSail
https://github.com/thedevdojo/larasail
Does the work well.

This is 'DigitalOceon' Specific. May not work for other hosting providers (AWS, Azure, GCP)

Well,
Below could be one of the solution.
1 . Install docker on your hosting machine (aws, azure, gcp, etc...)
2 . go to the root directory of your app
3 . type below command to install software dependencies.
docker run --rm \
    -u "$(id -u):$(id -g)" \
    -v $(pwd):/var/www/html \
    -w /var/www/html \
    laravelsail/php81-composer:latest \
    composer install --ignore-platform-reqs

4 . make docker container run in the detach mode (sail up -d)

Refer this url for deploying laravel sail over aws,

Laravel offers paid service - Laravel Forge - for serving Laravel applications for production using real webservers.
If they would include a sail build-for-production-with-nginx command, and extend the docker setup with Nginx and PHP-FPM, it would kill their business of their paid services...


Update key-vault-linux.md

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


Connection error when publishing a message with java-function-invoker

I see this fairly consistently when the java-function-invoker launches (greeter sample).
2017/11/21 14:40:54 Error invoking http://localhost:8080: Post http://localhost:8080: dial tcp [::1]:8080: getsockopt: connection refused
2017/11/21 14:40:54 Error dispatching message: Post http://localhost:8080: dial tcp [::1]:8080: getsockopt: connection refused

This causes the function to remain deployed until a second message is published.  It appears to be due to the lag in the java-function-invoker start up time compared to the function-sidecar. We should probably add retry logic to the sidecar and/or get the pod to terminate if there is an error.

It's there already, but chances are you have an old sidecar (because the helper script doesn't checkout master). Should be fixed by now though

Ok. I'll take a look

Closing this. I think it's stale.

Hello, I am facing the same problem,
when I issue command
riff publish --data hello --reply
I get error
Posting to http://<IP_ADDRESS>:31007/requests/uppercase
Post http://<IP_ADDRESS>:31007/requests/uppercase: dial tcp <IP_ADDRESS>:31007: getsockopt: connection refused

I am using Spring BOOT 2.0.1.RELEASE and Spring Cloud Function 1.0.0.BUILD-SNAPSHOT & reactor.version 3.1.2.RELEASE...

@mgorav I've seen similar errors on my system after upgrading several system libraries (not sure of the root cause 😞) and wasn't using the java invoker. Can you try adding -i foobar to your riff publish command to see if still get the same error. If so, the error is between the riff-cli and http-gateway, and the java invoker is innocent.

Reopening...


flyway: 9.0.4 -> 9.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/flyway/versions.
meta.description for flyway is: "Evolve your Database Schema easily and reliably across all your instances"
meta.homepage for flyway is: "https://flywaydb.org/"
meta.changelog for flyway is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.1.2 with grep in /nix/store/h5lpc3416rsgbyq2gypyl15agkx3mvdz-flyway-9.1.2
found 9.1.2 in filename of file in /nix/store/h5lpc3416rsgbyq2gypyl15agkx3mvdz-flyway-9.1.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
flyway

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/h5lpc3416rsgbyq2gypyl15agkx3mvdz-flyway-9.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flyway https://github.com/r-ryantm/nixpkgs/archive/8787835fe3821e47b4e0043d96be329f44416604.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/h5lpc3416rsgbyq2gypyl15agkx3mvdz-flyway-9.1.2
ls -la /nix/store/h5lpc3416rsgbyq2gypyl15agkx3mvdz-flyway-9.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

flyway

Maintainer pings
cc @CMCDragonkai for testing.

nixpkgs-review build went fine on NixOS 22.05 Linux x64
Also able to run the program.


chore(deps): bump stackrox/rox dep

Bump this version in preparation for the future removal of pkg/bolthelper. stackrox/rox and stackrox/scanner unfortunately have a circular dependency, so I think it's best to try to catch up with the latest version of stackrox/rox before stackrox/rox catches up with stackrox/scanner.
This PR also bumps the minimum required go version to 1.19, as stackrox/rox requires this

Go 1.21 is kind of annoying. Maybe this PR should wait until stackrox/stackrox updates to go1.21

Depends on https://github.com/stackrox/scanner/pull/1454


Spelling

What type of PR is this?
/kind cleanup
/kind rule-update
Any specific area of the project related to this PR?
/area build
/area engine
/area rules
/area tests
/area proposals
What this PR does / why we need it:
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/falco/commit/fe4788d51b99f7dae4213e57921cd3dbef37adae#commitcomment-67427362
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/falco/commit/7978e6869a54a620ceb941e04b3af90e17042c2f
Which issue(s) this PR fixes:
Special notes for your reviewer:
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Does this PR introduce a user-facing change?:
Fixes for miscellaneous typos

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jsoref
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @jsoref! It looks like this is your first PR to falcosecurity/falco 🎉

LGTM label has been added.  Git tree hash: 031284be54e7546afb2bf1a32844f23729195b31

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, jsoref
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, jsoref, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.32.0

Sure, added to my todo list https://github.com/stars/jsoref/lists/to-check-spelling (which is quite long).


Path issues windows

When using patch.oldFile().path(); as per example seen here https://github.com/nodegit/nodegit/blob/master/examples/walk-history-for-file.js#L27 the path returned here stays with forward-slashes (/), where-as when you use nodejs' path it returns backwards-slashes. This now makes comparing part of the path quite hard.
The workaround I currently have it just to replace all slashes in the path string, so they match.

Git uses forward slashes internally, we should never ever change them to be back slashes.

ahh ok, so what is the recommend approach on windows then? Just not use the nodejs path module?

Node normalizes paths for you.  Can you paste an example where this isn't true?

That is exactly the problem - node normalizes the path to windows style, so path\to\file but git uses path/to/file.

Try using: https://nodejs.org/api/path.html#path_path_format_pathobject

I think this is out of the scope of NodeGit, which is attempting to bind 1:1 to libgit2 and where possible provide some convenience over repetitive tasks.  By allowing either Unix or Windows style, we'd be breaking a convention from within Git.
You can normalize with a simple enough replace regex: path = path.replace(/\\/g, '/');

@Globegitter could you not call path.normalize on the returned value, like so?
path.normalize(patch.oldFile().path());


Restore the header row

Looks good to me, I just had those two comments. I'm happy to merge if we are keeping the language inside the class for now.

We could have a static mapping of textcontent and titles on the main browser class that could be swapped out, which is in turn passed to the sub-classes.

That's a good strategy, yeah. Since most of our widgets don't have language in them, this isn't coming up too frequently, but something like what you're suggesting sounds good to me.


Monitoring - kube-state exporter print too many error log

What kind of request is this (question/bug/enhancement/feature request):
BUG
Steps to reproduce (least amount of steps as possible):

Enable Cluster Monitoring

Result:

kube-state exporter keeps printing error logs

Other details that may be helpful:

Cannot list poddisruptionbudgets.policy, it seems kube-state exporter doesn't have the list and watch permission on poddisruptionbudgets.policy resource.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): master
Installation option (single install/HA): single

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Custom

Observe the same issue on v2.2.0

The log shows in kube-state exporter pod. There is no harmful. So I think it's not a blocker issue. If we want to fix it, we need to release a new version of monitoring chart

I upgraded to v2.2.2 and then enabled monitoring - I had previously enabled and then disabled it when it did not work - and I'm seeing the following error in the exporter-kube-state-cluster-monitoring workload
E0417 02:18:42.366969 1 reflector.go:205] k8s.io/kube-state-metrics/pkg/collectors/builder.go:508: Failed to list *v1beta1.PodDisruptionBudget: poddisruptionbudgets.policy is forbidden: User "system:serviceaccount:cattle-prometheus:exporter-kube-state-cluster-monitoring" cannot list resource "poddisruptionbudgets" in API group "policy" at the cluster scope

@junkiebev Do you mean your monitoring doesn't work now?

@junkiebev Do you mean your monitoring doesn't work now?

that workload was blowing up and creating a new configmap every few minutes.

This error will not cause the exporter-kube-state-cluster-monitoring pod failed.
The configmap issue will be fixed in https://github.com/rancher/rancher/pull/19079
Can you look at the logs and events for the pod?

The issue may be related to workers re-starting plan monitors due to websocket timeouts. You want the logs for the exporter-kube-state-cluster-monitoring pod, right?

@loganhz  - It looks like the cluster monitoring catalog item has a PR in which would fix this error:
https://github.com/rancher/system-charts/pull/27

Chart PR merged
Waiting for https://github.com/rancher/rancher/pull/19766 https://github.com/rancher/types/pull/801 https://github.com/rancher/system-charts/pull/37 merged and https://github.com/rancher/rancher/pull/19766 https://github.com/rancher/types/pull/801 backport to 2.2. branch.

The bug fix is validated on Rancher: master beffccd
Step:

add an ec2 cluster
enable cluster monitoring
check the log of the workload exporter-kube-state-cluster-monitoring under proejct System and the namespace cattle-prometheus

Result:

the error messages showed in the original issue are gone


typo in javadoc

Check List:

Fixes javadoc
Unit tests: NA
Javadoc with a code example (API only) : NA

Cool, thanks for reading the javadoc 😄


fix canvas sprite texture change

Let us fix #3997

@brenwell

AnimatedSprite caching tint - https://jsfiddle.net/brenwell/62qub9vn/4/
TilingSprite not tinting - https://jsfiddle.net/brenwell/yo2Lz9dc/1/

Saving it here, will make tests of them some day.


Heptic feedback improvement suggestion:

If disarmed - do not vibrate on Compass, level , or GPS fix alerts.
Those are big and impossible to avoid, but the vibration-sound makes people crazy when working on a Solo inside.

PRs welcome!


Add 1.1 scale for tank and heavy class

Make Entity:SetModelScale for tank and heavy

I was seeing that if I mess with player scale, their hitbox also are changed. I thing this can cause some troubles for the big boy. Like can fit in some place.


Add a new config to override kubebuilder printcolumn:name

Issue N/A
In some CRDs like GlobalTable adding a is_printable: true to the GlobalTableStatus causes kubectl get to print very large/redundant column names.
Description of changes:

This patch adds a new config to allow overriding kubebuilder printcolumn:name
Adds metav1.Time to the acceptableColumnMap

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

Hmm I wish I had the foresight to add this initially, because I'd probably have made the config a struct containing the boolean and the string - rather than them both being on the parent resource level. Regardless, without breaking backwards compatibility, this is good.
/approve

Hmm I wish I had the foresight to add this initially, because I'd probably have made the config a struct containing the boolean and the string - rather than them both being on the parent resource level. Regardless, without breaking backwards compatibility, this is good.

Agreed. I hesitated to introduce a struct config for it.. but as you said it will break the compatibility .. maybe one day a generator config v2 :)

/lgtm


Add "Clear VM" button to the IDE

Clear the ChucK Instance for public class re-instantiation
feature request from @tae1han

@tae1han Won't be working on this feature since there would be some sensitive VM things that the IDE needs to preserve like HID functionality and the like.
Although not recommended, you can manually clear the ChucK VM with code by doing:
Machine.clearVM(); // Note this would break HID

Hopefully #18 will be able to achieve a similar result as clearVM and maintain WebChucK IDE classes/VM basic things


Getting error while starting VS in docker after upgrade to v1.3.1

[bug] Getting error while starting VS in docker after upgrade to v1.3.1

Additional info:

all files connected to docker, webpack or typescript configuration are not modified;
themes and extensions are temporary removed from the project;
previous VS (1.2) works well in docker;
running VS (1.3) on non-docker environment in development/production mode is successful (localhost:3000)

vue-storefront.sh:
#!/bin/sh
set -e

yarn install || exit $?

yarn build:client && yarn build:server || exit $?

if [ "$VS_ENV" = 'dev' ]; then
  yarn dev
else
  yarn start
fi

Dockerfile:
FROM node:8-alpine

ENV VS_ENV prod

WORKDIR /var/www

COPY package.json ./

RUN apk add --no-cache --virtual .build-deps ca-certificates wget git \
  && yarn install --no-cache \
  && apk del .build-deps

COPY docker/vue-storefront/vue-storefront.sh /usr/local/bin/

CMD ["vue-storefront.sh"]

default.env:
NODE_CONFIG_ENV=docker
VS_ENV=prod
BIND_HOST=<IP_ADDRESS>
PM2_ARGS=--no-daemon

Steps to reproduce:

clone the repository
run docker-compose up inside the project

Fresh installation:

Local Environment:

OS: MacOS
Docker: 18.06.1
Language: [TypeScript 3.0.3 | NodeJS - 8.11.4 | npm - 5.6.0 | yarn - 1.7.0]

Docker Environment:

OS: Linux
Language: [TypeScript 3.0.1 | NodeJS - 8.11.4 | npm - 5.6.0 | yarn - 1.6.0]

@vue-kacper can You please test this issue as You're testing it on Linux anyway?

@pkarw fixed issue by adding missing lines/files to volumes config in docker-compose.yml
- './tsconfig.json:/var/www/tsconfig.json'
- './shims.d.ts:/var/www/shims.d.ts'

Docker starts now. Is it correct fix?

@kovinka yes, please create Pull Request for it

@pkarw done, please review PR.

Thanks! Merged in :-)


gradle version 4.1.3 throwing error for for ktlint version - 0.40.0

Expected Behavior

Observed Behavior
Gradle version is updated from 4.0.1 to 4.1.3 and this breaking the Ktlint.

What went wrong:
Execution failed for task ':app:ktlint'.

The value for task ':app:ktlint' property 'mainClass' is final and cannot be changed any further.

Steps to Reproduce
Code from build.gradle
task ktlint(type: JavaExec, group: "verification") {     doFirst {         def changedFileNames = project.extensions.extraProperties.get('changedFileNames')         for (fileName in changedFileNames) {             classpath = configurations.ktlint             main = "com.pinterest.ktlint.Main"             args fileName         }     } }

Version of ktlint used: 0.40.0
Name and version (or code for custom task) of integration used (Gradle plugin, Maven plugin, command line, custom Gradle task):
Version of Gradle used (if applicable): 4.1.3
Operating System and version: Android

@kirti04 this is a Gradle problem, not a ktlint-specific problem. I'd refer to https://github.com/gradle/gradle/issues/12841 to see if you can resolve your issue.
Alternatively, there are a couple ktlint gradle plugins you can try (links in the README.md).

Thank you . That helped.


Feature: Delay / Easing on Tilt

Wondering if its possible to implement a delay or add easing to the tilt effect.
See how http://thexx.info/home/ works for an example.

Worked it out, you can just use easing and it works... duh!


Update backoff

Proposed changes
Closes #1268
Superseeds #1268
The patch dependabot proposed in #1268 does not suffice, as the API of the crate was changed a little bit as well. This PR adds the patch dependabot suggested and adds a patch for the changed API interface.

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

This should wait for #1273 to be merged.

@dependabot rebase


Vapor of levity causing massive lag

Issue Description:
Apparently larger quantites of vapor of levity will cause massive lag.
What happens:
I tried to use it as a coolant for my max size extreme reactor. My tps went down to around 4-5. I even tried unloading the chunks but that didn't help either. It doesn't matter if the reactor multiblock is formed or not. I don't think it has anything to do with the reactor.
What you expected to happen:
I obviously expected it to not affect tps in a significant way.
Steps to reproduce:

Fill a moderately sized room with vapor of levity (I suggest at least 16x16 and around 30 blocks high), just placing it on the floor and letting it flow up until it hits the ceiling.
Check /forge tps.
Be amazed at how it destroys your tps.

Affected Versions (Do not use "latest"):

EnderIO: 3.1.164
EnderCore: <IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: <IP_ADDRESS>5

Your most recent log file where the issue was present:
No crash log, since it didn't cause a crash.

Please attach a profiler (e.g. warmroast) and drill down to what takes the time. I cannot see anything here, even with a full chunk of it. Server is still spending way over 90% of it's time in Thread.sleep(), and most of the rest is trying to spawn mobs.

I reproduced it in a new clean MultiMC instance, the only mods being EnderIO and EnderCore. Just filling a section of a chunk already had a huge impact. Mean tick time went from around 5 ms to 15 ms.
Check out the screenshots attached.

In SF3 I created a RFTools Dimension where Huge Liquid Orbs were filled with Vapor of Levity, this Levity was in a confined space, didn't flow up or anything, they were nicely packed inside the orbs. Loading in the dimension brought server TPS down to below 10, even 5. Needless to say I scrapped the dimension. Filling a decent size reactor with Vapor of Levity causes significant TPS drops as well.

I tried reproducing this and could not.
EnderIO: 3.1.171
EnderCore: <IP_ADDRESS>-beta
Minecraft: 1.10.2
Forge: <IP_ADDRESS>9

the other example was using stone, not glass, this is not an exact reproduction

I tried it with stone and had the the same results. Not sure what I'm missing as far as reproducing this goes...

You're testing with the latest version, so either this doesn't happen for you, or my changes did work. I'm now preventing Forge's fluid code from running most of the time---the code that checks if a fluid can flow into a new block.

Sounds like it might be fixed then. Hopefully 1 or 2 other people can confirm my results on latest.


VersionB PropertyValue.ValueCase return 20 after setting DataType to DataType.PropertySetList

I would like to report an issue when setting VersionB PropertyValue's DataType to DataType.PropertySetList.
        var propertyValue = new PropertyValue()
        {
            DataType = DataType.PropertySetList,
            PropertySetsValue = new PropertySetList()
        };

When I checked the ValueCase of the PropertyValue, it somehow returned 20, which indicates PropertySet, rather than 21, which indicates PropertySetList.
I can force the ValueCase to 21, but I think it should be set to 21 automatically.
I hope I have explained the problem clearly as English isn't my mother tongue.
Thank you very much for your useful library!

I'm currently reworking the total conversion and value assignment and try to back all those things by unit tests. Stay tuned, I hope to finish this soon.

Fixed with https://github.com/SeppPenner/SparkplugNet/releases/tag/1.3.3.


P2SH-Segwit and Legacy Single Signature signing occasionally failing

I am using LibWally-Swift to sign for multisig and single signature transactions/psbt's.
Frequently I get an error for P2SH-Segwit transactions when broadcasting them:
non-mandatory-script-verify-flag (signature must be zero for failed check(multi)sig operation
And occasionally for Legacy I get an error when broadcasting as well:
mandatory-script-verify-flag-failed (operation not valid with the current stack size) (code 16)
In the readme it states Compose and sign (SegWit) transaction. Does that imply non segwit transactions do not have signing functionality? I am confused because in the tests it has examples for signing all three types of transactions.
As a side note if it is a multisig transaction all three formats work fine as do single sig Native Segwit transactions.
Of course I may be doing something wrong... However if you have any obvious advice for me it would be much appreciated. Again thank you for the wonderful library.

You should be able to sign all input types; I removed the confusing "(SegWit)" from the README.
To clarify, you're spending from P2SH-Segwit or from Legacy addresses when you see these errors?
Also to clarify, are you seeing this when signing a PSBT or when signing a Transaction you composed yourself? These are separate code paths.
Do you see it consistently for the same transactions or does it work when you try again?
Examples would be very useful, but don't doxx your mainnet coins...

This was user error. I am using bitcoin core to build the psbt's and was not specifying the change_type in the walletcreatfundedpsbt arguments and forgot that the node would create segwit wrapped change addresses by default, I was attempting to sign specifically for P2WSH inputs. Works like a charm now that I account for multiple address formats for the inputs.

Thanks for the update. I would still like the library to catch this earlier...


Collections Keywords for Dictionary objects requires Scalar Variable Syntax

Version information
Robot Framework version: 3.0.2
Python interpreter: Python3
Operating system: OSX 10.13.3
Issue
The keywords for interacting with dictionary variables require passing the dictionary using scalar syntax instead of the dictionary syntax.
Expected
&{dictionary}    name=arg
Dictionary Should Contain Key    &{dictionary}    key   message

Actual Working
&{dictionary}    name=arg
Dictionary Should Contain Key    ${dictionary}    key   message

This is by design. If you use a variable like &{var}, then it's items are passed as individual arguments as name=value. To pass the value as a dictionary, you need to use ${var}. This is explained in the User Guide but I'm sure the docs could be enhanced:
http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#dictionary-variables
Let us know if you have ideas how to enhance the docs.


Update readme.md with AUR package

I created an AUR package for easy installation on Arch Linux.

Awesome! Have you automated the upgrade process, or will the version need to be updated manually whenever a new release comes out?


Trey Icons not Working

Love this script. My only issue is that the trey icons are not working in 11 Pro. I don't get anything when I left click on wifi, sound or battery only right click

Love this script. My only issue is that the trey icons are not working in 11 Pro. I don't get anything when I left click on wifi, sound or battery only right click

It is working for me (installed two days ago)

Going to try on different hardware. First was a Dell XPS 16. Installing now on a Lenovo P14S

Downloded a new ISO and things are working better now

@TahoeMiah Glad you like it! Yeah I haven't had that issue, I'm glad the new ISO fixed it for you.

Just to recap. I created an ISO from the DVD in a windows 11 PRO OEM disk. Then I used NTLite to add updates, inject the necessary NVME intel drivers and remove other editions of 11. Then, I added the autounattend file with anyburn.  After install, the trey icons did not work
Same process, except I downloaded a new ISO from microsoft. No trey icon problems


Provide base for 2.15

Version 2.15 of Gerrit is coming:
https://www.gerritcodereview.com/releases/2.15.md
Highlights:

New change workflows for changes not yet ready for full review
(formerly Drafts).
The new PolyGerrit UI is mature enough for most uses.
Account data is stored in NoteDb.
NoteDb migration for change metadata is available.
Made several improvements and additions to the documentation to
help
users find the information they need.

Change-Id: I767b84f078552ceb81fb3772fb4091227abf9d66

This is not meant for master but for a new branch 2.15-rcx !
Couldn't figure out a way to propose a new branch as a pull request.

A 2.15.rc branch is created. Would you please rebase you commit then submit your PR on that branch again? However, I kind of feel that it's a little early for us to track the 2.15 already, unless you really need to see how it works on docker.

I'm starting to experiment with 2.15 as I'm working on a new infrastructure and would like to try a database free design. Seems like NoteDb might be ready for prime time.
However I already have a branch in my fork so it won't impact me if you don't accept this PR, and it is more an open question about whether or not we want to make some pre releases available in a separate branch. I imagine that we could remove that branch once 2.15 is out.
I'm also wondering about the interest for a 'nightly' branch that would just take the latest Gerrit and plugins out of CI.

Someone just asked me a question in #77 about the NoteDB that makes me notice the database free option introduced in 2.15. It's so tempting and I even want to have a look at it myself. So I think it's worth creating a temporary RC branch for it.
Nightly branch is also open to discuss. Although I have to figure out a way to trigger it nightly.


Import metadata

Add title and description metadata to authored pages

Added title and metadata description for the following:
https://main--caesars-careers--hlxsites.hlx.page/contact-form


Considering updating the documentation to state that the default configuration of this container is insecure

Like tens of thousands of other MongoDB users, we were ransomed. This is embarrassing, especially for me who had told my developers that it's extremely unlikely that a widely used piece of database software distributed in 2023 would have insecure defaults.  Yet it happened.
To recap:

MongoDB by default binds to a local port
When run inside the container, however, it must bind to an interface that can be exposed to outside the container
When a user uses Docker's -p flag in its default incantation, the port is publicly exposed
Because docker writes straight to iptables, this happens even if a firewall is set up
This container ships in a configuration where authentication is disabled

This issue appears to be well known to the developers, but so far there is no mentioning of this glaring problem on the Dockerhub page of this container.
This behavior breaks expectations, and although not all blame lies with MongoDB's lack of a password in the default configuration -  Docker's default behavior to assume -p <IP_ADDRESS>:host:container is to blame as well - it seems to me that an "official" image should warn about this trap which is easy to fall into.
Please consider updating your documentation. The current idea - which to me appears to just not mention the behavior that occurs on -p - and to bury the fact that authentication is disabled by default in the fine print is, in my view, suboptimal, to put it mildly.

I'd like to follow up on why I believe that the current behavior "breaks expectations."
When users install official versions of software using their package manager - say running apt-get install - they do not expect that the act of doing so by itself will expose their software unprotected to the world, even if their machine is connected to the Internet. That is, I'd argue, an expectation that's been in place for 10 years if not longer.  In fact, when mongodb in 2017 introduced this default behavior this was - 6 years ago - already an outlier.
Now, when you package and distribute a piece of software in a container, you should be following similar rules. That is, the mere act of downloading and activating the software using commonly used steps should not leave you with a vulnerable installation. This should be true even if as a result of the installation your software is reachable via an exposed port. If, for whatever reason, there is an exception, it should be noted.
I did a small amount of research to see whether my expectations are off base. Here's what I found in 5 minutes of research:

The mysql official docker image requires a password setup
So does the postgress official docker image
The official Couchbase container appears to involve a mandatory password setup before use
Redis (which is primarily used for transient data and is probably less often run in a container) comes by default in a passwordless config. The docker page, however, includes a prominent warning:

which is easy to see as it is listed second right after "What is Redis?"
This shows, in my opinion, that if the call is made that software be distributed without a mandatory password setup process, at a minimum, users should be prominently informed about common pitfalls in canonical use. A strong case is also to be made to not allow use of the software until a mandatory setup has been completed.
Lastly, I'd like to add that users of such software as Discourse or Wordpress - which is also distributed in containerized form - have become accustomed to mandatory setup processes before the software can be used.

While a good start, that section is insufficient because it does not address the behavior on -p hostport:containerport. I suggest looking at the Redis documentation for an example to follow.
The pitfall here is not just that you ship with authentication disabled: it's that the common defense mechanism of binding to the loopback interface does not work inside a container. As soon as you create a network path to the container -- which you have to do to be able to use your software at all - you run the risk of exposing the database to the Internet.

Thank you for the additional feedback.
Docker Official Images (DOI) are intended to provide access to a wide variety of software across a wide variety of use cases. The types of DOI, their variants, and configurations are driven by the open source communities that develop and use them. Many DOI, mongo included, are optimized for ease of use in the local development inner loop since this is where most developers first use the images. For use cases such as these, it is entirely appropriate to use the default configuration provided by the mongo DOI.
Your assertion that the content in links you provide is "wrong" is not entirely accurate. The information may be wrong or incomplete for production-ready, publicly accessible use cases, but one should not confuse a "get a container running in five minutes" guide or forum posting helping someone get a port exposed with a guide for running a production instance of a publicly accessible data store.
The DOI READMEs on Docker Hub are not intended to provide exhaustive documentation for running the provided software. In fact, the mongo README already exceeds Docker Hubs character limit for a README, which is why the supported tags section contains a link and not the full list of tags.
I understand your frustration given the experience you detail in the description of this issue. I'll work to revise the Security section to provide a stronger warning.

I really don't understand your hesitancy to explicitly mention (-p) the way the Redis documentation does.
You have changed mongodb's defaults, thus arming what others have called a Docker footgun.

Many DOI, mongo included, are optimized for ease of use in the local development inner loop since this is where most developers first use the images. For use cases such as these, it is entirely appropriate to use the default configuration provided by the mongo DOI.

I would have to ask what you mean by "local development" here. Does "local" imply to you a machine that's not on any network? What about a machine that's on a coffeeshop's local network? I would tend to disagree, and in fact even if this is the primary use case for a DOI (which I find counterintuitive also upon reflection), it's even more reason to warn.
I actually think the problem could be addressed with a slight tweak:

It is highly recommended to set a root user name and password if you plan on exposing your Mongo instance to the internet.

why not

It is highly recommended to set a root user name and password if you plan on exposing your Mongo instance to the Internet, such as by using docker's -p option.

(and yes, -p does not always expose to the (capital I) Internet, but here we're imprecise in a defensible direction.)

The mongo DOI is intended to support a wide variety of use cases, many of which do not use docker run, do not result in exposing a port to the internet, etc. As such, what is defensible and what is not is subjective. What would mentioning -p mean to someone who uses Docker Compose or only runs workloads in Kubernetes? How is a developer running a mongo container in WSL on a private network supposed to interpret a warning about exposing a port to the internet? There are many excellent resources for dockerd, Docker networking, running MongoDB in production, etc. There is no way for a 25,000 character README on Docker Hub to address all the concerns related to these topics.

I think we're disagreeing about the urgency of the issue. I'm a bit surprised that the bad publicity mongodb + docker appears to be getting are of less concern to you than they would be to me if I were in your situation.
(Some of the compromises of course first concerned mongodb in its old configuration, but as evidenced by the sources I included, such as the NewsBlur compromise the compromises continue except now with the dockerized version.)
I'm also perplexed that you mention the limit of the README, given that the current README addressed a variety of topics that are arguably of much less concern.


[Feature request] Support for getting most recent value from a set of keys

We would like to be able to retrieve the most recent setting for a set of keys rather than a single key.
For example, given the following configuration files added in order
config1.json
{
    "FirstSetting" : "First value"
}

config2.json
{
    "SecondSetting": "Second value"
}

Please provide a method like
KeyValuePair<string, string> result = configuration.GetLatest("FirstSetting", "SecondSetting");

where result.Key is "SecondSetting" and result.Value is "Second value"

What's the scenario?

We have two cases where we ran into this, in the first one we had configuration based on a class name with support for either the short or full name. The following two configurations would be equivalent:
{
    "ClassName" : {
       "Property" : "Value"
    }
}

{
    "SomeNamespace.ClassName" : {
       "Property" : "Value"
    }
}

In the other case, we were allowing configuration as either a property value or a key lookup, so the following two configurations would be equivalent:
{
    "MyClass" : {
        "MySetting" : "Some Value"
    }
}

{
    "Data" : {
        "Value" : "Some Value"
    },
    "MyClass" : {
        "MySettingKey" : "Data:Value"
    }
}

Sounds like two different features here.
For getting the hierarchy of things, this seems like a feature that would get very confusing to users. Allowing different formats for keys and expecting them to be coalesced seems very error prone. In my mind the behavior would be that the consumer of these keys has a priority system of perhaps preferring "complex names" to "simple names" and that's that. If the user mixes key formats then too bad.
The second feature is having keys dynamically depend on other keys.

That sounds like an accurate description of the situation and I agree with your assessment on both accounts.
Does this look good to you, @rowanmiller ?

@Eilon This is consistent with how we resolved the issues on our end too.
For context type name as key, we decided that full qualified name always wins over short name. I don't think this is too bad since if you want to guarantee that you're overriding something, just use the full name. I think there can be confusion either way, but we don't want to require full name (as it's yucky to type) and I agree that coalescing them in the config stack is probably a little too magic.
Having the feature for redirecting to another key would be great. We really only use this for connection string at the moment, and there is a well known 'name=xyz' format for connections so we're just going to use that for now... but having something general purpose like this would be great.
//cc @divega @ajcvickers @bricelam @anpete

@rowanmiller cool sounds good. Should we close this issue and file a new issue for the value-redirecting feature? No guarantee it'll happen of course, but even if it doesn't and we end up doing it just for EF for now, we should at least have a quick discussion on what the feature would look like if it was more general purpose.

Opened new issue for value-redirect https://github.com/aspnet/Configuration/issues/129


Add an in the formgroup of portfolio in the setting page called technolo...

gies
Checklist:

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the main branch of freeCodeCamp.
[ ] All the files I changed are in the same world language, for example: only English changes, or only Chinese changes, etc.

Closes #XXXXX

Hi @oussamanidhal
Thanks a lot for taking the time to prepare this pull-request.
We are closing this PR at this time, but we encourage you to create a GitHub issue with some mock screenshots and details of the feature that you are proposing. We can surely discuss this before going into the implementation.
To be fair to all our contributors and respect everyone's time we insist on everyone reading and following contributing guidelines presented in the pull request template earlier.
Thanks and happy coding!

ok sure I will Do


Prototype Implementation - Install CWMS DB and CCP Schema

Prototype Implementation - Install CWMS DB and CCP Schema
Will be used for prototype development and demonstration.

Moving forward with OpenTSDB instead of CCP schema due to issues with getting database export


Merge views

:warning: Work In progress :warning:

I think we should go further here and remove the code folder too - happy to work on this with you if you like

As discussed I'm going to put in a new pr for this, do you want to close this one?


The loss of calibration iteration always equals to zero

Hi guys :),
I am running vai_q_caffe to generate a quantized model by the line "vai_q_caffe quantize -model float.prototxt -weights float.caffemodel". And the command executed successfully without any bugs. However, I noticed that the loss of calibration iteration always equals to zero during the process. Here is an example below. Could anyone give me any clue about this? What should I do to pinpoint the cause of the problem? Many thanks!

I got the same problem .And I got other error when I deploy the prototxt and caffe. That is the same layer name in the prototxt file.Do you have the problem?

"loss" will not be maintained in calibration stage and its value does not affect calibration.
Please check the quantized model accuracy directly and compile the quantized model.

Hi @zxw602
Since we haven't received your reply for a long time, we assume you have solved this issue and I'm going to close it. If you still have any questions, please feel free to reopen it. Thank you very much.


@Value toString pattern

It would really really really be awesome if:
@Value(toString="fib({})={})")
class FibonacciExample {
    int input;
    int result;
}

generated a toString method returning the specified pattern, replacing {} placeholders with field references in declaration order:
public String toString() {
    return "fib(" + input + ")=" + result;
}

Optionally, this can be done as a shortcut to the hypothetical feature in @ToString:
@ToString(pattern="fib({})={})")
class FibonacciExample {
    int input;
    int reasult;
}

This doesn't really feel like a necessary feature. You want a specific way implementation of toString for your class, which isn't really boilerplate.

I feel that I probably misinterpreted the usefulness of this, however, I think some modification to the suggested implementation is required. For example, one might wish to print out one field more than once so, in this case, {input} to print out the value of input
Credit to rzwitserloot for this suggestion.

I really like this idea. It'd have to go on @ToString and not @Value, the rule would be that {fieldName} is a field access, in case of multiple consecutive { or }, only the innermost count (so, {{name}}={age} would end up printing {Joe}=10. We need a way to do lists. How about:
names={names:[A, B]|(empty)}
which means: Print 'names' here, but treat it as iterable, using 'comma+space' as a separator, [ as prefix and ] as postfix (A and B have special meaning, and are always required) and in case of 0 elements, printing the string "(empty)" instead.
The obvious downside is that this turns into its own little language which is normally not a great plan, but, regex is also its own little language and it does allow you to be incredibly expressive. For example, we could add a symbol for using a custom method to render a given string.
That's getting ahead of ourselves; the first version of this would simply allow {} for field names, and will automatically enumerate iterables with the pattern: [A, B]|[].

Field name access as proposed seems a bit verbose to me. If you don't accept my proposal of Logback-style {} references by declaration order, is it possible to have index references? {0} references first field, {1} second and so on? Is that even possible as Java reflection Class#getFields doesn't guarantee the ordering?

Veto on anything where you don't have to name the fields explicitly.
The downsides:

You can't double-visit a field (print it twice). It's probably not needed, but a minor niggle.
Lombok uses a way to get at the fields which preserves order, however, the VAST majority of the time where java field order would come up, it's because Class.get(Declared)Fields() is used, and those methods, as @mbjelac mentioned, do NOT preserve order. That means, in the java community, most people consider fields to be freely re-orderable, and that this won't change anything significant. Whilst lombok uses field order here and there (the arguments of lombok-generated constructors are ordered in the same order as the fields show up, and we calculate hashCode and equals in that order too), any change in order is self-documenting (in the case of the constructors) or shouldn't matter (equals/hashCode; only performance is potentially affected assuming non-broken equals/hashCode impls of members). This would simply silently change behaviour. That's not acceptable. A simple example of where the community tends to assume field order is not important to backwards compatibility: A LOT of code auto-formatters will freely re-order fields to be in static-> non-static order, and within a category, alphabetized.

I understand. Explicit names then. Any field name errors will show up at compile so that's good (better than at runtime, anyway).

Caught in umbrella #1297.


Animating both position and rotation on a AnimatableBody3D doesn't work

Godot version
4.0.2 Stable
System information
Windows 10, AMD Ryzen 7 3700X 8-Core Processor 3.60 GHz
Issue description
I was trying to make a moving platform that also rotates, but only one of the rotation or position animation properties change at a time. It works when previewing the animation in the editor, though.
Steps to reproduce
1.) Download sample project
2.) Play the animation in the editor
3.) Click play and watch as the animation isn't the same.
Minimal reproduction project
platform_animation_bug.zip

AnimatableBody2D also has the same issue. They have the same reason as #75487. When sync_to_physics is enabled, setting position/rotation/scale/skew/transform/global_transform will all cause a NOTIFICATION_LOCAL_TRANSFORM_CHANGED notification to be sent. This causes the actual global_transform to be overwritten with the previous global_transform.
https://github.com/godotengine/godot/blob/db1302637023168f7becceb1c4ce13228e1b2a43/scene/3d/physics_body_3d.cpp#L352-L363
Line 356 causes the last global_transform to be used during a frame.
In this case, it may be better to merge multiple tracks into a single transform property track to reduce the number of times NOTIFICATION_LOCAL_TRANSFORM_CHANGED is sent.

RemoteTransform2D/RemoteTransform3D is suitable for combining multiple actions for setting transform components (position/rotation/scale) into one action for setting transform.

For RemoteTransform2D, preparation has been done in #75487.
For RemoteTransform3D, we should first expose the method of Transform3D to modify each component separately, and then merge the components into one Transform3D in RemoteTransform3D::_update_remote().


Fix readme image link

Hi there, I wanted to make a hacktoberfest contribution by resolving #44

I am going to close this PR as it was for Hacktoberfest which I have completed now and it looks like this project is not actively being maintained. Thanks anyway.


Simplify description of version to use to get GitHub dependency graph integration

Submitted via Learn Editor.

We updated the vcpkg-tool binary to fix identified bugs with the GitHub dependency graph feature (see https://github.com/microsoft/vcpkg/commit/56954f1db97f38635782d5ad7cdfd45d2731c854), and we plan to continue fixing more over the next couple of months. This change makes it so that we don't have to continually update this docs with the most recent version with fixes.


feat: add Subtitle Support to MetadataCardContent Component

Description
In this PR, I have added support for a new subheading property in the MetadataCardContent component to accommodate flex design requirements.
Testing
Navigate to MetadataCardContent component and verify that it includes a subheading below the title.

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/Lightning-UI-Components/490/rdkcentral/Lightning-UI-Components

Commit: 5aa4a5ee5744275a26cb8ae9914b0c8fd8290b6a

Report detail: gist

Test Execution Failed.

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/Lightning-UI-Components/490/rdkcentral/Lightning-UI-Components

Commit: 1bfdf836fc23a86e3603fbcb05edb33bd508503a

Report detail: gist

Test Execution Failed.

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/Lightning-UI-Components/490/rdkcentral/Lightning-UI-Components

Commit: 1bfdf836fc23a86e3603fbcb05edb33bd508503a

Report detail: gist

WARNING: A Blackduck scan failure has been waived
A prior failure has been upvoted

Upvote reason: Code match is OK

Commit: 1bfdf836fc23a86e3603fbcb05edb33bd508503a

Test Execution Failed.

Test Execution Failed.

Test Execution Failed.

Test Execution Failed.

Test Execution Passed.

Test Execution Passed.

Test Execution Passed.

Test Execution Passed.

Test Execution Passed.

:tada: This PR is included in version @lightningjs/ui-components-v2.21.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add module XML-namespace declaration support to the parser

Description:
Refer: https://ballerina.io/spec/lang/2020R1/#section_8.8

Added with #22805


zsh doesn't work as the shell in EMR documentation

Alluxio EE documentation for 2.1.0 on EMR should specify that should be using /bin/bash terminal when running aws emr create statement. iTerm by default uses zsh which doesn't take in URLs accurately.
zsh: no matches found: Path=s3://alluxio-public/emr/2.1.0/alluxio-emr.sh,Args=[s3://madans3bucket/emr/mount/]

In light of preserving simplicity across most systems - I've added a note that the command is designed for bash.
Most people who use zsh are using it by choice. MacOS has recently started defaulting the shell to zsh when upgrading to MacOS Catalina, but I don't think the user base is large enough to justify having a second command.
If you don't think this fix is enough, we can try to spend some more effort to design a command compatible with both interpreters.


Added main html landing page

Created main landing page HTML, and styling for it.
Still some tweaking left to do, no javascript done

impressive work


Ported Chiya from discord-interactions to pycord

This pull request ports Chiya from discord-interactions to pycord.
Files rewritten:
Apps

[x] Move Question
[x] Report Message

Commands

[ ] Administration
[x] Ban
[x] General
[x] Kick
[x] Mute
[x] Note
[x] Purge
[x] Reminder
[x] Server
[x] Ticket
[x] Warn

Listeners

[ ] Automod
[x] Autoresponder
[x] Ban
[x] Boost

Tasks

[x] Reddit
[x] Reminder

Changes tested to be working:
Apps

[x] Move Question
[x] Report Message

Commands

[ ] Administration
[x] Ban
[x] General
[x] Kick
[x] Mute
[x] Note
[x] Purge
[x] Reminder
[x] Server
[x] Ticket
[ ] Warn

Listeners

[ ] Automod
[ ] Autoresponder
[ ] Ban
[ ] Boost

Tasks

[ ] Reddit
[ ] Reminder

Updated the PR OP to no longer include now removed files.


Change wasmless transfer cost to 250 million gas units

set wasmless_transfer_cost in chainspec to .25 CSPR for production release
this is mitigation against ping pong behavior witnessed in testnet

@mpapierski please turn this around when you wake up tomorrow

@mpapierski this will have to reverted


Ember-client failing without a Content-Length

As reported by @rintcius:

Requests without content length confuse ember. This looks like the request counterpart of https://github.com/http4s/http4s/pull/5881

I wonder if this is related to https://github.com/http4s/http4s/issues/5256.


fesetround is not part of the C++ std library

fesetround() is not part of the C++ std library. It is defined in the fenv.h header in the POSIX standard.
Addresses #7289

i signed the Google CLA

@carlorosati Since C++11 it is defined in the std namespace via the header .
http://en.cppreference.com/w/cpp/numeric/fenv/feround
Can we change the code to use that header instead and get rid of the direct references to
STDC_IEC_559? If not, I'm OK with your change.

@rmlarsen Do you want me to remove the preprocessor statements? Do you know why they were needed?

Hm, ScopedSetRound looks a bit broken in general. It doesn't reset the rounding mode as stated in the header. This doesn't doesn't matter at the moment, but I'll fix and test it internally and push to github. Thanks for making me aware of this.

@rmlarsen Be sure to close out #7289 with your commits.

@carlorosati will do, thanks. The change is running through automated testing. Should be pushed tomorrow or the day after.


Italian mobile phone

Hello,
i wanted to know if it is possible to add zero=>false option on the match_split function.
Mobile phone does not have 0 when displaying in national format.
Phony.format('393885641630', :format => :national) => "0388 564 1630" but it think that it should display "388 564 1630"
Thank you

Hi @pascalineJulien ! Sorry for the late answer 😓 Thanks for the issue – can you explain why it should be<PHONE_NUMBER>?

Hi Florian,
sorry too for late reply, it was one of my Italian customer who fire it out
to me.  He said that there is no more leading "0".
More over Wikidepia seems to say same thing
Mobile numbers prefix shortening[edit
<https://en.wikipedia.org/w/index.php?title=Telephone_numbers_in_Italy&action=edit&section=10>
]

Until 2001 a leading "0" was part of any mobile phone number, but it has
been removed.[5]
<https://en.wikipedia.org/wiki/Telephone_numbers_in_Italy#cite_note-5>

https://en.wikipedia.org/wiki/Telephone_numbers_in_Italy#Trunk_code_removal
2016-09-14 20:16 GMT+02:00 Florian R. Hanke<EMAIL_ADDRESS>
Hi @pascalineJulien https://github.com/pascalineJulien ! Sorry for the
late answer 😓 Thanks for the issue – can you explain why it should be 388
564 1630?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/floere/phony/issues/330#issuecomment-247106697, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADLHNiaPzg_hVNBDcD9ThrENUh63ZTwFks5qqDn8gaJpZM4JZffI
.

@pascalineJulien What version are you using? Since ruby -e 'require "phony"; p Phony.format("393885641630", :format => :national)' results in "388 564 1630". So, probably it has already been improved by a user 😊

Ping @pascalineJulien ❓

Hi Flore
Of course i had an outdated version. My phony-rails is 0.9.1. But when i use to compare the lib files for italian country i have not seen any diff. I will try to update the gem and come to you again if the pbl still there. You can close the flow.
Have a Nice day and thank you again

Le 10 nov. 2016 à 13:50, Florian R. Hanke<EMAIL_ADDRESS>a écrit :
Ping @pascalineJulien ❓
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@pascalineJulien Hi! It may be that the Phony core was changed, so that the Italian case may have been fixed (probably intentionally, since tests needed to be changed). Ok, thanks for your response, I'll close 😊 Have a nice day too! 🚀


A very serious bug.

Use simpleConnect() function to create a TCP connection.

Thank you very much! I will update the version as soon as I can.