IPv6 support missing

I tried to set additional socket options to enable IPv6 for a socket but those options are not exposed via the library. Could you add this easily?

I made the latest release just for you :)

👌


Colors washed out after 1.31 upgrade

Since the 1.31 release all the colors have a yellow hue to them. When I downgrade to 1.30 this issue goes away.  I have updated GPU drivers and run with the --disable-gpu flag without any success.
I installed the insiders 1.32 build and the issue is still occurring, but the 1.31 exploration build #68893 does not have this issue.
Image comparison below.
1.31.1

1.30.2

@bpasero dupe of https://github.com/Microsoft/vscode/issues/68893?

Yeah could be.
We are building exploration builds that use a much newer version of our UI framework (Electron version 4.0.x). I wonder if this issue reproduces with one of these builds, could you try? Download:

macOS: Download
Linux: Download
Windows: Download

Doesn't occur on the exploration build (I had already checked and mentioned above).
This does not happen on my other PC, so this could be something around my hardware.

CPUs
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 x 2592)

GPU
Nvidia P2000 / Intel UHD630

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabled webgl: enabledwebgl2: enabled

Memory (System)
31.78GB (24.29GB free)

Process Argv

Screen Reader
no

VM
0%

I have same issue updating to 1.36, not sure what ver I was coming from though.
Version: 1.36.0-insider (user setup)
Commit: c089daa858f34631f5f827ff8a0313bf1e2ded6d
Date: 2019-06-07T05:19:15.188Z
Electron: 4.2.3
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.17763

Same issue on ubuntu

We will ship with Electron 4 with our upcoming release 1.36 this week. As such I am closing this issue. To benefit from the update already today, consider to use our insiders version: https://code.visualstudio.com/insiders/

Not sure if it's the same problem, but after 1.36 colors are a bit off. I'm using Ubuntu 19.04.

Turning off HDR on my primary monitor fixed the washed out colors (even though I was using VSCode on a secondary monitor).  I'm on VSCode 1.36.1

@bpasero this issue is still occuring in version 1.36.1 it looks like when you enable HDR vscode becomes washed out, can we reopen this issue?

Got it. See https://github.com/microsoft/vscode/issues/65816 for the related issue to allow to force the color profile as a setting (not having to pass it as command line argument).


Working ?

Hi, I'm on Grafana 10.4.0 ans PostgreSQL and it appears that the plugin is not working. The tile is appearing nice and smooth but when I click on play nothing happens

Hi!
When i click to play / pause, i get an error of variable used before Assignment...
On the demo, there is a deprecation warning in grafana 10.2.0. Can't understand why in mine it's not working...
Any help appreciated here !
Have a nice day !

Able to solved de variable used before assignment by changing "let" to "var". But got a "can't find variable : angular" ! ^^'

Yeah, just checked. Seems the angular object was removed between 10.2 and 10.4. This means the foundation of this script (let's face it, was already a hack to begin with) is now gone and it's a lot more difficult to do something similar in react.
This would mean this quick script would need to be replaced by a full blown plugin. We might come to that at some point, but it has a low priority on our development roadmap, so we need to deprecate it for now.
Happy to accept pull requests though ;-) and thanks for reporting your issue, will save others some time.


Making base64 encoding/decoding optional

I am storing my messages as Json in to the database and I didn't want them to be base64 so I made it optional.

It also would be great to have ability to store messages in column with BLOB type (bytea in postgres for example).

hi, @dnvriend are you going to merger this?

This week I will look at all the pull requests. The serialization feature is something I want to have for some time now, but I am thinking about a pluggable architecture, so this pull request will not be it but I will look into it. I am glad that you contributed though and your code will serve for inspiration. Thank you!
Regards
Dennis

Thanks, just wanted to add some feature that are nice to have:

ability to change journal/snapshot tables schema and mapping
it should be easy to store data in readable formats (json, xml, etc..)

Really looking forward to your new release :)


Allow unbound to use TCP for upstream DNS requests (Domain override) instead of UDP

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
In my configuration unbound uses domain overrides through an IPsec tunnel. As described in the following forum discussion the IPsec tunnel has an issue with UDP communication. Telling unbound to use TCP for specific domain overrides solves the problem that DNS requests through the IPsec tunnel time out.
See link: https://forum.opnsense.org/index.php?topic=32997.0
Describe the solution you like
Allow users to configure to use TCP for communication per domain override in the WebUI. This can be done by adding the parameter "forward-tcp-upstream: yes" in the domain override configuration section (see example below).
root@opnsense:/var/unbound/etc # cat domainoverrides.conf
forward-zone:
  name: "fritz.box"
  forward-addr: <IP_ADDRESS>
  forward-tcp-upstream: yes
root@opnsense-host:/var/unbound/etc #

Describe alternatives you considered
The only alternative will be to solve the IPsec issue as discussed in the forum (see link above)

https://github.com/opnsense/core/commit/a556df4a85df41db80b4b4ec22e9f9bfc79f2925 should do the trick

Many thanks.


GEODE-5575: Removes Travis CI

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[ ] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Seems fine since we've integrated the PR checks with concourse.  Let's leave the travis jobs in place for geode-examples and geode-native though.
LGTM.


fix spawn in Windows OS

In Windows OS, the spawn command is failing for the npx command triggered at first for compiling cds.
Adding .cmd to the command fixes the issue.

fixed in this PR:
https://github.com/SAP/ctz/pull/17
Closing this one.


Problems with backslash (Windows, DIRECTORY_SEPARATOR)

It seems like this problem is still here: https://github.com/michaeldrennen/Geonames/issues/18
PHP constant DIRECTORY_SEPARATOR on Windows system is backslash: "\"
On MySQL query running it make a troubles:
# php.exe artisan geonames:install --country=EN --language=en
.............................................................
Inserting via LOAD DATA INFILE: D:\OpenServer\domains\project\storage\geonames\iso-languagecodes.txt
SQLSTATE[HY000]: General error: 7890 Can't find file 'D:OpenServerdomainsprojectstoragegeonamesiso-languagecodes'.

PDO::exec("LOAD DATA LOCAL INFILE 'D:\OpenServer\domains\project\storage\geonames\iso-languagecodes.txt'
    INTO TABLE geonames_iso_language_codes_working IGNORE 1 LINES
        (   iso_639_3,
            iso_639_2,
            iso_639_1,
            language_name,
            @created_at,
            @updated_at)
    SET created_at=NOW(),updated_at=null")

@michaeldrennen you use DIRECTORY_SEPARATOR constant in two packages: Geonames & LocalFile.
Geonames requires Laravel, so it's possible to use dotenv features and change DIRECTORY_SEPARATOR to env('DIRECTORY_SEPARATOR', DIRECTORY_SEPARATOR) in the Geonames package source code, and don't forget to add line DIRECTORY_SEPARATOR=/ to .env file.
LocalFile package need to change too, in method split() - add optional attribute $directorySeparator with default value.

Hi, for fix this problema i added addslashes() to $absoluteLocalFilePathOfIsoLanguageCodesFile in the file IsoLanguageCode.php and it would be like this:
$absoluteLocalFilePathOfIsoLanguageCodesFile = addslashes(self::downloadFile($this, $remotePath, $this->connectionName));
The same for the following files:
InsertGeonames.php -> $absolutePathToMasterTxtFile = addslashes($this->combineTxtFiles());
I hope it helps!!!

Hi, for fix this problema i added addslashes() to $absoluteLocalFilePathOfIsoLanguageCodesFile in the file IsoLanguageCode.php and it would be like this:
$absoluteLocalFilePathOfIsoLanguageCodesFile = addslashes(self::downloadFile($this, $remotePath, $this->connectionName));
The same for the following files:
InsertGeonames.php -> $absolutePathToMasterTxtFile = addslashes($this->combineTxtFiles());
I hope it helps!!!

With those changes it works for me. Thanks  @CamaleonGamer !!!

Hi, for fix this problema i added addslashes() to $absoluteLocalFilePathOfIsoLanguageCodesFile in the file IsoLanguageCode.php and it would be like this:
$absoluteLocalFilePathOfIsoLanguageCodesFile = addslashes(self::downloadFile($this, $remotePath, $this->connectionName));
The same for the following files:
InsertGeonames.php -> $absolutePathToMasterTxtFile = addslashes($this->combineTxtFiles());
I hope it helps!!!

I use windows and I had the same problem but with the changes you mention works perfectly. Thanks @CamaleonGamer

Good thing it was helpful! Greetings!

I just committed some code that should fix this issue.
@CamaleonGamer was on the right track.
Let me know if this resolves the issue.
If not, I will dust off my Windows machine and take a deep dive.

I just committed some code that should fix this issue.
@CamaleonGamer was on the right track.
Let me know if this resolves the issue.
If not, I will dust off my Windows machine and take a deep dive.

I just committed some code that should fix this issue.
@CamaleonGamer was on the right track.
Let me know if this resolves the issue.
If not, I will dust off my Windows machine and take a deep dive.

Excellent, Thanks so much!

I just committed some code that should fix this issue.
@CamaleonGamer was on the right track.
Let me know if this resolves the issue.
If not, I will dust off my Windows machine and take a deep dive.

Excellent, Thanks so much!


add editThreadAdmins

few days ago I've made similar function to #658
But I didn't have time to write docs so I didn't pushed it to Github
It looks a bit cleaner IMO
I've also done some tests in the wild
and you can change adminStatus of every user in thread without being blocked by Facebook
but if you try to do the same thing one by one... Facebook blocks you for an hour :(

changelog record and docs added

@bsansouci, could we merge?

These little changes were just sorting alphabetically
Should I really undo them?

Alright had a chance to look at this again. If this is the one that you guys want to merge, let's change the name to changeAdminStatus to be more consistent with the other function names and then I'm happy to merge. Idrc about the function order, sorry for the delay here but in the future it's probably simplest to keep it to one PR per feature when possible.

thanks!


Raycast Extension: Download Video Youtube : 🚨 Error: ffmpeg is not installed

Extension
https://www.raycast.com/vimtor/youtube-downloader
Description
found installation instruction about homebrew but after copy and pasting the code in terminal no fix happened
Steps To Reproduce

Current Behaviour
No response
Expected Behaviour
No response

Can you re-open the terminal and type which ffmpeg?
If ffmpeg was installed, you should see a path (e. g. /opt/homebrew/bin/ffmpeg) - copy & paste this path into the extension settings under ffmpeg Path

Can you re-open the terminal and type which ffmpeg? If ffmpeg was installed, you should see a path (e. g. /opt/homebrew/bin/ffmpeg) - copy & paste this path into the extension settings under ffmpeg Path

Exactly! Also, please do the same with ffprobe. (Thanks, @darmiel ❤)

Have a intel version, so my path is under /usr/local/bin/ffmpeg. Even after updating the path in the extension setting, ffmpeg can not be found...

Have a intel version, so my path is under /usr/local/bin/ffmpeg. Even after updating the path in the extension setting, ffmpeg can not be found...

Can you check if your issue is similar to #9051?

The solutions you wrote in the other thread did not work for me either. I haven tried manually installing ffmpeg though.

If I understand correctly @sjimmylin, you are also getting an error when running ffmpeg -version?

@vimtor It doesn't look like it. Here is the output:


Simplifying Setup

As of now, the repo is not very well organized to get started with running the experiments. Makes it difficult for a new user to come to the repo and start scaling experiments. The aim here is to make it easy for any user to come and start running experiments as easily as possible.

[ ] run-factorizer-enc script, has hard-coded values that need to be changed when running the script.
[ ] Less information on how to get the data and factorizer models and where to place them.
[ ] Setting up the python environment for running the experiment. Seems like conda works a bit differently than venv and it creates confusion

Modifiable parts for any experiment :

Config files : base.prep.yml and base.conf.yml. Whenever, we will have to change the language pair, this needs to be changed.
Bash Script Files : run-factorizer-enc.sh. Here, we have hardcoded parameter values which change from experiment to experiment. They change more frequently.

Getting Datasets
Although, it is easy to get the files and tokenize them using mosestokenizer, but for different language pair tokenization can vary. Can \ Shall we automate this process ?

As of now, here are the things I am working on to make this process easier :

[ ] Add a script to get the factorizer models and setting up the datasets directory ( if feasible )
[ ] Removing hardcoded parameters from bash run scripts
[ ] Minimize the number of parameters, using repo_setup.env file ( stores the variables like, dataset setup dir, factorizer model dir, exp collection dir, config store dir )
[ ] (Maybe a script to generate base conf files for different language pairs )


Remove usage of org.json

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.

This contains the container-core + metrics-proxy changes from #16279. The code for serializing decimal number to JSON now correctly handles NaN and Infinity.


Toggle hashtagName resize incremental on scrollY

On page-hashtag, the hashtagname is resized when the user scrolls downs, and the "i" toggle disappears. the "i" toggle still has to disappear, but the hashtagname has to resize relative to the scrollY position, making it a gradual resize.

no priority


chore(deps-dev): [Security] Resolve lodash to 4.17.21

No ticket.
Description
In order to fix CVE-2021-23337 and CVE-2020-28500.
How to test
As regular dependency updates.
Review

[n/a] Read CONTRIBUTING.md and Component API principles
[n/a] Annotate all props in component with documentation
[n/a] Create examples for component
[n/a] Ensure that deployed demo has expected results and good examples
[ ] Ensure that tests pass by running yarn test
[ ] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

/rebase

/rebase


[SPARK-21673] Use the correct sandbox environment variable set by Mesos

What changes were proposed in this pull request?
This change changes spark behavior to use the correct environment variable set by Mesos in the container on startup.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

LGTM from a Mesos perspective

@skonto @susanxhuynh
ok to test

Test build #4182 has started for PR 18894 at commit 4ccb4be.

Test build #4182 has finished for PR 18894 at commit 4ccb4be.

This patch fails PySpark unit tests.
This patch does not merge cleanly.
This patch adds no public classes.

retest this please

Test build #90927 has started for PR 18894 at commit 4ccb4be.

Test build #90927 has finished for PR 18894 at commit 4ccb4be.

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

Merged build finished. Test PASSed.

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


[Embeddingapi] Need to check the video playing in android TV

Impacted tests(approved): new 0, update 2, delete 0
Unit test platform: Crosswalk Project for Android 20.49.517.0
Unit test result summary: pass 2, fail 0, block 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-6120

LGTM


Use longer dimension for camera Field of View (FOV)

Currently we have camera.frustum.fovy which represents the FOV along the vertical axis.  The downside is it's hard to establish an upper limit for the FOV in both the horizontal and vertical.
In STK, the FOV applies to the larger window dimension.  If the 3D window is wider than it is tall, the FOV applies to the width, otherwise the height.  This keeps the display more reasonable during window resizes by establishing an upper bound to the FOV.  I recommend Cesium should adopt the same behavior.

I know this is closed, but folks interested in this issue, but also like http://www.gearthblog.com/blog/archives/2015/03/google-maps-earth-view-fov.html


Add kindergarten-garden exercise

Closes #194

@BNAndras let me know if you like these new enum changes, and we can merge


[docs] Fix copy paste error

Describe the pull request

What does your PR fix?
Fixes Copy paste error introduced in #24764

CC: @ras0219-msft @BillyONeal

Oops, thanks!


Update jekyll.yml

Breaking changes
Ubuntu 24.04 is ready to be the default version for the "ubuntu-latest" label in GitHub Actions and Azure DevOps.

Target date
This change will be rolled out over a period of several weeks beginning in September 25th, 2024. We plan to complete the migration by October 30th , 2024.

The motivation for the changes
GitHub Actions and Azure DevOps have supported Ubuntu 24.04 in preview mode since May 2024, and starting from July 2024 Ubuntu 24.04 is generally available for all customers. We have monitored customer feedback to improve the Ubuntu 24.04 image stability and now we are ready to set it as the latest.

Platforms affected

 Azure DevOps
 GitHub Actions
Mitigation ways
Steps or options for impact mitigation
If you see any issues with your workflows during transition period:

Switch back to Ubuntu 22 by changing workflow YAML to use runs-on: ubuntu-22.04 We support two latest LTS Ubuntu versions, so Ubuntu 22 will still be available in near future.
File an issue in this repository

I followed the above advice and fixed YAML to use ubuntu-22.04.

Thanks for the prompt help, Andreas


1.23.0-rc0 Site Administration not accessible

Description
Try to access site administration as an admin user results in a 404 (Not found or not authorized).
Gitea Version
1.23.0-rc0, also 1.23-nightly (2024-12-19)
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
dockerr
Database
SQLite

ok, had a custom head template and the admin url changed from 1.22 to 1.23

I updated the blog to add it to the break change part. https://blog.gitea.com/release-of-1.23.0-rc0/#major-breaking-changes


Initial hw1 for Krithsanvith Manthripragada (km59)

Hey Krith, I ran your code and overall it works pretty well! For gridworld, PI, VI and Q-learning give correct answers. SARSA values differ from theirs by about 10-20% so something might be off there (maybe it's just tuning of parameters). For pendulum, I am not sure why both give me very small state values. Let me know if it's not the same for you. Below are a few suggestions that could help, some of which you might know already but I've written them for completeness.
For Q-learning and SARSA:

the 'return Q' lines in SARSA and Q-learning code needs to be indented 4 spaces backward to move out of the episodes loop. Otherwise code exits loop after first episode.
use a higher value of epsilon since I guess 0.1 isn't enough to explore all states within the limited steps and episodes. For example, 0.8 in your code gave me good results.
the states and actions arguments to the functions aren't needed and env.num_states/actions could be used instead.
you could skip defining max_steps yourself. 'done' from env.step (as you use now) along with changing max_steps in gridworld.py if needed, can achieve same purpose.
return Q from q-learning function along with Q_T.

In general:

gridworld environment code in the beginning can be removed since you import gridworld anyway. Same for pendulum.
couple of very small suggestions: can use 'randrange(actions)' instead of 'randrange(0,actions,1)', can write 'Q[state]' instead of 'Q[state,:]'.

Code structure:

another way to structure your code is by defining repeatedly used functions (like sarsa, q-learning, optimal policy etc.) in a separate file and then importing them in main file to avoid defining them multiple times/copy pasting them. That could help in debugging and readability.
I am not sure how to phrase this in a general way but it's useful to add parameters used by functions in input arguments like max_episodes. Then to change it for all algorithms, it needs to be changed in only one place in the code. Also for instance in optimalpolicy function, having Q as an input argument could make it easier to re-use this function in other places because you don't have to worry about variables used in the function defined beforehand in the new code where optimalpolicy is being re-used.
using classes to organize code could also be helpful. That could help to re-use parts of code in future without copy-pasting or having to modify the rest of the code where it's being re-used. For example, another algorithm might use same update rule as in q-learning (along with other new things) or policy evaluation as in PI.

Overall, it was easy to understand and get results from your code. Just also include code for generating required plots.


Multi-language Runtimes

Create multi-language wrappers that can run Java, C++ and R models. For this, we can leverage the existing research in Seldon Core which leverages tools like JNI and PyBind to bridge from Python to other runtimes.

Adding to the above issue as indicated in https://github.com/SeldonIO/seldon-core/issues/4531
MLeap is used to deploy Spark mllib models (including Spark Xgboost and others) for inference through Java runtime. With Seldon core the Java language wrapper could be used to wrap MLeap format models and deploy using Java JNI wrapper. The JNI wrapper however had many vulnerabilities https://github.com/SeldonIO/seldon-core/issues/4103.
Please support deployment of MLeap serialized Spark MLlib models in MLServer so that Java JNI wrapper vulnerabilities can be avoided.

Hey @indranilr ,
Thanks for expressing interest on this one!
Just as a head up, this is on the roadmap, but probably won't come through until the 1.4.0 release.

Just out of interest would this include Julia support?

We've already done something along these lines for C++ and Java for SCv1 so that would be the initial priority. We are not planning to explore adding support for Julia yet.

Totally understood! Will be good to see those first few languages and we could always try to mimic for Julia if we decide we really need it :) thank @adriangonz!

Hey @indranilr ,
Thanks for expressing interest on this one!
Just as a head up, this is on the roadmap, but probably won't come through until the 1.4.0 release.

@adriangonz since 1.4.0 is released now, has the support for MLeap serialized Spark Xgboost model incorporated ? Could you please point to relevant documentation ?

Hi @indranilr -- We recently moved things around in the roadmap of MLServer and have started dedicating more capacity to improving different features of it and its runtime. It might take us a couple more versions before we can fully dedicate time for multi-language wrappers (it would definitely be very valuable to add these :raised_hands: ).


Dangers dependencies do not respect no_proxy environment variable

Report
What did you do?

Set no_proxy environment variable
Set DANGER_GITHUB_API_BASE_URL
Set DANGER_GITHUB_HOST
Set DANGER_GITHUB_API_TOKEN
Run bundle exec danger local

What did you expect to happen?
Expected danger to run locally
What happened instead?
This was printed out:
no_proxy is unsupported
/Users/xxx/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/net/http/response.rb:122:in `error!': 503 "Service Unavailable" (Faraday::ConnectionFailed)
Your Environment

Which CI are you running on? Local

Are you running the latest version of Danger? Yes

What is your Dangerfile?
  # PR is a work in progress and shouldn't be merged yet
  warn "PR is classed as Work in Progress" if github.pr_title.include? "[WIP]"

  # Warn when there is a big PR
  warn "Big PR, consider splitting into smaller" if git.lines_of_code > 500

  # Ensure a clean commits history
  if git.commits.any? { |c| c.message =~ /^Merge branch '#{github.branch_for_base}'/ }
    fail "Please rebase to get rid of the merge commits in this PR"
  end

  # Mainly to encourage writing up some reasoning about the PR, rather than
  # just leaving a title
  if github.pr_body.length < 5
    fail "Please provide a summary in the Pull Request description"
  end

  # If these are all empty something has gone wrong, better to raise it in a comment
  if git.modified_files.empty? && git.added_files.empty? && git.deleted_files.empty?
    fail "This PR has no changes at all, this is likely an issue during development."
  end

  has_app_changes = !git.modified_files.grep(/ProjectName/).empty?
  has_test_changes = !git.modified_files.grep(/ProjectNameTests/).empty?

  # If changes are more than 10 lines of code, tests need to be updated too
  if has_app_changes && !has_test_changes && git.lines_of_code > 10
    fail("Tests were not updated", sticky: false)
  end

  # Info.plist file shouldn't change often. Leave warning if it changes.
  is_plist_change = git.modified_files.sort == ["ProjectName/Info.plist"].sort

  if !is_plist_change
    warn "Plist changed, don't forget to localize your plist values"
  end

  podfile_updated = !git.modified_files.grep(/Podfile/).empty?

  # Leave warning, if Podfile changes
  if podfile_updated
    warn "The `Podfile` was updated"
  end

  # This is swiftlint plugin. More info: https://github.com/ashfurrow/danger-swiftlint
  #
  # This lints all Swift files and leave comments in PR if
  # there is any issue with linting
  swiftlint.lint_files
  swiftlint.lint_files inline_mode: true

Looks like support was added pretty recently, https://github.com/lostisland/faraday/pull/658 want to look at updating the dependency?

I've already tried setting faraday to 0.12.1 but it didn't seem to help

@orta Does this look like a possible reason as to why no_proxy is not being respected now? https://github.com/lostisland/faraday/issues/701. Basically calling Faraday.get without first initialising the connection. If so, this should be fixed in 0.12.2

Yeah.- I could imagine that being it

Hi @orta, I've looked into faraday 0.12.2 which supposedly would have fixed the no_proxy issue, but seems like we're getting two other issues, that I've figured out locally, but would love your opinion before submitting a PR.
The first error is:
 'connect_nonblock': SSL_connect returned=1 errno=0 state=error: certificate verify failed (Faraday::SSLError)
This fails as our GitHub Enterprise has a self-signed SSL cert and hence the verification fails when dealing with Octokit. I've managed to get bundle exec danger pr to work by adding a flag --verify-ssl flag and within pr.rb, I've modified the code as such:
def configure_octokit(cache_dir)
  # setup caching for Github calls to hitting the API rate limit too quickly
  cache_file = File.join(cache_dir, "danger_local_cache")
  cache = HTTPCache.new(cache_file, clear_cache: @clear_http_cache)
  p @verify_ssl
  Octokit.configure do |config|
    config.connection_options[:ssl] = { :verify => @verify_ssl }
  end
  Octokit.middleware = Faraday::RackBuilder.new do |builder|
    builder.use Faraday::HttpCache, store: cache, serializer: Marshal, shared_cache: false
    builder.use Octokit::Response::RaiseError
    builder.adapter Faraday.default_adapter
  end
end

This works in solving the SSL issue, but I'm not too sure if this is the only/best place to set this. Would love your advice on this.
The second issue seems to be https://github.com/bundler/bundler/issues/5300, and the fix for that is by installing a temporary gem: http://ermaker.github.io/blog/2017/02/06/proxy-error-on-ruby-2.4.0.html. This error happens when a no_proxy variable is set on Ruby version 2.4.0/2.4.1. I could submit another PR for that but not too sure if you would like to install that gem.
Thank you!

Him, I think that seems like a reasonable tradeoff - TBH, I don't know too much about all the HTTP caching, it came in as a PR 🍡
I'm happy to have it skipping verification, as it's not really a potential attack vector for anyone.
WRT the gem, that seems  fine too

Fixed in #880. Closing this issue. Thanks @orta!


Allows the profile directory to be set with an environment var

Retroactive issue for PR https://github.com/fishtown-analytics/dbt/pull/1049
Passing the CLI flag (as in dbt run --profiles-dir ~/path/to/profile) should still work. Similarly, if no DBT_PROFILES_DIR environment variable is set, DBT will look for profiles in the default location.
this change requires an update to the dbt documentation

Fixed in https://github.com/fishtown-analytics/dbt/pull/1049


FrontEnd Landing page 2

create workout cards to render seeded data (left hand side of page)

completed in branch "46-landing-page-styling"


Crash reported by a user of my modpack.

crash-2023-04-25_13.14.25-client.txt
This user reported a crash when the game finished loading, not sure what in the world would cause it to though.

Hey @Slayer5934,
it seems that you're using a version of the mod from early 2021. Just a few weeks ago I've published an update to major revision 4 on Forge 1.12.2.
Would it be possible for you to upgrade?

Indeed, I can do that (: I will close the issue then re-open if it happens again, sorry for the trouble.

No problem, just be sure to create backup before upgrading 👍🏻


Added CORS

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other: <!-- Please describe: -->

What is the current behavior?
Live Server doesn't send Access-Control-Allow-Origin header, making it difficult to develop sites. Also, 301 http status code can be cached, what is not good.
Issue Number: N/A
What is the new behavior?
I have set Access-Control-Allow-Origin to * and changed 301 status code to 302.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
None

Live server does already have a cors module.
See package.json and index.js.
Also check out the updated fork called Five Server.

Live server does already have a cors module.
See package.json and index.js.
Also check out the updated fork called Five Server.

For some reason it does not work for me.

Looks like you are right.
I have just improved the CORS options (see https://github.com/yandeu/five-server/commit/38a0b0e7e784ad44976bd642c728da04bbb0ce50).
Will be available in the next update!


Refresh application details graph when sync button is pressed.

Currently if a user presses sync the graph in the application details page will not update.
Steps:

Load application details page
Update number of replicas for application
Click sync button
Graph does not change
Reload page
Graph is now correct

The graph needs to update when a user clicks the sync button.

Perhaps regular polling similar to the applications summary page?

Related comment from an internal exercise:

Had to page reload the UI to see the updated commits (the list was cached showing older commit as the last synced)

Pressing the sync button doesn’t seems to update the source/kustomization commits list


ci: use the apm-its/main branch

What does this pull request do?
Leftover from the main renaming for the apm-its

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-01-05T15:25:21.803+0000

Duration: 36 min 51 sec

Commit: c37c81b584b78f0590befd085fcaf92cbffc7e0b

Test stats :test_tube:

Test
Results

Failed
0

Passed
10261

Skipped
9603

Total
19864

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Fire error hook while merging graphs with nodes of $type === 'error'

cc @jhusain @sdesai

oops, looks like I accidentally have some cruft from the prettier PR in here. I'll clean that up

Noted from @jhusain's review: "perhaps we shouldn't pass the routerInstance around, but it it's probably not a big deal, it's likely we'll need it for something else in the future"
Related note from me: We're using the router instance in some of our middleware to pass in a logger that we use to that errorHook, so we need to have a this context of the router instance in the _errorHook call. @jhusain noted that using bind might not be too expensive if we're doing it at the beginning of the merge, but we'll probably just leave the router instance passing for now.


Font issue

Issue in font.(transaction value)
OS: OSX Yosemite
Dash Core (<IP_ADDRESS>)

Wow. What language?

English

What was the original value?
-2.02 DASH?

-2002.xxxxx Dash

Yes, but in other places "." dot is displayed correctly, just randomly any character get get corrupted (in transaction values)

That's strange :)

Hi Karek, is this still an issue using the latest version of the software?

Hi @nmarley Sorry i don't have ability to test it right now.


Create baraBlzDev

Commits to dev. Merge with base: master, head repo:baraBlz/Microsoft.IO.Recyclable

I have no idea what this is, but it looks like a mistake.

I have no idea what this is, but it looks like a mistake.

lol benny bro, u sound like my mums gyno - yet here i am
kek 👯

Hey Ben,
My apologies, for the confusion Im just playing around with stuff I never
understood. I learn best by mistaking a lot :D
I hope I didnt bother you. If there is any action youd like me to stop.
Please feel free to let me know.
On Tue, 27 Jul 2021 at 17:00, Ben @.***> wrote:

I have no idea what this is, but it looks like a mistake.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Microsoft.IO.RecyclableMemoryStream/pull/191#issuecomment-887635250,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASMEIYH3BUTGRLLZSK2UPJLTZ3J2JANCNFSM5BCMWIMA
.


Column for company's HQs?

Would you consider helpful having their HQs?

That's a good idea! Or even a column that lists all of the physical offices maybe?

:thumbsup:


Next-gen registry & Bower architecture

I'd like to help and get the next-gen registry out. I reviewed previous discussions, and seems like the team and interested parties still need to norm on a general architecture.
State of the union

CLI works very well and heavily relied on by tens of thousands of devs and CI environments all over the world (very important to ensure uptime & backward-compatibility)
Experience for package publishers has room for improvement
Registry needs more data to be single source of truth (stats, keywords, etc.)
No user management
Does not serve binaries
3rd party integration relies on embedding CLI
Multiple server-side services with overlapping functionality
Light on tests & no CI environment
No https (https://github.com/bower/bower.github.io/issues/45)

Previous rewrite design doc for reference
Proposed architecture
Note that even though this looks very complicated, it's more of a reorganization of existing parts. Actual work will be focused on building next-gen registry and API. As you review this please keep simplicity in mind.

Drawing link
Decisions to make

Focus on RESTful API-oritented architecture (yes)
3rd party tools currently embed the CLI. Does it make sense to build an API that does most of what the CLI can do (namely /package and /search endpoints), and have the CLI be a client that consumes the API? Currently CLI does this already to a certain degree. We can also push some logic to server-side (e.g. https://github.com/bower/registry/issues/48)

User management (yes, need to experiment re: 3rd-party service)

Necessary? Or continue to use existing method of relying on github tokens (not everyone uses github)
If yes, build our own or use 3rd party API like Stormpath or Auth0?

Why not keep Postgres? (keep)
RMDBS is decently performant and well-known by potential contributors. Instead of saving the whole bower.json, we can just parse it and insert a row in a db table. For simplicity we can use an ORM like bookshelf. I'm not too familiar with Postgres / MongoDB / CouchDB / ... admin so it's up to the team to pick one and I'll figure it out.

Why store binaries? (yes, but do it last)
Major benefits vs. what we do today? Aren't packages always on a repo hosting service like Github? If not maybe publisher can submit a link to a binary (security risk?)? For private packages publisher can provide a key to install.

Is it premature to worry about scaling now? (yes for now, no action)

Do we need to worry about ease of replication? (yes, better docs on this subject for now)

Express vs. Hapi? (@svnlto can you make an argument for this?) (leaning towards hapi, need to experiment)

CoffeeScript? (no, maybe ES6 + traceur)
I would like to personally ask the team for blessing on this. I'm most productive writing CoffeeScript, but I understand there may be concern with maintenance and attracting future contributors. There are many high profile OSS projects (like Atom) that use CoffeeScript exclusively. If the team feel strongly against this I'll stick w/ vanilla js.

Do we still need caching to serve stats? (need to experiment)
If db of choice is performant enough, I'll just dump/fetch stats straight from of db

Next steps

[x] Get access, understand current infrastructure
[ ] evaluate pros / cons of hapi & 3rd-party auth service
[ ] db - new tables with stats & 3rd-party data
[ ] db - migrate packages table to include all info from bower.json
[ ] db - scrape github for bower.json data and put in packages table
[ ] CLI - include bower.json in payload, check for consistency (e.g. name, verison, etc.), recommend tags if none
[x] Break out stats front-end
[ ] adapt stats back-end for ETL service
[ ] Write new endpoints for server, proxy old endpoints
[ ] hook up user service
[ ] simple admin panel for admins / publishers
[ ] test all the things!
[ ] Set up CI (try using github's release hooks for deploy)
[ ] Load testing
[ ] Get a SSL cert
[ ] document API endpoints (use http://docs.bower.apiary.io/ or RAML)
[ ] document replication & running private registry
[ ] Update CLI (need team's help on this)
[ ] Migrate / deploy
[ ] Store / serve binaries (sponsor needed)

Info
New consistent repo / service modules naming convention:
bower-server-api (combines below)
bower-server-registry (this repo)
bower-server-etl (from stats service)
bower-server-stats (from stats service)
bower-server-user

Does anyone have objections to some work being done on these items? I have a direct need for downstream mirroring and caching, and a few free weeks I can throw at it.

Any news on this @rayshan? I'd love to consume an api.bower.io to fetch packages by a certain keyword, instead of relying on search-server which is usually flaky.

Just a small crazy hint in JS vs Coffee vs Ruby - why not Pharo (ping @pharo-project)? ;-)

Unfortunately we need to abandon api rewrite as we lack sufficient resources.
Moreover nowadays it's clear it's not a good idea to introduce yet another binaries registry when npm's is more than sufficient. I suggest to focus on developing bower a client of npm's registry, instead introducing brand new one. This would also fight bower-npm registry dichotomy we experience.


Add new cop Performance/ReverseEach

@bbatsov that is what I get for copying and pasting a section header. The header has been renamed to Performance.

@bbatsov, sorry about the earlier usage of node.children. I was working on a cop for detection of parallel assignment earlier, and I was in the mindset on not using *node.

:+1:


Need to update PatternMatcher Bundle example.

Version Information

Software
Version(s)

BusinessEvents
6.3.0

OS Type?
Windows

OS Version?
Windows 10

What is the expected behavior?
Pattern Bundle example should get execute end to end.
What is the actual behavior?
The bundled example PatternMatcher use TCP catalog functions which shows an error. So the use case should be updated accordingly.
Attached screenshot for reference.

Pattern Matcher example updated with HTTP catalog function and reverted back to OOB feature in BE.


Fixes make on ubuntu

By using a certified cl-webkit version. It is the same used by travis.

can we use a commit hash instead?

Oh sorry, I thought that was the branch name.


Inline lib functions to templates

https://github.com/forseti-security/policy-library/tree/master/lib
the lib function calls should be inlined in the template yaml files. So that the rego in the template yaml file doesn't require any additional dependencies.

I'm pursuing a solution for this using partial evaluation.

My partial evaluation exploration didn't yield anything helpful so I'm not sure that solution will work.


Improve performance by batching inserts

By batching inserts, performance can be greatly improved.
On my machine, runtime for importing Spain_Portugal.db went from 3m00 to 1m00.
I verified that the resulting db contains the same elements by comparing the results
of the query
select p.id, p.type, p.name, FR.name, FS.name, TK.name, TV.name
from Points p
         join Points_Root_Sub PRS on p.ROWID = PRS.Points_id
         join Points_Key_Value PKV on p.ROWID = PKV.Points_id
         join FoldersRoot FR on PRS.FoldersRoot_id = FR.id
         join FoldersSub FS on PRS.FoldersSub_id = FS.id
         join TagKeys TK on PKV.TagKeys_id = TK.id
         join TagValues TV on PKV.TagValues_id = TV.id
order by p.id
;

on the db before and after the change.

This patch does not handle the append mode correctly, you will get duplicate Ids (actually, what is the use case for this mode?). I'll post a patch soon.

Fixed the bug above; added two changes:

Always use node_id 0 with Poi_Importer (the ID is supposed to refer to the OSM node id, which is not available. Using 0 seems less confusing than an arbitrary, but wrong id).
Cleanup of the previous commits.


Improve user feedback when updating

when running update, it was not obvious for me that this is waiting for me to hit enter

I think this issue is potentially closed already:
const flags = parse(Deno.args, {});

let unresolvedDirectory = Deno.args[0];
if (flags._.length !== 1) {
  const userInput = prompt("Where is the project directory?", ".");
  if (!userInput) {
    error(help);
  }

That being said, I would propose the following change - if the use did not pass an argument initially, ask them if they would like to use the current directory first, then ask them to supply the path if they decline. As things stand, Deno's prompt defaults are mildly confusing without context.
const flags = parse(Deno.args, {});

let unresolvedDirectory = Deno.args[0];
if (flags._.length !== 1) {
  const updateMessage = "Update the project in the current directory? y/n - ";
  const useDefault = prompt(updateMessage)?.toLowerCase().trim();
  let userDirectory;
  switch (useDefault) {
    case "y":
      userDirectory = ".";
      break;
    case "n":
      userDirectory = prompt("Enter a directory to update:");
      break;
    default:
      error(help);
  }
  if (!userDirectory) {
    error(help);
  }
  unresolvedDirectory = userDirectory;
}

Let me know if this sounds appealing.


CGO_ENABLED error

What version of Hugo are you using (hugo version)?

$ hugo version
not installed yet

Does this issue reproduce with the latest release?
yes
I executed the following:
CGO_ENABLED=1 go install -tags extended github.com/gohugoio/hugo@latest
# runtime/cgo cgo: C compiler "gcc" not found: exec: "gcc": executable file not found in $PATH

This is not a bug. If you want to build the extended version from source, you need to install the GCC compiler.
Please use the forum (https://discourse.gohugo.io/) for questions and troubleshooting. We prefer to use GitHub for verified bugs and vetted enhancements. Thanks.


Bug: debugbar javascript error

Describe the bug
When using (a lot of) JavaScript, for instance my VueJS application, elements of the debugbar do not seem to be ready yet in the DOM, when the debugbar tries to modify those. Error in console:
Uncaught TypeError: Cannot set property 'innerHTML' of null
    at XMLHttpRequest.<anonymous> (index.php?debugbar:77)

CodeIgniter 4 version
CodeIgniter 4.0.2
Affected module(s)
system/Debug/Toolbar.php
I've created a PR to load the debugbar script right before the closing body tag, which solves this issue: #2596.
I now see it might re-introduce other issues. @najdanovicivan Does my PR conflict with yours (#2494)?

looking at the script it seems that must the response object trying to badge the icon:
var h2 = document.querySelector('#ci-history > h2');
h2.innerHTML ....

I’m a JavaScript lightweight but i think that should only be called after the listener for DOMContentLoaded has brought up the actual toolbar, so location of the script (head, body) shouldn’t matter. Can you confirm the issue is actually the badging?

Yes, I can confirm the issue. But I think it is because an XMLHttpRequest can already happen before DOMContentLoaded. Therefor and after testing some more, I'm changing my proposed solution in the PR.


[onlyOperationTypes] missing input types

This is a quick fix for https://github.com/dotansimha/graphql-code-generator/pull/3760
Some input types are missing and this is critical
This is a hotfix and should be reverted after that issue goes https://github.com/dotansimha/graphql-code-generator/issues/3958

I believe this will fix #3956

@dotansimha could you release this request. It's important for onlyOperationTypes feature


Method to populate users into test environment

As a product manager or tester, I want a method to create knowable data subjects in the Fides test environment, so that I can test privacy requests.
Details

The method for this can be anything, but the goal is that either as part of a nox command when creating the test environment or a Fides CLI command, I can create one or more test users, with either an email or phone number as an identity.
This is in-lieu of the

Acceptance Criteria

Given that I am testing Fides, while running the project, then I can add one or more data subjects to test a data subject request.

I'm assuming you want something a little more flexible than the hardcoded ones that are populated into test_env right now? Those use the database schemas we use for automated tests and populate sample data for subjects using these identities:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
For reference you can see the raw SQL for the Postgres data here: https://github.com/ethyca/fides/blob/main/src/fides/data/sample_project/postgres_sample.sql#L130


[FIX] eslint and minor bug

List of fixed issues (if they exist):

Fix eslint issues and minor bug in concat_json2trx.mjs

@dlevitas , I'm merging this in since it is NOT into the main branch. However, I don't think concat_json2trx.mjs should be in the repo at all. It is not intended to be used in the browser, and looks to be more of a convenience script rather than something that should be in /src

@hanayik thanks. This  fork is not meant to be merged into the main NiIVue branch anytime soon. Rather, this fork will explore how brainlife can use NiiVue for QA. This will go both directions: move brainlife from proprietary formats (e.g. json files for streamlines) to community formats (trx) and then make sure NiiVue can support all the brainlife features (e.g. NiiVue supports TRX groups, but does not yet support TRX per-group colors). So this branch allows us to meet half way.


Lint fails when optional chaining is in use

Affected Packages

all

Problem
Latest master has updates for TS, but prettier fails when we optional chaining is used. Example for the error:
$ /Users/dotansimha/Dev/changesets/node_modules/.bin/eslint . --ext .ts,.tsx,.js

/Users/dotansimha/Dev/changesets/packages/cli/src/commands/publish/publishPackages.ts
  108:20  error  Parsing error: Expression expected  prettier/prettier

Proposed solution

Thanks for the report - I've prepared a fix for this: https://github.com/atlassian/changesets/pull/430


Opt(multi-catalog) Opt date type reading.

Proposed changes
[Opt] (exec) (multi-catalog) Opt date type reading.
For tpch-500-parquet(one node): 2.32->1.57.
select count(l_shipdate) from lineitem;

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run p0

run p0

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>77。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>77.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>33。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>33.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>19。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>19.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>78。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>78.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>04。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>04.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>79。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>79.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>08。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>08.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>18。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>18.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>08。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>08.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>49。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>49.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>95。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>95.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>11。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>11.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>10。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>10.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/

感谢您与我们联系。(Thank you for contacting us.)
我们收到了您的请求，并会在一至两个工作日内给您回复。您的案例编号是<PHONE_NUMBER>04。
想了解更多与开发相关主题的信息，请访问 开发者支持网页 (https://developer.apple.com/support/)。
Apple Developer Program Support
We’ve received your support request and will get back to you in one to two business days. Your case number is<PHONE_NUMBER>04.
For additional information on development-related topics, visit:
https://developer.apple.com/support/
Best regards,
Apple Developer Program Support

Copyright (c) 2024 Apple Inc. All rights reserved.
Contact Us
https://developer.apple.com/contact/
Developer
https://developer.apple.com/
My Apple ID
https://appleid.apple.com
Privacy Policy
https://www.apple.com/privacy/


Voting power refactor : 1 cycle delay

See #56
I think the problem is that the most recent checkpoint block number could be higher than the block number at end of calculation period.

See #56
I think the problem is that the most recent checkpoint block number could be higher than the block number at end of calculation period.

Yea I think I see the problem

@subject026 please pull and try again, I think this should be addressed with d4809e3
Also I added some comments to the code if you would like to read through, should be more understandable now

imo there are way too many comments added to this and it's making the code messy. The code should be mostly self-commenting with exceptions made for bits of logic that are especially convoluted or require context external to the code. Overly simplistic comments are OK for Natspec comments only because they're meant to be parsed and displayed external to the source code like on Etherscan forms.

Is there a reason we're going through the trouble of converting everything between "timestamps" and "block numbers" instead of just using block numbers and approximating the duration of a cycle to be like 172800 blocks (roughly 30 days)?

imo there are way too many comments added to this and it's making the code messy. The code should be mostly self-commenting with exceptions made for bits of logic that are especially convoluted or require context external to the code. Overly simplistic comments are OK for Natspec comments only because they're meant to be parsed and displayed external to the source code like on Etherscan forms.
this is doing way too much
        // Check if the start time is before the end time
        if (_start > _end) revert StartMustBeBeforeEnd();
        // Check if the end time is after the current block
        if (_end > Time.blockNumber()) revert EndAfterCurrentBlock();
        // Get the latest checkpoint for the user
        uint32 latestCheckpointPos = BREAD.numCheckpoints(_account);
        // Check if the user has ever held $BREAD
        if (latestCheckpointPos == 0) revert NoCheckpointsForAccount();
        // Check if the user has ever held $BREAD in the interval by comparing the first mint to the end of the interval
        if (BREAD.checkpoints(_account, 0)._key > _end) return 0;
        // Starting to filter out irrelevant checkpoints that are not in the interval

addressed by 2e9c094

Is there a reason we're going through the trouble of converting everything between "timestamps" and "block numbers" instead of just using block numbers and approximating the duration of a cycle to be like 518400 blocks (roughly 30 days assuming Gnosis's 5 second block times)?

addressed by 9e6a03a @bagelface


Split 'value' into 'depositValue' and 'sendValue'

Replaces the value argument of the TransactionDeposited event, and Deposit Transaction type with two arguments:

depositValue is the ETH amount sent to the contract, to be minted on L2.
sendValue is the ETH amount to be sent to the recipient (analogous to value in s a typical L1 transaction).

Relevant issue: https://github.com/ethereum-optimism/optimistic-specs/issues/85

One potential pitfall here, which @tynes pointed out, is that an L1 contract making a deposit could end up stranding ETH on L2. This would occur in the case that the contract calls the deposit function with both msg.value > sendValue. In that case, the difference (msg.value - sendValue) would be minted to the contract's address alias on L2.
Unless the contract has been specifically designed to recover this balance, it would not be spendable as the private key is unknown.
However this possibility exists with many other design choices, including with the currently operating bridges (a contract could send value to itself).
If we reject this change, and stick with requiring that the deposit value be the same as the send value, then it would be impossible (in a Deposit-only Rollup, or with a censoring Sequencer), to transfer an existing L2 balance.

When Norswap mentioned we needed to both deposit and move funds, I was interpreting it as:

value stays the same as regular tx: it moves ETH from one account to the other, and is available through EVM execution etc.
mint is added: it creates ETH on the L2. It is up to the L1 to lock it up during the deposit flow, for later withdrawals
If value == mint: mint first in creator account, before EVM execution.
If value > mint: mint first, and then move value from that account. If account_funds + mint < value then fail the transaction.
If value <= mint: mint first, and then move value from that account. Note that there will always be enough funds during execution.
If EVM fails, the mint is still persisted, and stays at the tx origin account of the L2 execution (the From address). No lost ETH if EVM fails somehow.

This also means that the contract sets mint to msg.value (whatever it locks up will be minted on L2) and value is arbitrary (and won't be used for minting, and might cause the tx to fail on L2 if it's too high)


Update README.md to clarify Apple Developer site process

Provide guidance on creating a VoIP cert on the Apple Developer site.
Fix a doc issue raised via the docs' Feedback widget. https://twilio.slack.com/archives/CPR6DM5D4/p1655337114674259
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[X] I acknowledge that all my contributions will be made under the project's license.

I disagree. I think this info should be in there, particularly since it's a small addtion, and that to assume developers just know how to do stuff is wrong -- as the feedback comment that lead to this proposed change shows. I mean, if we're assuming developers just know how to do things why bother with any documentation?
Not my call, of course, so I'll leave it to you folks to merge or just close this PR.


Reverting long enum names in Cloud API.

Do we have to give a default value here? This is a required field and UNSPECIFIED is not actually a valid option. I'm actually working on a change that will remove all the 'UNSPECIFIED' zero values from the OpenAPI output (effectively hiding them).

We don't, no. I'll remove it.


Catalog namespaces don't show up until refresh

Rancher versions: 2.0 master 3/4
Steps to Reproduce:

Deploy wordpress catalog app

Results:  Notice that the Namespace doesn't show up on the workload page.  refresh page, and they show up.

Not reproducible any more. Once app is created namespace is showing up immediately.


rustfmt on all crates; rustfmt.toml with 400 char width

Fixes #266
Making some lines less wide is an optional future change

Thanks for the idea. Unfortunately I'd like to merge https://github.com/tomaka/vulkano/pull/321 (which is the branch I'm currently working on) into incoming first.

 I guess I trash this.

The incoming branch doesn't pass CI. The tests haven't been updated for the new code yet.

Feel free to ping me when incoming is ready for such- I can take a fresh pass checking also tests.


Add documentation for installing and using docker with NILRT

We want documentation on how to:

install docker from NILRT
ensure that it is installed correctly
start containers with host networking

Looks like your commits weren't authored with your ni.com email address.

Summary of changes:

Correct header line length
Remove bash formatting from output text
Capitalize Docker
Link to Docker main site
Correct some typos, grammar, and wording

Changes:

Fix link to Docker website
Reword host-networking section to indicate why it's useful (currently we don't support bridged networking)
Add note in installation that docker-ce is incompatible with LabVIEW RT

Changes:

Correct formatting
Link docker's host networking docs
Add note of network disabling

Changes:

Wording in intro sentence


Compilation error after creating the app

Hi,
I created the directory and the code as per the instructions in the documentation and when I ran cargo fullstack I got the error below:
error[E0063]: missing fields `model_path` and `schema_path` in initializer of `GenerationConfig<'_>`
  --> .cargo/bin/dsync.rs:19:52
   |
19 |     dsync::generate_files(schema_file, models_dir, GenerationConfig {
   |                                                    ^^^^^^^^^^^^^^^^ missing `model_path` and `schema_path`

After some trial and error, this is the fix I applied:
pub fn main() {
    let dir = env!("CARGO_MANIFEST_DIR");

    println!("Running dsync (generating model code from `backend/schema.rs`)");

    let schema_file = PathBuf::from_iter([dir, "backend/schema.rs"]);
    let models_dir = PathBuf::from_iter([dir, "backend/models"]);

    let model_path = "models::".to_string();    // <-------------------
    let schema_path = "crate::schema::".to_string();    // <-------------------

    ensure_schema_is_generated(&schema_file);

    dsync::generate_files(schema_file, models_dir, GenerationConfig {
        connection_type: "create_rust_app::Connection".to_string(),
        default_table_options: TableOptions::default()
            .tsync()
            .autogenerated_columns(vec!["id", "created_at", "updated_at"]),
        table_options: HashMap::from([
            // plugin_storage
            ("attachment_blobs", TableOptions::default().ignore()),
            ("attachments", TableOptions::default().ignore()),

            // plugin_auth
            ("role_permissions", TableOptions::default().ignore()),
            ("user_permissions", TableOptions::default().ignore()),
            ("user_roles", TableOptions::default().ignore()),
            ("user_sessions", TableOptions::default().ignore()),
            ("users", TableOptions::default().ignore()),

            // plugin_tasks
            ("fang_tasks", TableOptions::default().ignore()),
         ],
        ),
        model_path,   // <-------------------
        schema_path,   // <-------------------
    });
}

So, could you please fix this, or if I did something wrong, which is entirely possible because I am new to the rust ecosystem, could you please update the docs to outline clearly the steps that need to be done in order to successfully run the app?
Thank you,
🙏

Same issue here

This is probably due to a new release of dsync, for now try using an older version (of dsync) while I work on a fix (which might take me a while because I don't have a lot of free bandwidth right now

also, shouldn't model_path be "crate::models::" or did that not work?
see: https://github.com/Wulf/dsync/commit/ec866873bc1d074000082a03a0011bb548e9f39c (the breaking change)

This is probably due to a new release of dsync, for now try using an older version (of dsync) while I work on a fix (which might take me a while because I don't have a lot of free bandwidth right now

actually nvm, issue was much smaller than I first thought, thanks for providing your fix @boggye

do note, even after fix is pushed it may take a while to be shipped bc I don't control releases

(will close when fixes are released)

Thanks for jumping on this


DnsServerRecursion: New resource proposal

Pull Request (PR) description

DnsServerDsc

Added new resource

DnsServerRecursion - resource to enforce recursion settings (issue #198).

ResourceBase

Moved more logic from the resources into the base class for the method
Test(), Get(), and Set(). The base class now have three methods
AssertProperties(), Modify(), and GetCurrentState() where the
two latter ones must be overridden by a resource if calling the base
methods Set() and Get().

This Pull Request (PR) fixes the following issues

Fixes #198

Task list

[x] Added an entry to the change log under the Unreleased section of the
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Community Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
[x] New/changed code adheres to DSC Community Style Guidelines.

This change is

@Sudman1 I started moving more stuff into the base class ResourceBase from the resources (still not touching DnsRecordBase though). This approach simplifies the actual resources class even more, see resource DnsRecourceRecursion. I will add tests and stuff for the  DnsRecourceRecursion later (I put this one in draft in the meantime). Ones this is merged I gonna fix the DnsServerCache, DnsServerEDns, and DnsServerScavenging to use the same approach. That will also able us to remove one of the overloads of Get() in ResourceBase.

Will add unit test for the class ResourceBase.

I merge this, so I can fix the other classes I created to the same pattern so we can get rid of the one overload that is unneccessary.

@Sudman1 thanks for the review and feedback! 😃


renamed app-version -> workload-version in State.Status

Fixes #24

bundling this and some other breaking changes for a major version bump


not installing with different kubeconfig file

Hi, really fun project, enjoying it so far :). One little thing I noticed; when I merge 2 kubeconfig files in the KUBECONFIG variable, there is hardcoded path searching for config file in .kube dir in this function in client.go
// Client is used to authenticate with Kubernetes and build the Kube client
// for the rest of the program.
func Client() (*kubernetes.Clientset, error) {
	kubeConfigPath := path.Join(homedir.HomeDir(), ".kube", "config")
	return ClientFromPath(kubeConfigPath)
}

giving this error when context is in other file than config:
unable to find local kube config [/home/decoder/.kube/config]: invalid configuration: [context was not found for specified context: default, cluster has no server defined]
Swapping to another cluster (with context present in config) works as expected.
Maybe reading KUBECONFIG variable on a retry when this error occurs would be a good idea?

i think the program should inherit the same logic that kubectl uses.
if anyone wants to PR the changes feel free to - otherwise i won't be able to get to them until next week.
cheers

if you want to try the 1.0.0

Thanks for making the change so quickly. I have tested it and although both files are now picked up, the config cannot be loaded.
You can see below, I'm running the setup against docker desktop and than against my vm, both fail with the same error message. Maybe it's worth pointing out that I'm using WLS2, not sure if this might be an issue.


”Obârșia de Câmp” is listed in the drop-down menu

Description:
"Obârșia de Câmp" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Obârșia de Câmp" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Obârșia de Câmp, MEHEDINȚI".


bin= should be an instance method in MRuby::Gem::Specification

Array#flatten is unneeded because we should use bins= for passing an
array, I think.

If we remove flatten, the assignment should be @bin = bin I think.

Thank you for your comment. I interpreted your comment as follows:

bin= should accept both one name (String) and multipule names (Array).
If we don't use flatten, the assignment must be @bins = bin etc for
an array.

But bin= accept both (one name and multiple names) and bins= (just an
attr writer) accept multiple names only is unnatural for me.
I think it should be one of the following:

bin= accept one name only and bins= accept multiple names only (this PR).
bins= accept both and we remove bin=.

Hmm, it seems no one uses bin= and uses bin << path instead. So I am going to remove the method.


add color swatches

simple swatch / defs for existing color set

weirdness. w/ the commits... sorry.


Error "Page not Found"

Hi,
It seems that the page is not found when I click on the print button on the pages of my blog. It's probably an issue with the route (slug ?) of the pages.
You can see the error on any page of my blog , for instance :
http://www.gamecoderblog.com/fr/unreal-engine4/ue4-recommended-folder-structure
Tested with the lastest version of Grav, a personnal theme (GCB that is just an antimatter theme override), and prettyprint v0.3.1
Lost of plugins enabled (not sure it has any influence on the issue)
Multilanguage enabled (english and french, possible influence on the issue))

Hi,
using Chrome > Developer Tools > Application > Frames > Scripts (and Stylesheets), I do not see jQuery UI libraries and their css sheets ...

normally I haven't made specific changes for the 3.0.1 version in my blog.
After checkink its conf:
for jquery :

source was maxCDN
version was 1.12.0 (by default), probably because I've installed previous versions of your plugin before

I've changed to 1.12.1 , same error occurs

I've made some changes that improve the slug selection. Within a short time the new version should be available on GPM

hi, I've updated my blog with the last version of your plugin and the issue is still present.
I'll try to test with a clen Grav install

Hi,
I can't find where the problem is with this version of the plugin.
I've created an dev version for you, that just uses the lastest Grav version, a few plugins and the lastest version of PF.
It will be available at http://dev.gamecoderblog.com in a few minutes
Just clic on the blog Menu (top right of the home page), and clic on the print button of the post.
Now the error is an http 500.
If you need to access to the admin, just send me a PM.
I could also send you the source files.
I'll get back to the 0.2.x version on my blog, that was working well, and I'll test your next releases on my dev blog.
Good luck and Best regards
laurent

hi,
JFYI , the 0.3.3 version doesn't produce an error, but the content of the printed page is empty
you can see it on the test blog at http://dev.gamecoderblog.com in a few minutes.

Hi, I think I've found the cause of the issue.
It's due to the param_sep value in the system.yaml file
if it's set to ";" (to make Grav fully compatible with a windows system, as mine)  the issue "page not found" or sometimes "http 500" occurs.
If it's set on ":" as default, there is no issue

I've found the solution!
Mainly you should pass the parameters to your ajax call using a post method instead of get.
I'll submit a pull request, as it you can add the fix to your code if you want

Thank you for your desire to look for a solution. That is not the right one though.
On my local computer:

Apache / 2.4.7 (Ubuntu)
PHP Version 5.5.9-1ubuntu4.21

I get the same error that you get on the online server (Not found).

You say that the cause of the error was due to param_sep parameter value in system.yaml: unfortunately I did not use it because I entered ":" in code directly.
Then say that if the value of param_sep is set to ":" as default, there is no issue: that's what I said before.

So, I looked for some similarity in the code of some Grav Team plugins: in particular I looked at the Login plugin.
I will adapt to the coding adopted by the Team Grav: I will use the parameter param_sep.
Meanwhile, you could try that part of code that I reported above (of the Login plugin): the code handles sending mail when a new account is activated.


Deprecated runner stuff

What does this PR do?
Noticed some logs about deprecation in the actions, solves them
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


SQLSTATE[25P01]: No active sql transaction: 7 ERROR:  SAVEPOINT can only be used in transaction blocks error when using $afterCommit = true;

Laravel Version
10.25.2 & 10.25.1
PHP Version
8.2.10
Database Driver & Version
PostgreSQL
Description
The project I am working on uses nested transactions and they used to work flawlesly however I've updated laravel framework from version 10.25.0 to 10.25.2 and now I keep getting errors:
PDOException: SQLSTATE[25P01]: No active sql transaction: 7 ERROR: SAVEPOINT can only be used in transaction blocks in /var/www/vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php:159
I reverted back to v10.25.0 and the problem has gone away, then changed to v10.25.1 and problem re-appeared.
I then looked into the changes in vendor/laravel/framework/src/Illuminate/Database/Concerns/ManagesTransactions.php and it turned out that if I revert logic of this trait back to https://github.com/laravel/framework/blob/4b5ef9e96e15eff8b1a8f848419feba8dc0be50f/src/Illuminate/Database/Concerns/ManagesTransactions.php then issue vanished as well.
Please see below steps to reproduce and let me know if anything is unclear.
FYI (I hope you don't mid) : @mpyw, @tonysm @crynobone
Steps To Reproduce
Step 1 - below code is executed, however ActionQueue "created" event is observerd. ActionQueue observer has got $afterCommit set to true.
        DB::transaction(function () {
            $actionQueue = new ActionQueue([
                'action_id'     => Action::TEST->actionId(),
                'delay'         => 0,
                'payload'       => ['data' => 'test'],
            ]);
            $actionQueue->save();
        });

Step2 - in ActionQueue observer I dispatch below job using dispatchSync() method.
<?php

namespace App\Jobs;

use App\Models\ActionNote;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Queue\SerializesModels;
use Illuminate\Support\Facades\DB;
use Spatie\InteractsWithPayload\Concerns\InteractsWithPayload;

class Test implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels, InteractsWithPayload;

    public function handle(): void
    {
        DB::transaction(function () {
            $note = new ActionNote(['note' => mt_rand(1, 10)]);
            return $note->save();
        });
    }
}

This is when I get error:
SQLSTATE[25P01]: No active sql transaction: 7 ERROR:  SAVEPOINT can only be used in transaction blocks

I was able to reproduce this. The issue seems to be with $afterCommit and dispatchSync... I didn't have much time to dig in, but I created a sample test. With this code in my routes/web.php file I was able to reproduce it on latest Laravel:

routes/web.php
<?php

use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Foundation\Bus\Dispatchable;
use Illuminate\Notifications\Notifiable;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Queue\SerializesModels;
use Illuminate\Support\Facades\DB;
use Illuminate\Support\Facades\Route;
use Laravel\Sanctum\HasApiTokens;

class User extends Authenticatable
{
    use HasApiTokens, HasFactory, Notifiable;

    /**
     * The attributes that are mass assignable.
     *
     * @var array<int, string>
     */
    protected $fillable = [
        'name',
        'email',
        'password',
    ];

    /**
     * The attributes that should be hidden for serialization.
     *
     * @var array<int, string>
     */
    protected $hidden = [
        'password',
        'remember_token',
    ];

    /**
     * The attributes that should be cast.
     *
     * @var array<string, string>
     */
    protected $casts = [
        'email_verified_at' => 'datetime',
        'password' => 'hashed',
    ];
}

class UserObserver
{
    public $afterCommit = true;

    public function created(User $user)
    {
        logger('[observer] before dispatching the job');

        LogUserCreation::dispatchSync($user);

        logger('[observer] after dispatching job');
    }
}

User::observe(UserObserver::class);

class LogUserCreation implements ShouldQueue
{
    use Dispatchable, InteractsWithQueue, Queueable, SerializesModels;

    public function __construct(public User $user)
    {
    }

    public function handle(): void
    {
        DB::transaction(function () {
            logger('[job] before updating user');

            $this->user->update(['name' => 'changed']);

            logger('[job] after updating user but before transaction commits');
        });

        logger('[job] after transaction committed...');
    }
}

Route::get('/', function () {
    DB::transaction(function () {
        logger('[request] before creating the user (level 1)');

        DB::transaction(function () {
            logger('[request] before creating the user (level 2)');

            $user = User::make(User::factory()->raw());
            $user->save();

            logger('[request] after creating the user, but before transaction (level 2)');
        });

        logger('[request] after creating the user, but before transaction (level 1)');
    });

    return view('welcome');
});

It looks like when the transaction inside the job tries to begin, it "thinks" there's an open transaction running...

I'll try to dig in deeper this weekend, but if anyone wants to take it over, feel free (I'm at a conference right today and tomorrow, so don't have that much time available).

Somehow I can't reproduct it with v10.25.1 in my environment... 🤔

Probably the following block causing problems.
try {
    if ($this->transactions == 1) {
        $this->fireConnectionEvent('committing');
        $this->getPdo()->commit();
    }

    if ($this->afterCommitCallbacksShouldBeExecuted()) {
        $this->transactionsManager?->commit($this->getName());
    }
} catch (Throwable $e) {
    $this->handleCommitTransactionException(
        $e, $currentAttempt, $attempts
    );

    continue;
} finally {
    $this->transactions = max(0, $this->transactions - 1);
}

It might be like:
+$decreaseLevel = function (): void {
+    static $applied = false;
+    if ($applied) {
+        return;
+    }
+    $this->transactions = max(0, $this->transactions - 1);
+    $applied = true;
+};

 try {
     if ($this->transactions == 1) {
         $this->fireConnectionEvent('committing');
         $this->getPdo()->commit();
     }
+
+    $decreaseLevel();

     if ($this->afterCommitCallbacksShouldBeExecuted()) {
         $this->transactionsManager?->commit($this->getName());
     }
 } catch (Throwable $e) {
     $this->handleCommitTransactionException(
         $e, $currentAttempt, $attempts
     );

     continue;
 } finally {
-    $this->transactions = max(0, $this->transactions - 1);
+    $decreaseLevel();
 }

@crynobone I think the three methods trasaction() commit() rollback() should be reviewed at the same time, since the order of  level decreasing and callback executions must be consistent.

Also this seems to be PostgreSQL specific, not reproducible on SQLite. SQLite probably ignores SAVEPOINT calls outside of transactions.

Thank you for getting involved and I am really pleased that you were able to reproduce the issue.

Hey @crynobone we may need to revert that change to transactions, this looks a bit serious for apps using transactions. I won't have time to dig into it until Sunday 😔

We already tested the code using DatabaseMigration trait which uses the default Laravel Transaction Manager without any issue (and tested with Postgres), should add failing tests example https://github.com/laravel/framework/blob/10.x/tests/Integration/Database/EloquentTransactionWithAfterCommitTests.php


Bring types from backend to frontend

Figure out a way to use the types from backend in frontend and implement it

Types can simply be imported by @backend/ but right now tsc gives errors from backend as it tries to compile it too but does not understand the backend path aliases. This needs figuring out. maybe import type or ajdusting config files

The database files can be imported from freely, because they themselves do not import files from the rest of the backend, meaning tsc will not try to compile the rest of the backend.
So, any other types that need to be shared should be put into repo-roots shared/ directory and imported to both from there.
Not sure yet if this solution will work for everything, but I'll go with this for now


Create Repository: There is no longer a "native browser" menu item

There is no longer a "native browser" menu when right-clicking on a in Artifactory. Describe how to get the URL from the artifact and simply open it in a browser of your choise (chrome, curl...)
https://github.com/praqma-training/artifactory-katas/tree/master/create_repository#look-at-them-through-the-native-browser

There is now again the native browser menu with the latest JFrog Cloud artifactory ( I suppose 7.something ) as well as 6.23.7.
Getting the URL is added to gradle_intro where the url is picked from the repository, see PR #83


@constructor or @class in jsdoc above a function declaration crashes

When encountering a top-level function where the @constructor or @class tag is used in the jsdoc:
/**
 * An ItemSet holds a set of items and ranges which can be displayed in a
 * range. The width is determined by the parent of the ItemSet, and the height
 * is determined by the size of the items.
 * @param {{dom: Object, domProps: Object, emitter: Emitter, range: Range}} body
 * @param {Object} [options]      See ItemSet.setOptions for the available options.
 * @constructor ItemSet
 * @extends Component
 */
function ItemSet(body, options) {
  this.body = body;
  ...
}

Crashes with exception:
/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:471
            switch (e.kind) {
                     ^

TypeError: Cannot read property 'kind' of null
    at writeReference (/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:471:22)
    at writePropertyDeclaration (/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:647:9)
    at writeClassMember (/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:630:24)
    at writeClass (/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:620:13)
    at writeDeclaration (/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:760:28)
    at Object.emit (/Users/macleodbroad/workspaces/vis/node_modules/dts-dom/bin/index.js:276:5)
    at Emitter.emit (/Users/macleodbroad/workspaces/vis/node_modules/tsd-jsdoc/Emitter.js:65:24)
    at Object.publish (/Users/macleodbroad/workspaces/vis/node_modules/tsd-jsdoc/publish.js:25:39)
    at Object.module.exports.cli.generateDocs (/usr/local/lib/node_modules/jsdoc/cli.js:448:35)
    at Object.module.exports.cli.processParseResults (/usr/local/lib/node_modules/jsdoc/cli.js:399:20)
    at module.exports.cli.main (/usr/local/lib/node_modules/jsdoc/cli.js:240:14)
    at Object.module.exports.cli.runCommand (/usr/local/lib/node_modules/jsdoc/cli.js:189:5)
    at /usr/local/lib/node_modules/jsdoc/jsdoc.js:105:9
    at Object.<anonymous> (/usr/local/lib/node_modules/jsdoc/jsdoc.js:106:3)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)

Can work around it by removing the @constructor or @class tag.

Looks like this is no longer happening in the latest v2


Add github action to auto-publish new pushes to github container registry

See https://github.com/burturt/lactf-platform/pkgs/container/lactf-platform/ as an example.

@burturt I was gonna actually add this as an issue eventually lol. However, not sure if it is needed now since we are still early on in the dev stages. Even for CI/CD in the end, I don't know if the build the image locally versus pulling the image makes too much of a difference since we are only deploying this at once place so it should be okay. That being said I don't exactly know the GCP setup at the moment so I am gonna to leave this open for a while until we figure out some of the styling changes and whatnot we need and then we'll make sure this is okay to merge. 👍

for GCP we would probably re-tag the final docker container and push it into google's artifact registry

decided to use google cloud artifact registry instead of github container registry


remove unused android support library import

Summary
Remove unused Nullable import from Android Support Library, that cause build failures on React Native 0.60+
Test Plan
What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Checklist

[ ] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

this pr should be landed and published :+1:


Error:Execution failed for task ':example:processDebugResources'. > Error: A library uses the same package as this project: com.ford.openxc.webcam

Hi Folks,
After building this project I am getting this error.Even I changed the package name, but still getting this error.Please provide me the solution.
Thank You!

Hi,
Thank you for the help. can you please mail me the* .apk* file.So i tested
once, it is helpful for me in testing before building the code & making
changes. Please do the needful.
On Fri, Sep 29, 2017 at 9:00 AM, 蒋朋<EMAIL_ADDRESS>wrote:

@mirzaaqib https://github.com/mirzaaqib Android Studio version here:
https://github.com/jp1017/AndroidUvcDemo
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/openxc/android-webcam/issues/25#issuecomment-333022322,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASvYuyMJV0mE3Pmx-1_7IaeshgX9ADXMks5snGROgaJpZM4PiUqQ
.

--

Hi,
I face some problem with setting in android studio and eclipse. Could you give me apk file for testing?
Thanks alot


Pylance does not recognize imports under certain conditions

Environment data

Language Server version: 2023.6.20
OS and version: Ubuntu 20.04.6 LTS
Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.10

Other version info that may be important:

Visual Studio Code version: 1.79.2
Python plugin version: v2023.10.1

Code Snippet

Code libraries attached
Repro Steps

run make on test2
run make on test1
Activate test1's venv, and set the interpreter if needed.
run pip install ../test2 from test1
run pip install -e . from test1
Open test1/folder/subfolder1/subfolder2_1/failed_pylance.py

Expected behavior
Pylance correctly recognizes folder.subfolder1.subfolder2.printer as a valid import
Actual behavior
Pylance recognizes folder.subfolder1 as an import, but doesn't see subfolder2.printer.
This behavior persists through recreating the virtual environment, deleting all artifacts, and running Python: Clear Cache and Reload Window.
Logs

Logs attached
pylance_import_test.zip
pythonLanguageServer.log
Edit: Added venv activation

If you haven't already done so, please look at the troubleshooting for editable installs documentation.

Yeah, I checked that out before posting this. I first got this issue in a more mature codebase. Pylance worked for a time by downgrading to (I think) 2023.5.20 but that eventually stopped working as well.

The problem is that your code is dynamically (at runtime) manipulating the __path__ variable. This won't work for static analysis tools like pylance. It looks like the module is implementing a namespace package using an archaic technique. This technique is no longer required as of Python 3.3. PEP 420 introduced the notion of an "implicit namespace package". This technique doesn't require the dynamic manipulation of __path__, and pylance is fully compatible with this approach.

I just spent some time with my actual codebase and verified that my use case was working with Pylance v2023.5.30 and no longer worked in v2023.5.40. Verified this was the behavior in my dummy code too.

We recently fixed some bugs that resulted in incorrect import resolution when using PEP 420-style implicit namespaces. If this happened to previously work for you, that was by accident and could be explained by these bugs.
If you want your project to work with static type analysis tools, I recommend that you eliminate the old code that performs dynamic manipulation of __path__. Such techniques were required for Python 2.x, but PEP 420 (which was accepted in 2012 and implemented in Python 3.3) has eliminated the need for these techniques.

Thanks. I've updated the title based on our thread so that other people searching might find it easier. We'll update our codebase to use the modern syntax and in the meantime continue to use the older version of pylance.