PHP-CS-Fixer Error: Error: Could not find 'php-cs-fixer'. The program may not be installed.

Description
The results of beautification are not what I expect.
Expected Results
The beautified code should have looked like:
<INSERT CODE HERE>

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/fe8188e9aecd79601afea771e2803ede
Checklist

[x] I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] I have reloaded (or restarted) Atom to ensure it is not a caching issue
[ ] Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Generated debugging information and added link for debug.md Gist to this issue

Since I came from other editors I'm new from Atom. And I can't seem to fix this error, Can anyone please help me? I'm a newbie when it comes to these type of things.

Since I came from other editors, I'm kind of new with Atom. Can anyone help me with this please?

Atom-Beautify uses PHP-CS-Fixer for beautifying PHP. There are a number of related issues: https://github.com/Glavin001/atom-beautify/search?q=Error%3A+Could+not+find+'php-cs-fixer'.+The+program+may+not+be+installed.&type=Issues&utf8=✓
I think a good one may be: https://github.com/Glavin001/atom-beautify/issues/394#issuecomment-111220120
See https://github.com/FriendsOfPHP/PHP-CS-Fixer for their installation instructions.

I really want to focus on improving the installation experience for users. I have created a new Issue, #1687, to target this problem. Please provide your feedback! Thanks in advance.

Still having issue...uninstall atom-beautify...but no luck.  Not able to beautify php.

If you've installed php-cs-fixer, make sure you set the path to it in atom beautify.  Open Atom Beautify's settings and expand "Executables".  Under that, expand "PHP-CS-Fixer" and set the path to it.


Indexed peripherals

Some peripherals in the idf are indexed, i.e there are two identical I2C peripherals on the esp32, instead of creating register definitions for both, they are defined once with offset.
This generator doesn't properly handle this at the moment, and only creates one peripheral.

The current approach simply inserts a generic blank peripheral at the start, see https://github.com/MabezDev/idf2svd/blob/c433ffab105c607bd4f868765c9f2967eba09a0a/src/lib.rs#L161 . This will require some post processing of the svd to copy and give them the correct base address

Hi, The I2S peripheral is also indexed and should probably be added to the list. The latest esp32 PAC only shows I2S0 as I2S.

Hi @sepotvin, I forgot about this repo. There are now official SVD's in the https://github.com/espressif/svd repo. Please file the issues there.


添加trapezoid-api文档

#373

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

该 API 提案已通过，如果有需要完善的地方，请在原提案上继续修改。


Code examples for using TFRecorder TFRecords in a tf.data.Dataset

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
As a user I would like to see an example of how to read the output of TFRecorder in as a tf.data.Dataset.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi @mbernico !, regarding the code examples in Jupyter Notebook documentation. A nice to have feature would be the ability to open them in a colab environment.  Maybe adding a Badge like this   .
thoughts? :)

Hey jmarrietar, yeah, I think this makes a lot of sense. Would you mind adding it as a separate issue?  Also if you wanted to pull request it we'd love that too, if not we can for sure get to it.
Lastly, would you mind taking a look at the flexible schema PR #20 I think it's useful, but it does make the codebase more complicated so I'd love some feedback before we merge it.

Hey jmarrietar, yeah, I think this makes a lot of sense. Would you mind adding it as a separate issue? Also if you wanted to pull request it we'd love that too, if not we can for sure get to it.
Lastly, would you mind taking a look at the flexible schema PR #20 I think it's useful, but it does make the codebase more complicated so I'd love some feedback before we merge it.

Just created Issue https://github.com/google/tensorflow-recorder/issues/27  as a separated one. I didn't Assign it to me just yet since I might be short of time right now. But would like to take it soon.

Ok, cool, I put it in my name but feel free to take it on :)


Feat/custom separator

This PR contains:

Changes to allow customising the decimal and group separator.
Tidied up the utils functions

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta@1d9f8b3). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             beta       #56   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?        10
  Lines           ?       128
  Branches        ?        33
========================================
  Hits            ?       128
  Misses          ?         0
  Partials        ?         0

Continue to review full report at Codecov.

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


Add cosine sources to MSL

Reported by christiankral on 14 May 2013 12:50 UTC
For particular applications it is advantageous to have sine and cosine source which shall also be clearly indicated by model symbols. In particular for quasi stationary electrical (and magnetic) models cosine sources are required for appropriate comparison with time domain models. In order to avoid errors in adding pi/2 to the phase angle of sinus sources, cosine source are introduced in the MSL. A proper graphical representation of icons will be included.
The changes introduce the new following models:

Modelica.Blocks.Sources.Cosine
Modelica.Electrical.Analog.Sources.CosineVoltage
Modelica.Electrical.Analog.Sources.CosineCurrent
Modelica.Electrical.MultiPhase.Sources.CosineVoltage
Modelica.Electrical.MultiPhase.Sources.CosineCurrent

Migrated-From: https://trac.modelica.org/Modelica/ticket/1098

Comment by christiankral on 14 May 2013 13:10 UTC
Cosine blocks and voltage and current sources are included by d9581bb75591f1e0fb823d00f32cde957eaac70c.

Modified by dietmarw on 18 Jul 2013 11:27 UTC


Extend chart docs

I feel like the helm-chart could benefit from some extra documentation.
For example:

How to use the schema.json. (e.g. VSCode plugin example)
When to use the busybox permission fix init container or not.
Some deployment examples.

Second this, an example with postgres would be awesome.

I'll try to draft up a PR over the weekend @hari-ara .


Upgrade typescript eslint to fix eslint conflicts

Description
See here: https://github.com/typescript-eslint/typescript-eslint/issues/3738
Motivation
Newer version of eslint, upgrade suggested by dependabot, has conflicts with old version of typescript/eslint, thus the affected packages have been manually updated
Fixes:

packages.json
packages-lock.json

Tests included/Docs Updated?

[ ] Included for each change/fix?
[ ] Passing? (Merge will not be approved unless this is checked)
[ ] Docs updated?
[ ] New packages used/requires npm install?
[ ] Toggle added for new features?

Hey @minottic I see you tried to upgrade some dependencies and probably fix some errors in the actions. I have done this already here https://github.com/SciCatProject/scicat-backend-next/pull/178 in one of my PRs. I fixed the unit tests as well and it mainly fixes Raw dataset datablocks API tests. Would be nice if you could look into that and give a feedback.

yes, I saw that (after I opened this one actually), but since it was a draft I thought it would be good to have this one ready, since it broke the build. But as I understand now, #178 is ready to be reviewed, correct?

yes, I saw that (after I opened this one actually), but since it was a draft I thought it would be good to have this one ready, since it broke the build. But as I understand now, #178 is ready to be reviewed, correct?

Yes #178 is ready to be reviewed.

closed by #178


Passing "--project-cache-dir" causing included build to be always out-of-date

Expected Behavior
When I run the same Gradle build twice in a row, as many tasks as possible in the second build should be UP-TO-DATE.
Current Behavior
Currently, when I ./gradlew --project-cache-dir gradle-project-cache :included:compileJava --info twice in a row in the linked project, the task executes both times.
Context
This slows builds down slightly in AndroidX. In practice, this causes :doclava:compileJava to rerun whenever building documentation
Steps to Reproduce
See reproduction project at https://github.com/mathjeff/gradle-samples/tree/master/included-build-project-cache-dir
Your Environment
Build scan URL: https://gradle.com/s/f2p54eu5bbpo4
Thanks!

I'm pretty sure that the root cause is that we overwrite the executionHistory cache for each included build (including buildSrc). If we add some sources to the buildSrc then the error becomes clearer. In the second run, when we expect everything to be up-to-date we'll get:
Task ':buildSrc:compileJava' is not up-to-date because:
  Output property 'destinationDirectory' file <snip>/gradle-samples/included-build-project-cache-dir/included/build/classes/java/main has been removed.
  Output property 'options.generatedSourceOutputDirectory' file <snip>/gradle-samples/included-build-project-cache-dir/included/build/generated/sources/annotationProcessor/java/main has been removed.
  Output property 'options.headerOutputDirectory' file <snip>/gradle-samples/included-build-project-cache-dir/included/build/generated/sources/headers/java/main has been removed.

Note that these logs reference outputs of the :includedBuild:compileJava. And then:
Task ':included:compileJava' is not up-to-date because:
  Output property 'destinationDirectory' file <snip>/gradle-samples/included-build-project-cache-dir/buildSrc/build/classes/java/main has been removed.
  Output property 'destinationDirectory' file <snip>/gradle-samples/included-build-project-cache-dir/buildSrc/build/classes/java/main/Bar.class has been removed.
  Output property 'options.generatedSourceOutputDirectory' file <snip>/gradle-samples/included-build-project-cache-dir/buildSrc/build/generated/sources/annotationProcessor/java/main has been removed.

Now the outputs of :buildSrc:compileJava are referenced instead.

Hi @mathjeff! Can you please describe your use case is for --project-cache-dir (as opposed to relying on the default cache directory location)?


SearchTx timeouts

I'm trying to search a CreateValidator Tx
With the current code, the HTTP request always timeout or get socket hang up
        let client = await StargateClient.connect("https://rpc-juno.mib.tech")

        let txs = await client.searchTx({
            tags: [{ key: "create_validator.validator", value: "junovaloper1hvhyunq7qvykzvrcnhjj4xnkcla58xusk6r60g" }],
        });

errors
cloudflare proxy
(node:11661) UnhandledPromiseRejectionWarning: Error: Request failed with status code 502

direct tcp
(node:11835) UnhandledPromiseRejectionWarning: Error: socket hang up

Using Juno CLI to query instead is always almost instant
 junod q txs --events create_validator.validator=junovaloper1hvhyunq7qvykzvrcnhjj4xnkcla58xusk6r60g
that made me wonder why, so I did some logs and I notice some differences between the RPC call made by cosmjs and the one made from CLI
CosmJS:
{
  jsonrpc: '2.0',
  id:<PHONE_NUMBER>33,
  method: 'tx_search',
  params: {
    query: "create_validator.validator='junovaloper1hvhyunq7qvykzvrcnhjj4xnkcla58xusk6r60g' AND tx.height>=0 AND tx.height<=9007199254740991",
    page: '1'
  }
}

CLI:
{
  jsonrpc: '2.0',
  id: 0,
  method: 'tx_search',
  params: {
    order_by: '',
    page: '1',
    per_page: '30',
    prove: true,
    query: "create_validator.validator='junovaloper1hvhyunq7qvykzvrcnhjj4xnkcla58xusk6r60g'"
  }
}

The default value for max tx.height is too high! By manually setting it in fact the 502 error is gone
       let client = await StargateClient.connect("https://rpc-juno.mib.tech")

        let txs = await client.searchTx({
            tags: [{ key: "create_validator.validator", value: "junovaloper1hvhyunq7qvykzvrcnhjj4xnkcla58xusk6r60g" }],
        }, { maxHeight: 8027955})

        // all good

I think we should entirely remove height filters if not specified

Additional note, this example code is super quick (<100 ms per query)

let response = await axios.post("https://rpc-juno.mib.tech/", {
            jsonrpc: "2.0",
            id: 0,
            method: 'tx_search',
            params: {
                query: `create_validator.validator='${val.operator_address}'`,
                page: "1"
            }
        })
        ```

Thank you for debugging this. This sounds like a Tendermint bug to me then. Why should an additional numeric filter cause such a behaviour?

Thank you for debugging this. This sounds like a Tendermint bug to me then. Why should an additional numeric filter cause such a behaviour?

that's a good question, I'll try to dig more into this

I think the current abstraction level of searchTx is unsustainable anyways. I am considering to replace it with a much lower level version that avoids this sort of magic.


updated virtuoso.sh with explicit configfile

updated virtuoso.sh with explicit configfile

Hi, it would be helpful to be able to manage the configuration file from a volume

Hi @seralf ,
Thank you for your PR, but I'm afraid currently I can't merge it for two reasons:

you removed the exec virtuoso-t which means the main process of the container is no longer virtuoso,  this means the virtuoso process is not notified when it is stopped.
changing the location of the config file does not affect the use of volume for the configuration file. You can already do that using the current location, without breaking backwards compatibility using the following command

docker run --name my-virtuoso \
    -p 8890:8890 -p 1111:1111 \
    -e DBA_PASSWORD=myDbaPassword \
    -e SPARQL_UPDATE=true \
    -e DEFAULT_GRAPH=http://www.example.com/my-graph \
    -v /my/path/to/the/virtuoso/db:/data \ # using just this mount means the config is available in /my/path/to/the/virtuoso/db/virtuoso.ini
    -v configvolume:/data/virtuoso.ini
    -d tenforce/virtuoso

thanks for the suggestion!
Il giorno lun 5 nov 2018 alle ore 14:08 Niels V<EMAIL_ADDRESS>ha scritto:

Hi @seralf https://github.com/seralf ,
Thank you for your PR, but I'm afraid currently I can't merge it for two
reasons:

you removed the exec virtuoso-t which means the main process of the
container is no longer virtuoso, this means the virtuoso process is not
notified when it is stopped.
changing the location of the config file does not affect the use of
volume for the configuration file. You can already do that using the
current location, without breaking backwards compatibility using the
following command

docker run --name my-virtuoso
-p 8890:8890 -p 1111:1111
-e DBA_PASSWORD=myDbaPassword
-e SPARQL_UPDATE=true
-e DEFAULT_GRAPH=http://www.example.com/my-graph
-v /my/path/to/the/virtuoso/db:/data \ # using just this mount means the config is available in /my/path/to/the/virtuoso/db/virtuoso.ini
-v configvolume:/data/virtuoso.ini
-d tenforce/virtuoso
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tenforce/docker-virtuoso/pull/23#issuecomment-435867672,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFYfFG1chgK6fkRvHcmlvSC4vNZ7Z25ks5usDhIgaJpZM4X8Bgm
.


Update introduction.mdx

Description
The if else example was syntactically correct, but had a semantic issue of not using the condition variable. Could lead to confusion if you are a newbie.

Yeah sorry, forgot I had it forked for the change


Docs: add a message to mention the verbose option

Maybe this should go in with the other doc changes I was thinking of doing but yeah.

Coverage remained the same at 99.28% when pulling 65aa31ea851497465e26f19859d5f9dbeb652b1d on hzoo:patch-5 into 3f92418fa3af89dba132c45d9ca73dd035043f99 on jscs-dev:master.


Add GitHub CLI

Tool information

Tool name: gh
Tool license: MIT
Add or update? Add
Desired version: 0.7.0
URL for tool's homepage: https://github.com/cli/cli

Area for Triage:
Packages
Question, Bug, or Feature?:
Feature
Virtual environments affected

[x] macOS 10.15
[x] Ubuntu 16.04 LTS
[x] Ubuntu 18.04 LTS
[x] Windows Server 2016 R2
[x] Windows Server 2019

Can this tool be installed during the build?
Yes
Tool installation time in runtime
I hope it's fast :)
Are you willing to submit a PR?
Potentially

Hi @alvarosanchez! This tool can be easily installed in runtime by following steps:
### Ubuntu
wget https://github.com/cli/cli/releases/download/v0.7.0/gh_0.7.0_linux_amd64.deb
sudo dpkg -i ./gh_0.7.0_linux_amd64.deb

### Macos
brew install github/gh/gh

### Windows
choco install gh

It take approximately 20 seconds on each OS.
@alepauly What do you think? Perhaps we can add gh to the images as a potential replacement to the hub?

Hi @vmapetr, thanks for the feedback. I know how to install it. The point of this issue is to have it preinstalled, though.

I think it is not big deal to have both hub and gh on images.
They are compatible and looks like functionality is a bit different: https://github.com/cli/cli/blob/master/docs/gh-vs-hub.md

PR has been merged. The changes will be delivered to the production on next deploy


CGIF: init at 0.3.1

Needed for GIF saving support to libvips.
Description of changes
Add CGIF a new package https://github.com/dloebl/cgif
CGIF is an optional dependency of libvips
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Handled by #243024.


Module not found after upgrading Webpack from 4.33.0 to 4.35.0

Hi, Getting an error that
node_modules/@salesforce/design-system-react/module/components/trial-bar
can't resolve '../../../components/menu-dropdown/button-trigger'
and
can't resolve '../../../components/button'
after bumping Webpack from 4.33.0 to 4.35.0.
Probably because both button/index.jsx and button-trigger/index.jsx are jsx files instead of js files?

Please see #2113. Use 0.10.7 and we hope it doesn’t happen again with #2115


Share to Linkedin not working (desktop)

Hi, I'm currently using your component and it works very nice, but some months ago the Linkedin option is not working, it just says: Something went wrong. Refresh the page, I have everything configured well as the docs say.
I have been looking for andI found that the sharing url that you open is in the following format:
https://www.linkedin.com/shareArticle?url={url}&title={title}&summary={text}&source={provider}
But the 2020 way to directly open a sharing window is:
https://www.linkedin.com/sharing/share-offsite/?url={url}
Can you please solve the issue? Or do you want me to do a PR?

You can override default link see docs -> https://github.com/nicolasbeauvais/vue-social-sharing#extending-the-network-list

This is still an issue!

I see you have merged some changes. Are they now in the npm package?

Thanks, I'll update it to check.

Hello @nicolasbeauvais, I am still facing the issue on linkedin. I have also tried to overwrite it like you mentioned above but no success. I am using latest version 3.0.9
Any pointers?

Same here, LinkedIn is no longer working, even overwritting the links as you suggest.

Hello would it be possible to add :
linkedin: 'https://www.linkedin.com/sharing/share-offsite/?url=@u',
In the src/networks.js file on the version 4-alpha ?
Thanks in advance


Cache clients and sessions

This PR introduces a cache of sessions and clients (indexed by role and region) which are accessed by relevant goroutines when fetching data from the AWS API. Since, all AWS SDK clients are able to be accessed concurrently, this is a safe way to reduce calls to AWS (and rate-limiting) in situations where very few roles are used.
At this worst case, this could introduce a degradation in memory performance for configurations which use a lot of roles per job.
The SessionCache can be accessed in a lock-free manner, by safely calling Refresh() before making any calls or spinning off goroutines and then calling Clear() after all goroutines have finished to reset the credentials.
In particular, we currently have a very large autogenerated YACE config file which only has one role (by very large, it is about 10,000 lines). Prior to introducing the cache, we would call the AWS EC2 metadata API over 300 times per scrape to fetch credentials for subsequent data pulls. Due to this, YACE calls would be tarpitted, and time out when trying to access the API, and then run into nil pointer errors for account ids and other issues.
The cache reduces the number of EC2 metadata calls per scrape down to 1.

This also includes the fixes in https://github.com/ivx/yet-another-cloudwatch-exporter/pull/414 as these were necessary to understand the problem // are good fixes in general.

Ah, and it includes the function movements made by https://github.com/ivx/yet-another-cloudwatch-exporter/pull/418 to move session logic into one file for consolidation.

Hey @jandersen-plaid,
could you please rebase this? :) Would merge it then!
Thanks a lot!

Hey @jandersen-plaid,
could you please rebase this? :) Would merge it then!
Thanks a lot!

Alright, everything should be up to date now! Let me know if things need any further adjustment.
There are some small changes as well: I added a short circuit for creating sessions, in the case that a role is only used within static jobs (and therefore would only need a cloudwatch client).

Thanks a lot for the fast rebase!
Decided to release without this merge as it is already more packed then I wish.
Plan is to put this into 0.31.0 this week.

Thanks a lot for the fast rebase!
Decided to release without this merge as it is already more packed then I wish.
Plan is to put this into 0.31.0 this week.

No problem, and for sure! That makes total sense. I actually planned to add some tests to this later today, so it looks like the delay played out in my favor!

Awesome I plan to merge and release this on Thuersday.
The code is from your side ready now? :)

Awesome, and yep! Ready to go. I think I can actually close https://github.com/nerdswords/yet-another-cloudwatch-exporter/pull/414 and just leave this one open since this PR is a superset of the the other PR.


Export JSON as a list of objects

First of all thanks for your wonderful project! 🎉
Current JSON layout (column-oriented) isn't really easy to consume. I propose we flip it like this:
{
  "files": [
    {
      "Filename": "pycobertura/__init__.py",
      "Stmts": 2,
      "Miss": 0 ,
      "Cover": "100.00%",
      "Missing": ""
    },
    // ...
  ]
}

As a sidenote, I'd also like to shout out an excellent library called tablib, which supports a ton of formats out of the box and would probably be easier to use than maintaining a lot of different formatters by hand.

P. S. same applies to Yaml, of course.

@notpushkin @aconrad
I think the format is totally feasible, with regards to the library I do not have yet an opinion on it, as I do not know it. Generally, from a maintenance perspective I think in-built solutions and as less external packages as possible is optimal, so maybe in future a decision between tabulate and tablib would have to be taken.
Regarding implementation: I am currently still looking at the pytest coverage issue, which is a release-blocker for Version 3.0 and the solution could be to switch to unittest, so that is maybe just a caveat that it might be good to come up with something small first :)

@notpushkin How do you get along with this PR? It seems the changes the resolution of the pytest coverage issue brings will be minor, if this time I really have found the solution. For more info please look at: #140.

I'm marking this issue for milestone 3.0 since it would be a breaking change.

pycobertura-3.0.0 was released, I hope this release addresses this issue. Please reopen if not.


Adapt identity initializer API to other initializers.

This API extension is completely backwards compatible and supports consistency.
All initializer classes (such as ZerosInitializer) have the same API and can either be accessed via the initializer namespace, from Keras initializers or directly from the tensorflow import:
>>> tf.initializers.zeros
<class 'tensorflow.python.ops.init_ops.Zeros'>
>>> tf.keras.initializers.Zeros
<class 'tensorflow.python.ops.init_ops.Zeros'>
>>> tf.zeros_initializer
<class 'tensorflow.python.ops.init_ops.Zeros'>

The IdentityInitializer class, which was added in d5f1790530db0ee430d223497a59cfc26ab5f4d8, had been missing the last of those options. This is why the following way of access was added to its API:
>>> tf.identity_initializer
<class 'tensorflow.python.ops.init_ops.Identity'>

Can one of the admins verify this patch?

The initializers namespace is preferred, and we are trying to avoid adding new symbols to the top-level tf module.
Eventually (probably with 2.0), tf.initializer will be deprecated in favor of tf.initializers..
The inconsistency is ugly, but if you switch to using tf.initializers, you don't ever have to see it.


feat(kai): port device invitations from halo

also includes:

fix for sidebar not closing
adding dynamic config and configuring dev to not be persistant

Current dependencies on/for this PR:

main

PR #2264   👈

This comment was auto-generated by Graphite.


Travis install command not updated for Cordova 5.x yet

Found out you guys updated the gulp cordova-install command to use cordova prepare, but the Travis install command hasn't been updated yet. This one specifically.

You are absolutely right. Thanks!


Reports "Build complete with errors" even when no errors occured

Logic error in Sysbuild_Main - should compare to zero, not nil (!= vs 'unless').

Rel as 1.0.7


Fix android SA_* constants

Trying to crosscompile wait-timeout to armv7-linux-androideabi I found that SA_* had different types in libc, but they have to be the same because they are used in bitwise operations.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR! Unfortunately this'll be a breaking change to libc so we'll have to hold off on this for now, but otherwise we can be sure to merge on the next bump!

@alexcrichton if you have time, could you add a label for all these fixes-that-are-breaking PRs? :-)

Sure yeah

@alexcrichton It this really a breaking change? Can we consider it a bug fix instead? Some others PR with type changes was included in 0.2.x releases, for example https://github.com/rust-lang/libc/pull/516, https://github.com/rust-lang/libc/pull/523, https://github.com/rust-lang/libc/pull/533.

@malbarbo I think #489 didn't have any deletions, so was that a mistake? All the others I believe the breakage was contained to Solaris, a tier 3 platform. Android, however, is tier 2 :(

@alexcrichton  #489 was my bad. Thank you for the clarifications.

:umbrella: The latest upstream changes (presumably #538) made this pull request unmergeable. Please resolve the merge conflicts.

So I just looked at sigaction from the android-24 platform in the NDK, and it seems to me that this PR is wrong. In the NDK, both arch-arm and arch-arm64 have sa_flag from sigaction set to unsigned long. You can see for yourself :

https://android.googlesource.com/toolchain/prebuilts/ndk/r13/+/master/platforms/android-24/arch-arm/usr/include/asm/signal.h#97
https://android.googlesource.com/toolchain/prebuilts/ndk/r13/+/master/platforms/android-24/arch-arm64/usr/include/asm-generic/signal.h#101

So, as far as I'm aware, this should really be defined as c_ulong directly under android/. Am I missing something ?

@malbarbo can you rebase this ?
We can give this a try to see if anybody is affected by these changes, and if they aren't then just do them.

Done.

@bors: r+

:pushpin: Commit e2bbeeded77811298047739ac6d6b361176f669b has been approved by gnzlbg

:hourglass: Testing commit e2bbeeded77811298047739ac6d6b361176f669b with merge 0f395c6333aab3a7b707a8ee195bc9a0a7a73a43...

:sunny: Test successful - checks-cirrus, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing 0f395c6333aab3a7b707a8ee195bc9a0a7a73a43 to master...


Configurable openstack subnet cidr defaulting to the previous 10.0.0.…

…0/24 behavior.  Add the subnet_cidr as a required argument to the network module.

Good to merge, @drekle?

Good to merge


[SFC Playground Feature request]: Support auto format on save

What problem does this feature solve?
I really like to use the sfc playground to show some vue demo. Does it support auto format on save?
What does the proposed API look like?
Support auto format on save

The official playground is not supported, but you can try Element Plus playground. Try Ctrl / ⌥ + Shift + F.


--load-extension=spatialite shortcut

I added this to sqlite-utils in https://github.com/simonw/sqlite-utils/issues/136 and I really like it: pass a special value of spatialite and Datasette should attempt to load it from known likely installation locations.

Documentation: https://docs.datasette.io/en/latest/spatialite.html


Added DryIoc adapter to readme

DryIoc adapter. It passes DI.Spec.Tests.

Hi @dadhi, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

And more nice stuff, thanks!


[Bug] Invalid lane connections by stay-in-lane

Describe the problem
Bottom road: 3 lane 1 way from Network Extensions, upwards
Left road: tiny 2 lane street from Network Extensions, leftwards
Right and upper road: tiny 1 lane street from Network Extensions, upwards
In the screensot, lanes crisscross, despite pop-up hint promising it will not happen.
Steps to reproduce

Place roads as in the description
Activate TM:PE → Lane Connector
Select intersection
Press CTRL+S

Log files
Not  an exception, not required
Savegame?
Not required
Screenshots?

Notes or questions?
The stay in lane system should be enhanced, so any road combination works:

If user clicks on a segment then it is set as main road
Else largest road is set as the main road.
Other roads are read from the furthest lane
For each lane from far side of main road, there will be assigned a lane, counting from far side of other roads.

Yeah, something is wrong. I even changes outgoing road types to highway one lane and still the same weird result
@kianzarrin any ideas what is wrong here?

@kianzarrin @krzychu124 When it will be fixed?

the math is heavy and fixing this is not that important.

This won't fix problem above, however...
NExt2 roads have some weird bugs in them. You could get faster load and less lag + bugs in game by replacing NExt2 mod-based roasd with a pack of asset-based NExt2 roads that look and work the same. See RON workshop page for details.


Allow INCONSISTENT_RHCOS_RPMS in stream

In e.g. this build-sync job,
there was no attempt to produce a nightly, because RHCOS had different
rpm contents between the different arches:
- code: INCONSISTENT_RHCOS_RPMS
  msg: 'Found RHCOS inconsistencies in builds {False: [RHCOSBuild:x86_64:410.84.202201210604-0, RHCOSBuild:ppc64le:410.84.202201201604-0, RHCOSBuild:s390x:410.84.202201201602-0, RHCOSBuild:aarch64:410.84.202201210203-0], True: []}: {''ignition'': {''ignition-2.13.0-2.rhaos4.10.el8'', ''ignition-2.12.0-3.rhaos4.10.el8''}}'
  permitted: false

This is a situation that should be allowed as a stream assembly, as
rhcos can be produced with some delay, while it obviously should be
flagged down when creating a named assembly.

Consensus is that this is a liberty we should not take.
/close


Backward Compatiblity with application key

The Version 1.8 Supports application key
function MobileServiceClient(applicationUrl, applicationKey) {
		    /// <summary>
		    /// Initializes a new instance of the MobileServiceClient class.
		    /// </summary>
		    /// <param name="applicationUrl" type="string" mayBeNull="false">
		    /// The URL to the Mobile Services application.
		    /// </param>
		    /// <param name="applicationKey" type="string" mayBeNull="false">
		    /// The Mobile Service application's key.
		    /// </param>

Meanwhile the current beta doesn't. The previous version fails on PhoneGap build on ios and Android M.
Is there any guide where i can make changes to backend in this regard.

What backend are you currently using? Is it Mobile Services or Mobile Apps?

Mobile services.

https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-migrating-from-mobile-services/

In addition, https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-node-backend-upgrading-from-mobile-services/ talks about upgrading to Mobile Apps. https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-node-backend-how-to-use-server-sdk/ talks about the Mobile Apps nodejs sdk in detail.

Thanks for the quick response. I will just try to experiment with methods from 1.8 and B4. Migrate tom if it doesnt work.
will close the issue tomorrow, if i fail.

There are few other differences like authentication in the Cordova clients for Mobile Services and Mobile Apps. The Mobile Apps client (beta4) isn't intended to be compatible with the Mobile Services backend. In the short term you can try your approach.
For my information what is the error you are running into on Android and iOS? Also, can you link me to the plugin you are using?

Plugin for mobile services
https://github.com/Azure/azure-mobile-services-cordova
There is an error during run time in the following code
Promise.prototype.done = function (success, error) {
   	        this.then(success, error).then(null, function(err) {
   	            // "done" throws any final errors as global uncaught exceptions. The setTimeout
   	            // ensures the exception won't get caught in the Promises machinery or user code.
   	            setTimeout(function () { throw new Error(err); }, 1);
   	        });
   	        return undefined; // You can't chain onto a .done()
   	    };

I thought the mobile services were closed inorder to be replaced mobile apps.
Correct me if i am wrong

Thanks! It will be good if you can share the repro steps so that I can take a look too.
Your understanding of Mobile Apps is correct. I was referring to subtle changes in the Mobile Apps backend like REST endpoints for authentication which makes the Mobile Apps client incompatible with the Mobile Services backend.

No response for a long time, closing the issue.


Known issue in Java 8: TGS ticket generated by S4U2self is not forwardable

When invoking "impersonate", the TGS ticket generated does not have the forwardable flag set, preventing a target service called after S4U2proxy to invoke yet-another-hope with a second S4U2proxy...
Reported issue at http://comments.gmane.org/gmane.linux.redhat.freeipa.user/19481
Patch included for JDK 9: http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/ae6449bc523f

In fact this report is wrong - mistake was in server kerberos configuration, as usual.
With both Java 8 and 9, "impersonate" works properly and produce tickets that can be used to query TGS for another hop.

Hi Yves,
Is there any chance you know what their configuration mistake were?
I'm trying to run your example (Java 1.8 u74) and I get this:

Caused by: KrbException: Message stream modified (41)
KrbKdcRep.check: at #1. request for true, received false

I have web service which do SPNEGO authentication, and know I want to do constrained delegation to a backend service (Constrained delegation is configured under the "Delegation tab" in AD).
login.txt
krb5.txt

ADS_UF_TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION userAccountControl bit needs to be set! Setting this flag solved my problems.
Flag described here:
https://msdn.microsoft.com/en-us/library/cc223145.aspx

Hello
This is strange that the flag is unset on your service account. I have to confirm but I expect this flag to be set when invoking "ktpass" when generating keytab used to establish "trust" between your Java process and ActiveDirectory (keytab file is used instead of password to preauthenticate service)

On my service account, the flag - ADS_UF_TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION is set correctly.
Still I am getting this error - "S4U2self needs a FORWARDABLE ticket"
ymartin59, how did you manage to solve this issue?

@vijaysr @bhushan1987 Please check your TGT (on your workstation) has "forwardable" flag set
You may use klist -ef on Linux or kerbtray on Windows to do so.

Thanks, but the flag ADS_UF_TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION is set on the service account to whom the SPN is attached.

I figured out the solution. You need to set the JAAS config file in the system path. Then only the ticket obtained from the keytab is "forwardaable".
Surprisingly, this is not mentioned anywhere clearly.
System.setProperty("java.security.krb5.conf", "<path_to_JAAS_config>");
Also make sure you have mentioned "forwardable = true" in your JAAS config file.
Pasting example config file below:
[libdefaults]
default_realm = DOMAIN.COM
default_tkt_enctypes = aes128-cts aes128-cts-hmac-sha1-96 aes256-cts aes256-cts-hmac-sha1-96 rc4-hmac des-cbc-crc des-cbc-md5
default_tgs_enctypes = aes128-cts aes128-cts-hmac-sha1-96 aes256-cts aes256-cts-hmac-sha1-96 rc4-hmac des-cbc-crc des-cbc-md5
permitted_enctypes   = aes128-cts aes128-cts-hmac-sha1-96 aes256-cts aes256-cts-hmac-sha1-96 rc4-hmac des-cbc-crc des-cbc-md5
dns_lookup_kdc = true
dns_lookup_realm = false
forwardable = true
[realms]
	DOMAIN.COM = {
		kdc = KDC_HOST.DOMAIN.COM
		admin_server = KDC_HOST.DOMAIN.COM
		default_domain = DOMAIN.COM
	}

[domain_realms]
	domain.com = DOMAIN.COM
	.domain.com = DOMAIN.COM

This file is not JAAS configuration file but krb5.conf file used by native kerberos library https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html. There is no need to set system property java.security.krb5.conf if you already configured /etc/krb5.conf on Unix or C:\Windows\krb5.ini on windows.
From my point of view, there is no need for "servicelogin" TGT to be forwardable, as answered at https://stackoverflow.com/a/57087305/737790

@vijaysr Please do not comment on a closed issue - I am not sure your question is really related to - your question is interesting, may you please create a new dedicated issue about it.

Does the ExtendedGSSCredential::impersonate method support the resource based KCD? With resource based KCD, we don't set this TrustedToAuthForDelegation attribute. Only the PrincipalsAllowedToDelegateToAccount is set.
When I tried it, I get the following error.
Caused by: KrbException: S4U2self ticket must be FORWARDABLE
at sun.security.krb5.internal.CredentialsUtil.acquireS4U2selfCreds(CredentialsUtil.java:75)
at sun.security.krb5.Credentials.acquireS4U2selfCreds(Credentials.java:463)
at sun.security.jgss.krb5.Krb5InitCredential.impersonate(Krb5InitCredential.java:356)


Adds a list of active maintainers to README

So people know who to ping when they have questions, issues or want a review on a PR.

This makes me smile. 😁First time as a collaborator on a major repo!


IgCookieNotFoundError: Cookie "ds_user_id" not found

Error
Requirements

[x] I've searched the Issues
[x] I've read the basic concepts
[x] I'm using the latest version
[ ] I've debugged my code using the DEBUG variable.

Platform

[x] I'm using Node.js version v18.3.0
[ ] I'm using electron

Description
My username and password is correct, yet I still get the error mentioned in the issue title.
This is a duplicate of #997 but the issue was not properly resolved there.
Code
const fetch = require('node-fetch');
const config = require('./config.json')
const chalk = require('chalk');
const { IgApiClient } = require("instagram-private-api")
require('dotenv').config();
const ms = require('ms');

const USERNAME = "wtffspree";
const PASSWORD = process.env.instagram_password || config.instagram_password;
const currentBio = process.env.current_bio || config.current_bio;
const sentenceBeforeMentioningTrack = process.env.sentence_before_mentioning_track || config.sentence_before_mentioning_track;

const ig = new IgApiClient()
ig.state.generateDevice(USERNAME);

const response = fetch("https://api.spotify.com/v1/me/player/currently-playing?market=ES", {
        method: 'GET',
        headers: {
            'Content-Type': 'application/json',
            'Accept': 'application/json',
            'Authorization': `Bearer ${process.env.spotify_token || config.spotify_token}`,
        },
    })

const login = async () => {
    try {
        await ig.simulate.preLoginFlow()
        await ig.account.login(USERNAME, PASSWORD)
        process.nextTick(async () => await ig.simulate.postLoginFlow())
    }
    catch (err) {
        console.log(chalk.redBright('error' + " An error occured while connecting to your Instagram account:" + err))
    }
}

const main = async () => {
    try {
    const data = await response.json();
    const track = data.item.name;
    const artist = data.item.artists[0].name;
    console.log(chalk.blueBright('playing') + chalk.yellow(` ${track}`) + ` -` + chalk.yellowBright(` ${artist}`));
    login().then(await ig.account.setBiography(`${currentBio}` + `${sentenceBeforeMentioningTrack}` + ` ${track} - ${artist}`))
    }
    catch (err) {
        login().then(await ig.account.setBiography(`${currentBio}`))
    }

}

main()
setInterval(main, ms('1m'));

Error and Output
            throw new errors_1.IgCookieNotFoundError(key);
                  ^

IgCookieNotFoundError: Cookie "ds_user_id" not found
    at State.extractCookieValue (D:\Code\currently-playing-bio\node_modules\instagram-private-api\dist\core\state.js:143:19)
    at get cookieUserId [as cookieUserId] (D:\Code\currently-playing-bio\node_modules\instagram-private-api\dist\core\state.js:127:21)
    at AccountRepository.setBiography (D:\Code\currently-playing-bio\node_modules\instagram-private-api\dist\repositories\account.repository.js:166:41)
    at main (D:\Code\currently-playing-bio\index.js:45:39)
    at Object.<anonymous> (D:\Code\currently-playing-bio\index.js:50:1)
    at Module._compile (node:internal/modules/cjs/loader:1105:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1159:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Module._load (node:internal/modules/cjs/loader:827:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
    at node:internal/main/run_main_module:17:47

because the serialized data is a promise...put an await on it


conditioned Cox regression after PS matching  in the example

@schuemie
In the chapter 12. PLE, the example shows the conditioned Cox regression after PS matching
(PS matching in Figure 12.14 and Conditioned Cox regression in Fig 12.15)
Wouldn't it better to show 'Unconditioned Cox regression after PS matching' or 'Conditioned Cox regression after PS stratification'?
I know current ATLAS doesn't support 'unconditioned Cox regression' setting (I don't know the reason why I cannot set 'unconditioned Cox' in current ATLAS)

Never mind it was 'conditioned Cox regression after variable-ratio PS matching', so it makes sense. Sorry for my misunderstanding @schuemie


MySql Unicode Problem

I can use MySQL Connector , But When I want to show Chinese Characters it only show ??? why ?

Try setting this option right before you connect:
mysql.setOption(.MYSQL_SET_CHARSET_NAME, "utf8mb4")

OK done it


Please add support for dnd4eBeta

Hello @ghost91- is it possible to add support for EndlesNights / dnd4eBeta when you can?
Kind regards.

Been informed there is support for this using Drac's 4e Tools.
Closing this for now.


Add preliminary grouping of transformations

How should we group these transformations?
Note: this is a temporary interface. We can move to a nicer one in the future.

Woah nice, this already looks much better. Maybe we can discuss in our meeting tomorrow what would make the most sense as groupings for the target audience.
Also, it doesn't seem to render the corresponding transformation UI when I make a selection now--any idea why typeChange isn't getting triggered?


Can the aspect ratio be changed from stretch to cover?

I'm trying to prevent the scanner view from squishing when it's not using the full viewport. Just knowing where to start hacking would really help. Thanks.

@syousif94 with the new version 3.0.0 this should be no problem anymore. Could you report back if this resolves your issue? Thank you.

Awesome, thank you!
I'll let you know as soon as I test it.

It's still squishing the image. Also, when I added viewFinderHeight and viewFinderWidth, the viewfinder borders disappeared. My code looks like this:
<BarcodeScanner
  onBarCodeRead={this._onBarcode}
  style={{ flex: 1 }}
  torchMode='off'
  cameraType='back'
  viewFinderHeight={VIEW_HEIGHT}
  viewFinderWidth={FULL_WIDTH}
/>

@syousif94 How it going？

I has same issue

@feit couldn't fix it. may try disabling the viewfinder and using react native camera.

even without changing the size the camera view is stretched.
and no docs for setting fill / stretch / fit

Yeah, any update on this issue?

try this:
const windowWidth = Dimensions.get('window').width;
const cameraAspectRatio = 4/3;

<View style={{flex: 2}}>
  <BarcodeScanner
    onBarCodeRead={this._onBarcode}
    style={{
      flex: 1,
      alignItems: 'center',
    }}
    torchMode='off'
    cameraType='back'
    width={windowWidth}
    height={windowWidth * cameraAspectRatio}
  />
</View>

Anyone figure out a good solution for this? Setting the width and height only works if you keep the ratio and also isn't really ideal for flex layouts.

I forgot overflow: 'hidden' on the container, now it's fixed. Aspect ratio of the viewfinder is determined by flex layout, but the screen is not deformed. (QR codes are read from the whole camera picture, not just from the visible part in the viewfinder.)

Thanks. This did seem to fix the image from being squished, but it also breaks any custom overlays inside the Scanner component. Will see if I can figure out a work around.

overflow: 'hidden' didn't work for me with the latest version.


Could not resolve "@repo/visual-editing-helpers/csm"

Describe the bug
After updating packages I am having an issue with visual editor and a missing import.
To Reproduce
Running visual editor with svelte 4. I feel like this may be an issue with npm but have not been able to resolve it.
Error occurs running Svelte with npm run dev.
Expected behavior
I was able to run the app without a problem but am now getting this issue with importing visual-editing-helpers.
Which versions of Sanity are you using?
"@sanity/visual-editing": "^2.11.0",
"svelte": "^4.2.19",
VITE v5.4.11
3.68.2
What operating system are you using?
MacOS
Which versions of Node.js / npm are you running?
Run npm -v && node -v in the terminal and copy-paste the result here.
11.0.0
v23.4.0
Additional context
error:
k:dev: ✘ [ERROR] Could not resolve "@repo/visual-editing-helpers/csm"
k:dev:
k:dev:     ../../node_modules/@sanity/visual-editing/src/util/documents.ts:1:28:
k:dev:       1 │ import {DRAFTS_PREFIX} from '@repo/visual-editing-helpers/csm'
k:dev:         ╵                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
k:dev:
k:dev:   You can mark the path "@repo/visual-editing-helpers/csm" as external to exclude it from the
k:dev:   bundle, which will remove this error and leave the unresolved path in the bundle.
Any help much appreciated.

Getting the exact same issue.
Just adding import { setPreviewing } from '@sanity/visual-editing/svelte'; to the +layout.ts file bugs out the whole system.
I am using pnpm and it is also an issue here.

Sorry to hear you are experiencing the same, @pjarnfelt.
It seems visual-editing-helpers is not being bundled when npm installs visual editing.

The issue started in 2.11.0 and was not present in 2.10.10 I am using bun and also seeing this issue

The issue started in 2.11.0 and was not present in 2.10.10 I am using bun and also seeing this issue

Exactly the same for me!


Emitting a keyDown or keyUp event with a specific key

According to the doc, emitEvent takes in an event name, but this won't work with the keyup or keydown event when you need to specific a key as well.

Based on the documentation from the link (https://www.npmjs.com/package/@splinetool/runtime?activeTab=code), the SPEObject in @splinetool/runtime has the following method:
/**
 * Triggers a Spline event.
 * Starts from first state to last state.
 * @param {string} eventName String that matches the Spline event's name
 * @param {string} uuid String to match to the object's uuid
 */
emitEvent: (eventName: SplineEventName) => void;

Thus, it appears necessary to ensure compatibility with this implementation. However, it may be required to align the event details on the Spline side as well....

This issue is more than one year old. There still no solution for this?

Here is a really hacky workaround that I've found: document.dispatchEvent(new KeyboardEvent("keydown", { key: "l" }))


Please upload latest releases to the docker registry

The latest available docker image is k8s.gcr.io/node-problem-detector:v0.8.2, v0.8.3 and v0.8.4 are currently missing.
Could you please upload those.

I believe the releases are now under a subdirectory:
k8s.gcr.io/node-problem-detector/node-problem-detector:v0.8.4

Right, then probably https://github.com/kubernetes/node-problem-detector/blob/f42281ee2658900bdb0571e1159a43f6ab712a19/deployment/node-problem-detector.yaml#L23 could be updated

yep, that got me too :) and I got a nice ErrImagePull ...


Ensure status_code is in the registered dict

It may happen status_code isn't in the dict, leading to weird failure.
While this is apparently a random failure, it does hit at least in CI
(and could be reproduced locally with a simple playbook).
Ensuring the dict key is present should, hopefully, avoid a failure.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

/approve

/lgtm


Frontend: Enable -target-min-inlining-version min for API modules by default

Resolves rdar://67975153.

@swift-ci please test


Add mail ru

Added mail.ru to the sites.json list
Deletion form URL: https://account.mail.ru/user/delete
Help article URL: https://help.mail.ru/mail-help/faq/delete

Closing in favor of #377


11 feat zed sdk docker

Description
Issue #
This pull request adds zed sdk to docker stack with correct implementation.
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@dyu056 @YachtChen can you please test this works on the jetson with the cone detection/cone mapping


Allow multiple channels per connection

ConnectionStream.createConnectionChannel creates both a connection and a channel and there doesn't seem to be a way of creating multiple channels over a single connection, unless I'm missing something. According to https://stackoverflow.com/questions/18418936/rabbitmq-and-relationship-between-channel-and-connection, the rabbitmq model favours an approach of creating multiple channels within an application over a single connection to the server to reduce the amount of resources used. This is also important in my application where we're connecting to a Rabbit-as-a-service server which has a limited number of connections available.
It would be great to have some mechanism to create additional channels on an open connection.

Hi @DougC , nice seeing you around here!
Thanks for reporting it, I swear I had a déjà vu when I saw this issue and I believed this was already solved but it seems not.
It definitely makes sense to have this. If you would like to work on a PR I'd gladly take it otherwise I'll pick it up whenever I find some time :)

Hi @gvolpe! I've been giving it some thought overnight and wondering if multiple channels on a connection actually adds much benefit to an application since all activities will be serialised onto the channel anyway. So would it make sense to simply open one connection/channel pair and re-use it for all activities, in which case there would be no need for any change to fs2-rabbit? So I've done some investigation and I'm pretty sure that there is benefit in making the change. Here are my thoughts:

com.rabbitmq.client.Channel implementations, as far as I can tell, are not thread-safe (which matches with what the docs say). Although deep down the transmit function synchronises on a mutex that protects the channel, there are other places, such as incrementing the sequence number during transmit, that aren't thread-safe.
fs2-rabbit AMQPClient doesn't add any additional thread-safety to the channel (e.g. wrapping in a Ref), which is fair enough - no need to add the overhead.
The AMQP framing protocol multiplexes traffic on the connection and interleaves data from multiple channels, which means that small messages won't get delayed behind large messages, which would be the case if all the messages were sent down one channel.

I'll try and find some time in the next couple of days to put together a PR.
Thanks for providing this very handy library!

Thanks for the merge. Any thoughts on when you're planning the next release?

I'll publish a snapshot in a few minutes with these changes. I'd like to make a release as soon as #150 gets done (I'm planning to work on it these days, more likely next week).

https://oss.sonatype.org/content/repositories/snapshots/com/github/gvolpe/fs2-rabbit_2.12/1.2.1-SNAPSHOT/

Thanks :-)


jHi` causes String.sub exception

jHi`

Same for:
let a="

This is now fixed by https://github.com/rescript-lang/syntax/pull/328/files and https://github.com/rescript-lang/syntax/commit/c192534f9a08d81e66d54acf6da041a4af2eba80


breaking change in 0.1.1: "TypeError: 'NoneType' object is not iterable" when calling ARIScanner.evaluate()

This code works in versions 0.0.0 and 0.1.0.
I pulled from the latest main (git rev-parse --short HEAD: 1cdca85e) and started getting this error.
We are initializing an ARIScanner and then calling its evaluate method on different scripts a couple of times. The first calls are fine, but when we try to call it with a different script we run into this Exception: TypeError: 'NoneType' object is not iterable.
Here's a more detailed stack trace:
line 17, in __init__
    val = self.scanner.evaluate(
  File "/Users/andrewjda/ansible-risk-insight/ansible_risk_insight/scanner.py", line 1006, in evaluate
    scandata.annotate()
  File "/Users/andrewjda/ansible-risk-insight/ansible_risk_insight/scanner.py", line 609, in annotate
    contexts = analyze(self.contexts)
  File "/Users/andrewjda/ansible-risk-insight/ansible_risk_insight/analyzer.py", line 64, in analyze
    for j, t in enumerate(ctx.tasks):
  File "/Users/andrewjda/ansible-risk-insight/ansible_risk_insight/models.py", line 1645, in tasks
    return self.taskcalls
  File "/Users/andrewjda/ansible-risk-insight/ansible_risk_insight/models.py", line 1641, in taskcalls
    return [t for t in self.sequence if t.type == RunTargetType.Task]

Let me know if you'd like any more information from me. Thanks!

Thank you very much for reporting this. @andyjda
The fix PR https://github.com/ansible/ansible-risk-insight/pull/135 has been merged and this issue should be resolved now.


Still the same issue with 2.9.0 version and 3.0.0 as well

Original Issue: https://github.com/springfox/springfox/issues/2393
@MahithaC have you tried 2.9.0 if it is any better?
Originally posted by @dilipkrish in https://github.com/springfox/springfox/issue_comments/386814154
I have exactly the same issue. On investigating it further in editor.swagger.io, it appears that xml properties(listed below) get missed out in case of nested elements. If I just manually add the below block it shows the element with a correct case.
{
name: "",
attribute: false,
wrapped: false
}
Couldn't see a solution to this anywhere on this or related post? Do we have a fix for this?
Thanks,
Ishan

@dilipkrish Can we please see and confirm if this is a bug?


htop: using types.coercedTo

This refactors the htop module to use the coercedTo type function, which I didn't know of before I wrote the module initially.

Many thanks for the cleanup! I haven't used coercedTo before and it seems to work very well here. Rebased your change into master in 1d24e96074ac8c4c787c556fc3fa0fd7ff4a25ca.
Note, I changed your commit message slightly from "using" to "use", i.e. imperative mood.


Create calvijn.txt

Email of teacher is<EMAIL_ADDRESS>And of students is<EMAIL_ADDRESS>

@kennysinkeler Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!

Yes it is. Thuis school is 13+

This•


Consider adding specific libuv adapter

We may want to add a specific adapter taking advantage of libuv's process handling logic:

http://docs.libuv.org/en/v1.x/process.html
https://github.com/bwoebi/php-uv#resource-uv_spawnresource-loop-string-command-array-args-array-stdio-string-cwd-array-env--array-callable-callback-long-flags--array-options

To be clear, this project works just fine with all loop implementations, including the default StreamSelectLoop and ExtUvLoop. This potential adapter could take advantage of some of the optimizations inside libuv and avoid some of the known limitations of the project.
In particular, this may help with Windows support (#9) in the future because libuv supports pipes with overlapped mode on Windows. Note that a Windows build of ext-uv does not appear to be available at the time of writing this, but it is believed to change again in the future  (https://github.com/bwoebi/php-uv/issues/63).

Note that I've fixed the building on windows for php-uv.

See also @CharlotteDunois's excellent version here: https://github.com/AndromedaGalaxy/reactphp-libuv-process


#5605 update release notes for 3.1

Signed-off-by: Nigel Jones<EMAIL_ADDRESS>

Description
Release notes for 3.1
How Has This Been Tested?
Documentation only. Reviewed in intellij
Any additional notes for reviewers?
Please add any additional changes you think would be useful in the release notes as comments in the review.

As release 3.1 has now shipped I will merge these changes.
Please raise any additions/corrections as a new issue/pr


Allows for custom headers

Adds ability to send custom headers.  This is key for testing purposes allowing certain builds through security mechanisms.
let session = Session(webView: webView)
session.delegate = self
session.pathConfiguration = pathConfiguration
session.customHeaders["CF-Access-Client-Id"] = "<token>.access"
session.customHeaders["CF-Access-Client-Secret"] = "<secret>"

No longer needed with hotwire-native-ios.  Can be managed with a custom webview.
Hotwire.config.makeCustomWebView = { config in
    let webView = AddHeadersWebView(frame: .zero, configuration: config)
    let delegate = CustomHeadersDelegate()
    webView.navigationDelegate = delegate;
    #if DEBUG
    if #available(iOS 16.4, *) {
        webView.isInspectable = true;
    }
    #endif
    return webView
}

class AddHeadersWebView: WKWebView{
    override func load(_ request: URLRequest) -> WKNavigation? {
        let newRequest = (request as NSURLRequest).mutableCopy() as! NSMutableURLRequest
        let customHeaders = [
            "CF-Access-Client-Id": "<token>.access",
            "CF-Access-Client-Secret":  "< secret>"
        ]

        customHeaders.forEach { key, value in
            newRequest.addValue(value, forHTTPHeaderField: key)
        }

        return super.load(newRequest as URLRequest)
    }
}


Add Back button on first page of new sheet submission

Add Back button to the left of the Clear button on the first page of the new sheet submission
When Back is clicked

Return to identify page
If user selects the new sheet pathway again, any data they already uploaded or entered remains
If user selects the existing sheet submission path, any previously-entered data in the new sheet path is reset/removed/deleted

It seems odd to have different form data retention if the back button is chosen depending on the route you choose.

I initially thought it would be helpful for data to be retained if they backed out, then chose again the path they were on previously. However, I prefer the simplicity of resetting the state machine when new or existing is clicked.

Are implying that any existing sheet uploads should be deleted?
Yes, to deal with orphaned files. This will need a new issue anyway. I've been thinking about the scenarios of when it should happen.

Otherwise, I believe this is validated as it works now.


How do i add a character here in source

What is your question?
Something like this

tbh dont break your head and make it softcoded, its faster and easier in my opinion


chore: Add PR template

What this does
Adds a PR template to improve PR creation.
Screenshot

Hi @gau94rav, would be nice to merge this PR template when you have some time. Thanks


Fix assert_contains and assert_not_contains for std::string::String

assert_contains and assert_not_contains can now be used with std::string::String values:
assert_contains!("Hello World!", String::from("World"));

Fixes #483, Closes GUS-W-11679979

Closing for now, I thought this would be a super quick fix, but in the end it turned out that it isn't easy to mimick assert_eq's capabilities with a naive fix.


Rust Error on ParseTicks When Using isAlive and inventory

Error: When running the ParseTicks command, if you have both the isAlive and inventory attributes selected, it will throw the following error:
thread '<unnamed>' panicked at demoparser/src/parser/src/variants.rs:319:21:
Tried to push a Some(Bool(false)) into a StringVec([["m4a1_silencer", "smokegrenade"]]) column
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5

Demo: Both overpass and inferno from this match: https://www.hltv.org/matches/2367592/complexity-vs-m80-thunderpick-world-championship-2023
Version: 0.11.3
Command: let playerData = parseTicks(filePath, ["is_alive", "inventory"], [singleTick])

should be fixed in 0.12.0

Looks good, thank you very much!


🚸 Retry reads and writes on transient errors

What does this pull request do?
Retry reads and writes to external services on transient errors to improve user experience.
What is the intent behind these changes?
Currently, users experience random network blips as fatal errors (for example, 502 Bad Gateway responses) and we should retry those transient failures.
This change will retry only those. Quoting https://visionmedia.github.io/superagent/#retrying-requests:

By default the following status codes are retried:
408
413
429
500
502
503
504
521
522
524

By default the following error codes are retried:
'ETIMEDOUT'
'ECONNRESET'
'EADDRINUSE'
'ECONNREFUSED'
'EPIPE'
'ENOTFOUND'
'ENETUNREACH'
'EAI_AGAIN'

which are good enough defaults for us.
This was previously turned off in b24a3d2ca21fcf5d0e679d13d75cc686e14d9737 to mitigate load-related snowballing.
Further improvements could focus on introducing circuit breakers.

thanks!


docker: FATAL could not initialize New Relic client, make sure your profile is configured with newrelic profile configure

Description
➜  Documents docker run  -it --rm -e NEWRELIC_API_KEY=foo newrelic/cli apm application search --name fe-bl-service --accountId 3086931 --trace --debug
DEBUG could not load string value for key region, returning zero value: no value found at path *.region
DEBUG could not initialize SplitService: split SDK init error: Factory instantiation: you passed an empty apikey, apikey must be a non-empty string
DEBUG could not load string value for key apiKey and profile default, returning zero value: no value found at path default.apiKey
DEBUG could not load string value for key insightsInsertKey and profile default, returning zero value: no value found at path default.insightsInsertKey
DEBUG [splitio/client] - ERROR - 2021/08/27 17:17:08 Factory instantiation: you passed an empty apikey, apikey must be a non-empty string
DEBUG error initializing client: a User API key or Ingest API key is required, set a default profile or use the NEW_RELIC_API_KEY or NEW_RELIC_INSIGHTS_INSERT_KEY environment variables
FATAL could not initialize New Relic client, make sure your profile is configured with `newrelic profile configure`

I don't think docker image is designed around having to create profile manually
Go Version
go version go1.17 darwin/amd64

why was this closed? I'm having the same issue

/reopen

agree, wouldn't be easier to reopen this ticket? 😕 it's exactly the same issue

Thanks, sorry we usually ask for new ticket if the original author hasn't replied in a while.
But since @ostrolucky did I've reopened it.

There's a small typo in the command, not sure if it's same for you @ostrolucky
NEWRELIC_API_KEY needs to be NEW_RELIC_API_KEY.
If you're in the EU region you also need to add NEW_RELIC_REGION="EU"

Indeed 🤦 Thank you!

NEWRELIC_API_KEY needs to be NEW_RELIC_API_KEY -> Thanks! This worked for me as well.


220925 increase test coverage

Codecov Report

Merging #68 (563e74c) into version/0.14.1 (ded9af5) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@                Coverage Diff                 @@
##           version/0.14.1      #68      +/-   ##
==================================================
+ Coverage           96.60%   96.63%   +0.02%
==================================================
  Files                  36       36
  Lines                3535     3532       -3
  Branches              791      791
==================================================
- Hits                 3415     3413       -2
+ Misses                117      116       -1
  Partials                3        3

Impacted Files
Coverage Δ

src/FromItemInfo.ts
100.00% <100.00%> (ø)

src/ReturningItemInfo.ts
100.00% <100.00%> (+2.56%)
:arrow_up:

src/SelectItemInfo.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Homepage view

The interactive map will be here, the "make a report" section will be highly visible in browser version, but it will take the spotlight in mobile version


KeyPathIterable

Sorry this took a lot longer than expected, but hopefully we can start pushing this through! Please make changes you feel are necessary. Some of the metadata comments aren't useful, maybe we want more tests? Please let me know.
Edit: The readme that I updated is just a short snippet, we can update it more.
cc: @rxwei @dan-zheng

This is exciting! 🎉 As you expand on the proposal, I have a few thoughts/questions on the proposed APIs. We don't necessarily need to discuss these here — the forums or a follow-up proposal would make sense, as well.

It will be important to explain the difference between getting all the key paths for a type and for a value — I'm not sure those operations should have the same names. (MemoryLayout's APIs could be a guide here —something like  Reflection<Type>.allKeyPaths() vs Reflection.allKeyPaths(for: value).)
Should array elements be treated as "named", given that we currently have the duality of keyed / unkeyed collections in both
Codable and Mirror? What motivates the current design? What are non-named elements in this case?
Should the custom key-path iterable functionality be provided for collections more generally than array & dictionary?
Have you explored lazily generating the resulting collection of key paths, instead of returning an array? Getting the key paths for a collection this way will be an O(n) operation.
Given that you can pass any type to Reflection.allKeyPaths(for:), KeyPathIterable seems like a misnomer. Should that protocol have the Custom prefix, like CustomStringConvertible and CustomReflectable?
From a prioritization standpoint, why should KeyPathIterable come before the tools to access type metadata that you've defined internally?

@natecook1000 Hi Nate, I believe @rxwei and/or @dan-zheng said they were going to start discussion back up on the forums. I would love to continue discussing some of the API decisions we made over there once they're ready to start discussion back up.

After some discussion with @natecook1000 we'll merge this into the reflection branch and iterate further with new PRs.


Pause For  after cyclus don't work anymore

if i set the settings
2-5         150
150         5M pause after this cyclus
not working anymore
even with other settings it don't work anymore i can't find what to change in js  to fix it
plz can this de fixed
thx in advanced  nice work you did this snipe bot

Pause For does not take single value any more , you have to give in range like 1-10S
https://github.com/chithakumar13/Fifa21-AutoBuyer#pause-for


wilcard for user and resource

I want to do this:
let grantsObject = {
        '*': {
          '*': {
            'create:any': ['!*'],
            'read:any': ['!*'],
            'update:any': ['!*'],
            'delete:any': ['!*']
          }
        }
      };
//......... add more reading database
const ac = new AccessControl(grantsObject);

but I having this error:
Unhandled rejection AccessControlError: Cannot use reserved name "*" for a resource.
so, is there any way to add a default permission for all users and all resources?

In our case, we would like to grant anyone permission to read:any of their own resource. Seems not possible at the moment.

To expand on this, I'd love an api like this:
ac.grant('user').resource('resource_one').action('create', 'any')
ac.grant('user').resource('resource_one').action('edit', 'own')

allowing
ac.grant('user').resource('resource_one').action('*', 'any')

or
ac.grant('admin').resource('*').action('*', 'any')

or some other combination that you could imagine!

There's an (intermediate) solution to your problems https://github.com/anodynos/accesscontrol-re :-)

I want to do this:
let grantsObject = {
        '*': {
          '*': {
            'create:any': ['!*'],
            'read:any': ['!*'],
            'update:any': ['!*'],
            'delete:any': ['!*']
          }
        }
      };
//......... add more reading database
const ac = new AccessControl(grantsObject);

but I having this error: Unhandled rejection AccessControlError: Cannot use reserved name "*" for a resource.
so, is there any way to add default permission for all users and all resources?

I think instead of granting all permissions to all roles using *. Have a default role that is granted to everyone and then use that role to grant all permissions.


thunderbird, thunderbird-bin: 78.2.1 -> 78.2.2

Motivation for this change

Various fixes and changes, including OpenPGP related issues.

https://www.thunderbird.net/en-US/thunderbird/78.2.2/releasenotes/
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

After running thunderbird-bin, .cache/fontconfig is corrupted and other applications fail with segfault on startup. I don't know whether this happens only on my environment or not.  Maybe, mixing fontconfig versions caused this.

Result of nixpkgs-review pr 97892 1

2 packages built:

thunderbird-78
thunderbird-bin-78

The compiled one was suffering from a big issue (#97994).  I'm looking at testing these together with a fix, for the backports, too.


Make extended grammar work for Token imports.

Suggestion
Currently, (as an example), to extend a statement rule in a grammar called old_gram.lark, we can do %import .old_gram.statement -> old_gram__statement in the new grammar file new_gram.lark. The problem is that this does not work for Tokens and we cannot do %import .old_gram.IDENTIFIER -> old_gram__IDENTIFIER (lark will report an error because lark thinks old_gram__IDENTIFIER as a rule not a token). One workaround would be simply %import .old_gram.IDENTIFIER with the downside to be that the merged transformer of the old/new transformers would not work by default.
There is also another big issue of not being able to do %import .old_gram.IDENTIFIER -> old_gram__IDENTIFIER: if in old_gram.lark, we have the following rule:
identifier_list: IDENTIFIER ("," IDENTIFIER)*

and we import it to new_gram.lark with %import .old_gram.identifier_list -> old_gram__identifier_list. In the generated tree of programs that use identifier_list, IDENTIFIER tokens will be translated to old_gram__IDENTIFIER (under identifier_list Tree).  Then, we have some old_gram__IDENTIFIER live in the Tree, but we cannot explicitly add this Token to the tree. Any workaround we try will diverge from old_gram__IDENTIFIER.
My suggestion is to make the default prefix of Token importing to be uppercase, for example, %import .old_gram.IDENTIFIER -> OLD_GRAM__IDENTIFIER.
It would be great if someone can let me know if the above makes sense, I can probably help here too.

There is the idea of making terminals MixedCase instead of only UPPER_CASE. That way, user can name them MyTerminal if they want, and it will also solve what you're referring to.
But I'm not sure how I feel about users importing rules and terminals into a namespace explicitly.
Why not have matching import from the transformer instead?
i.e.
%import .old_gram.IDENTIFIER

and
class NewTransformer(Transformer):
    from old_transformer import IDENTIFIER

Thanks for the reply. Yes, I agree that we can match import from the transformer, but have to do that is already a different user experience from importing rules. Also, this might worth being documented somewhere.

Maybe so. This is a pretty new feature. I didn't even get a chance to use it much yet, so I can't say for sure what's the recommended usage.

Sorry, might have to confirm that I understood this:

But I'm not sure how I feel about users importing rules and terminals into a namespace explicitly.

Importing rules into a namespace is required for many use cases, right? Based on https://github.com/lark-parser/lark/blob/master/examples/composition/storage.lark and https://github.com/lark-parser/lark/pull/973#issuecomment-907287565

Yes, importing rules in the local namespace is a common operation.
What you were doing is injecting rules into other namespaces. In this case, the original namespace, so it's not as bad, but still feels like it shouldn't be encouraged. I'd much rather add a %soft_import directive that doesn't remove the namespace.


@@unique constraint doesn't handle non-scalar types

I believe this is strongly related to prisma/prisma2#1681, and could be a regression on prisma/prisma2#1377.

In one of my models, I have a model that looks similar to this snippet:
model User { ... }
model Item { ... }

model Sprint {
  id String @id @default(cuid())

  user      User
  items     Item[]
  startDate DateTime
  endDate   DateTime

  createdAt DateTime @default(now())

  @@unique([user, startDate, endDate])
}

But I think the @@unique attribute only handles the startDate and endDate components. My parser isn't panicking, but it is creating a type called StartDateEndDateCompoundUniqueInput which ignores user entirely when doing sprint.upsert(...)
type StartDateEndDateCompoundUniqueInput {
  startDate: DateTime
  endDate: DateTime
}

Is the @@unique constraint completely ignoring non-scalar types in this example?

You're correct. This issue occurred in preview023 but not preview024. This can be considered resolved.

For anyone who needs to upgrade the version, this is the command I used:
yarn upgrade<EMAIL_ADDRESS><EMAIL_ADDRESS>
I'm pretty sure just including<EMAIL_ADDRESS>would be fine.


schema browser/table view: Display JSON/VARIANT data in modal

As it is very common to employ nested data types in Snowflake quite extensively, it would be helpful to make them explorable in a better way. This is very much needed, when developing a model that is supposed to flatten certain fields into dedicated columns. Being able to browse a VARIANT field helps identifying the corresponding JSON paths.
Implementation idea:
Just follow the approach how Snowflakes Web UI displays this kind of content in a modal.

Or maybe even follow Apache Superset's Approach:

Closed in favour of a feature request: https://dataform.canny.io/feature-requests/p/schema-browsertable-view-display-jsonvariant-data-in-modal


Pass error info in #[source] variants

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a03627e) 70.61% compared to head (0132cf3) 67.18%.

:exclamation: Current head 0132cf3 differs from pull request most recent head f84907e. Consider uploading reports for the commit f84907e to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1217      +/-   ##
==========================================
- Coverage   70.61%   67.18%   -3.44%
==========================================
  Files          56       52       -4
  Lines        7066     6734     -332
  Branches     7066     6734     -332
==========================================
- Hits         4990     4524     -466
- Misses       1658     1798     +140
+ Partials      418      412       -6

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


Cannot add member to custom cluster - x509: certificate has expired or is not yet valid

Rancher Server Setup

Rancher version: 2.5.1
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: 1.19.3 and 1.19.7
Cluster Type (Local/Downstream): Custom (Rancher-launched)

Describe the bug
When trying to add a member (AD) to a custom cluster (Rancher-launched) I receive an errors and member does not get added.
To Reproduce

Result
I receive an error and user does not get added:
Internal error occurred: failed calling webhook "rancherauth.cattle.io": Post "https://rancher-webhook.cattle-system.svc:443/v1/webhook/validation?timeout=10s": x509: certificate has expired or is not yet valid: current time 2021-11-12T13:19:12Z is after 2021-10-22T13:04:54Z
Expected Result
User gets added.
Additional context
I tried rotating all certificates via Rancher on another cluster and add the member there but this resulted in the same error. Do I need to rotate the certificates of the Rancher HA cluster instead? If so, how?

On local cluster you need to do

On the local cluster, you need  to remove cattle-webhook-tls certificate on secrets and then remove rancher-webhook pod
https://github.com/rancher/rancher/issues/35068#issuecomment-943155280
and possibly change the version of rancher-webhook:v0.2.0 to rancher-webhook:v0.1.1 to be able to recreate the certificate
https://github.com/rancher/rancher/issues/35068#issuecomment-943691271

I followed this procedure and it worked. Thank you.
https://rancher.com/docs/rancher/v2.6/en/troubleshooting/expired-webhook-certificates/

if we delete it will it break anything

if we delete it will it break anything
no it will not break anything

I followed this procedure and it worked. Thank you. https://rancher.com/docs/rancher/v2.6/en/troubleshooting/expired-webhook-certificates/

Thanks @StoneCut it worked for me as well

Thanks @StoneCut , it really worked.


Fix loader 12287

Sorry for all the commits, this is my first time doing this process.
Fix for issue #12287, define isFunction in loader

Can you please clean up this PR / create a new PR which only includes your changes? Otherwise we can't work with this.


Dreambooth with custom CKPT -- Error no file named model_index.json

When attempting to use the Dreambooth API to train some custom CKPT files, the job will fail and this error will be logged.
OSError: Error no file named model_index.json found in directory cog_custom_base_data.
In my case, this occurred with the following model: https://civitai.com/models/4384/dreamshaper
That model provides multiple .ckpt files, I was using dreamshaper_331BakedVae.ckpt.
The prediction job ID is jkghijcnbbavznmgkc3pi4fcty.
Another user experienced the same bug with https://civitai.com/models/4201/realistic-vision-v13. (see Discord: https://discord.com/channels/775512803439280149/1074390955639177336)
For the sake of completeness, my payload generation is below (in PHP, but I'm sure you can get the gist).
$response = $client->post('/v1/predictions', [
    RequestOptions::JSON => [
        'version' => '9c41656f8ae2e3d2af4c1b46913d7467cd891f2c1c5f3d97f1142e876e63ed7a',
        'input' => [
            'instance_prompt' => Str::replace('_', ' ', $name),
            'class_prompt' => $gender,
            'instance_data' => 'https://an_s3_url',
            'num_class_images' => 200,
            'save_sample_prompt' => 'a photo of ' . Str::replace('_', ' ', $name),
            'resolution' => 512,
            'max_train_steps' => 1500,
            'ckpt_base' => 'https://a_long_s3_presigned_url'
        ],
    ],
]);

Quick update: I think the underlying error is the state_dict missing some keys. At the top of the stack trace, I can see this error:
Missing key(s) in state_dict: "up_blocks.0.upsamplers.0.conv.weight", "up_blocks.0.upsamplers.0.conv.bias", "up_blocks.1.upsamplers.0.conv.weight", "up_blocks.1.upsamplers.0.conv.bias", "up_blocks.2.upsamplers.0.conv.weight", "up_blocks.2.upsamplers.0.conv.bias".
Unexpected key(s) in state_dict: "up_blocks.0.attentions.2.conv.bias", "up_blocks.0.attentions.2.conv.weight".

I'm running into the exact same issue.

Hi folks, we fixed an issue with the Dreambooth trainer that trains on top of an existing custom CKPT, which improves compatibility with many CKPT files that failed previously. The new trainer version is a8ba568da0313951a6b311b43b1ea3bf9f2ef7b9fd97ed94cebd7ffd2da66654. You can also find it under the "versions" tab here: https://replicate.com/replicate/dreambooth/versions

Hi @Pwntus, I'm using the latest trainer version a8ba568da0313951a6b311b43b1ea3bf9f2ef7b9fd97ed94cebd7ffd2da66654  but still seeing the "model_index.json" error for almost every huggingface checkpoint file I try, including:

https://huggingface.co/wavymulder/portraitplus/blob/main/portrait%2B1.0.ckpt
https://huggingface.co/SG161222/Realistic_Vision_V1.4/blob/main/Realistic_Vision_V1.4.ckpt
https://huggingface.co/SG161222/Realistic_Vision_V2.0/blob/main/Realistic_Vision_V2.0-fp16-no-ema-inpainting.ckpt

This one works:

https://huggingface.co/dreamlike-art/dreamlike-photoreal-2.0/resolve/main/dreamlike-photoreal-2.0.ckpt


Rethinking how we do routing

As discussed in #119, I think it's worthwhile to reconsider how we route requests.
How we currently do it
Requests to the worker invoke the fetch() method in src/worker.ts. A Handler is defined for each HTTP method that the worker accepts (with the exception of HEAD, which shares a handler with GET). The Handler is in charge of routing the request and caching (if applicable).
For the POST handler it's fine imo, but the GET handler is a bit messy.
Proposal A - Provider Refactoring
As part of adding the Provider concept, I was going to refactor some bits of the routing code to make it generally cleaner. I have a untested and still very rough implementation of it for HEAD requests here: https://github.com/nodejs/release-cloudflare-worker/blob/flakey5/20240414/file-actions/src/handlers/head.ts
The general plan for it was to split up the GET method Handler so that it was only handling GETs, and to have a Handler specifically for HEAD requests. Additionally, any code specific to files or directories would be removed and placed into actions/file.ts or actions/directory.ts (see here).
This approach doesn't really change much about how we route requests in the worker - it's mostly cleanup.
Proposal B - Middleware Approach
This was proposed by @ovflowd in #119.
We can create different Middlewares that would look something like
class R2Middleware extends Middleware {
  // override
  handle(request: Request, next: (request: Request) => Promise<Response>): Promise<Response> {
    try {
      // handle request using R2
    } catch (err) {
      // some error happened - fallback
      return next(request);
    }
  }
}

Then, we can define a route like,
get('/dist/**', [r2Middlware, originMiddleware])

This is by far a lot more modular system than what we have and gives us a lot more control over how the worker is serving requests.
I was able to get something written up that should work - will update with a link when I push it. Under the hood, it uses itty-router. I was going to try out find-my-way but I don't think it's possible with its current api.
Proposal C - Just using itty-router
Something like
get('/dist/**', async req => {
  // handle requests similarly to how we would in proposal a
  // the main benefit to this proposal is we should be able to get rid of the mapUrlPathToBucketPath method
  const path = req.path.substring('/dist/'.length);
})

For both Proposal B and C we get the added benefit of being able to easily and nicely add new routes if we need to.

I'm biased towards Plan B, but also OK with plan C and A. (I'd prefer C over A)

I'm biased towards Plan B, but also OK with plan C and A. (I'd prefer C over A)

I think that's about the same in regards to what I'd prefer we do as well

Awesome! Let's do it. @MoLow do you have a different opinion here?

using an existing solution makes sense to me, but if a reimplementation will make code look better then I am ok with that as well

Fwiw, proposal b would really just be a wrapper of itty-router.


docs(contributors): Add Andrew Toy to the contributors list

I took a stab at adding you to the contributors list but feel free to update these PR if you want to add other contributions.
To update it, you can use yarn contributors:add

Thanks for adding me!


Websocket keep-alive

With a LoadBalancer, a websocket will be killed if inactive for e.g. 60 minutes (depends on timeout settings).
So we need a ping for our websocket, to keep it alive...
Simply send a PING to the server. The server will respond with OK.
The ping interval should be configurable via server or client config (same config file as fore alive interval). So, load interval from config file and override the value with the interval, sent by server - if sent.

Does the server already send the interval or is it coming soon

I've implemented it the same way I did with the aliveInterval, I've just named it "loadInterval"

Property is not available at the moment.

webSocketPingInterval
is a better property name. This is what it should do.

or
wsPingInterval

if ping interval is -1 -> no ping


LEGO: Pull request from lego/hb_935_20170831150035311 to master

LEGO: Pull request from lego/hb_935_20170831150035311 to master with localized lcls

@csigs,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Port Yii2 to Yii3.

Q
A

Is bugfix?
✔

New feature?
✔

Breaks BC?
✔

Fixed issues
https://github.com/yiisoft/db-redis/issues/12

👍


:package: chore: Add revm to repo

Description
Adds revm as git submodule to repo
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #451   👈

This comment was auto-generated by Graphite.


buildguide: add requirements of gcc version

c++17 is only provided in gcc 5 or grater
See: https://gcc.gnu.org/projects/cxx-status.html#cxx17

OR We may change default setting of c++ version to c++11 like #70 if c++17 is not necessary

@YukihoAA can't we check for this in cmake.. let me see


Update to 0.17.13

I know pascaldulieu already made one, but there's conflicts. This one should merge automatically.

You should be able to push to other peoples branches if you have enough rights in the repo.


Implement option to ignore legacy verified status

Introduced an option that lets users revoke legacy verified status for users subscribed to Twitter Blue. Currently, a legacy verified user will show a legacy verification badge if they are subscribed to Twitter Blue.
Note: The pop-up doesn't look great right now and I didn't want to mess with the structure too much as my experience with React is limited. Would appreciate suggestions/fixes!

Great, thanks for your constribution!


Token refresh

Changed security configuration
Changed password validation rules
Added API for refreshing access token
Authentication completed

Please include the review remarks of PR #137 into this PR and post a comment once they are done, so I can merge

All review remarks of PR #137 are included into this PR.


adding ci badge, new screenshot

One trick I sometimes do is I'll upload an image to a github issue (or PR) and then use the github generated URL as the one for screenshots in readmes. Mostly so there aren't binary files being changed too much in the repo (which ends up making the overall repo, once cloned, much bigger).

That's super clever, love it! I will switch that out 👍. I plan to update the readme much more thoroughly soon anyway (and maybe we wouldn't even want a screen shot after that -- I included it originally because I hadn't taken the time to write a nice readme 😄)


check authorizations after challenge responses

What have you changed?
I've changed some of the logic in get_certificate to call check_authorization_status() twice instead of just once. There are a couple of reasons for this:

After submitting a challenge response, the client wasn't waiting for the authorization to transition to the valid status, if it was in the pending status before that. The ACME server might have not had enough time to run the validation of the DNS challenge to transition the authorization to the valid state.
An authorization could have been successfully handled by a previous run of sewer for a hostname or set of hostnames. LetsEncrypt in particular caches valid authorizations for 30 days, so if you're requesting a new certificate for a hostname which you had already proved ownership, recently, then you should not submit a challenge for it.

Why did you change it?
I was getting a 403 error in send_csr: {'detail': 'Error finalizing order :: authorizations for these names not found or expired: rolodex.example.com', 'type': 'urn:ietf:params:acme:error:unauthorized', 'status': 403}. This is described in more detail in #109.
I adjusted the unit tests to better suite the modified logic. Particularly, the test_respond_to_challenge_called is validated by mocking a {"status": "pending"} response from check_authorization_status(). All the other tests don't go through that path (they are given a {"status": "valid"} response)

@luisbarrueco Hi.
Thanks for sending this for review. I don't have much time on my hand right now, but I'll do a proper review over the weekend.

I didn't get time last weekend to look at this.
I'll have a look this coming weekend


Timepicker in 5 min (Custom set) step increments

https://github.com/tuannvm2109/time_picker_spinner_pop_up/blob/bd34897f5fae28a220f10b72603eb30dcd8d3921/lib/time_picker_spinner_pop_up.dart#L251
I add this  minuteInterval: 5,  manually its good if it is a params like
 minimumDate: widget.minTime,    maximumDate: widget.maxTime,

Thank you for your feedback, I have added this to version 1.1.0


[Feature]: need to adjust generate from table output

The first item generated is the id:increments  and its being generated like  "fieldInput": "id:integer,true,true", and reverse these two.     "inForm": true,   "inIndex": false
    {
        "fieldInput": "id:increments",
        //** "fieldInput": "id:increments:guarded ",   //** possible
        "htmlType": "number",
        "validations": "",
        "searchable": false,
        "fillable": false,
        "primary": true,
        "inForm": false,
        "inIndex": true
    },

just thinking outside the box but maybe we can add a protected / guarded option for the fields and a protected option to the dates. to output into the model or i guess just add it regardless to all models.

Model.php
protected $guarded = ['id'];
protected $dates = ['published_at', 'deleted_at'];

Also on the date fields you should change to false by default.
{
        "fieldInput": "created_at:dateTime",
        "htmlType": "date",
        "validations": "",
        "searchable": true,
        "fillable": false,
        "primary": false,
        "inForm": false,
        "inIndex": false
    },

also on the date fields you should change to false by default.
"inForm": true,
"inIndex": true

I also noticed in your sample file you have it formatting the fields like this:
 {
        "name": "updated_at",
        "dbType": "timestamp",
        "htmlType": "",
        "validations": "",
        "searchable": false,
        "fillable": false,
        "primary": false,
        "inForm": false,
        "inIndex": false
    }

but in the actual output from table they are formatted like this:
  {
        "fieldInput": "id:integer,true,true",
        "htmlType": "number",
        "validations": "",
        "searchable": false,
        "fillable": false,
        "primary": true,
        "inForm": true,
        "inIndex": false
    },

What is this are is it now part of the generator?
 "dbType": "",
 "type": "",
 "relation": ""

if they are now part of it i would format the main sample file to copy the new format accordingly weather they are used on everyfield or not. Its getting a bit confusing. Also in relation fields we should add 2 more options for update and delete "cascade"
  {
        "fieldInput": "id:guarded",
        "dbType": "increments",
        "htmlType": "number",
        "validations": "",
        "searchable": false,
        "fillable": false,
        "primary": true,
        "inForm": true,
        "inIndex": false,
        "type": "relation",
        "relation": "1tm,Feature",
        "update": "cascade",
        "delete": "cascade"
    },

@madsynn it's already there, also dbType is supported and you can specify it.

relationship you can define like dbType": "integer:unsigned:foreign,users,id

@madsynn at the moment we don't have any support related to guarded but we will keep in our queue.


poll quietly fails when kafka server goes away and returns to service

Steps to reproduce:

Install and run kafka 0.8.2.
Start a process that polls a topic for messages. If you display debug emitters, you should see a message kafka.on debug: no data - reentering poll every few seconds.
Push some messages to topic and ensure the poller responds as expected.
Stop and restart kafka.
The poller goes quiet. No more kafka.on debug: no data - reentering poll messages and no indication that it will return from the spiral of death.

FYI - here is some more info that might help debug this issue:
kafka.on debug: no data - reentering poll
socket end
socket close
socket end
socket close


lwm2m: adding the Bootstrap Interface [v4]

Main changes from v3 (#2217):
Minor changes suggested by @cabelitos
Future Improvements
Use the SOL_MAIN_DEFAULT()
Add an API to add and remove known clients on the fly
Add tests to test-lwm2m.c

Thanks for the help and awesome tips @cabelitos.
Signed-off-by: Bruno Melo<EMAIL_ADDRESS>

As suggested, I'm closing this PR and opening a new one, since Semaphore CI is not picking it up for some reason.