Error while installing 'Flutter' extension. Please check the log for more details.

Type: Bug
So I enabled experimental settings profiles feature and now I am trying to install flutter extension in new profile but it gives this error. Also one more extension is giving similar error! It says in logs something like this:
Unable to resolve nonexistent file 'c:\Users\Administrator.vscode\extensions\johnpapa.winteriscoming-1.4.4'
Winteriscoming was a theme but it is not even installed in current profile!
I am not sure why I am unable to install certain extensions from marketplace. I don't want to do manually!
VS Code version: Code 1.72.2 (d045a5eda657f4d7b676dedbfa7aab8207f8a075, 2022-10-12T22:15:18.074Z)
OS version: Windows_NT x64 10.0.19043
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz (4 x 2594)

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

Load (avg)
undefined

Memory (System)
11.85GB (3.39GB free)

Process Argv
--crash-reporter-id a0fbb6bd-fff4-43a7-8ec6-e229505b6ad2 --crash-reporter-id a0fbb6bd-fff4-43a7-8ec6-e229505b6ad2

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

flutter-snippets
ale
3.0.0

flutter-stylizer
gml
0.1.16

vscode-flutter-files
gor
4.4.2

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vsccc:30566497
pyindex848:30577860
nodejswelcome1cf:30587006
fc301958:30595537

So, I changed my DNS and I am able to install extensions but now the webview when I click any extension doesn't load so I am not able to view the extension details!

Also #164551

/duplicate
Seems these two issues are similar


ReferenceError: _ApiClient is not defined - when run the first time

Using node 5.3.0, npm 3.7.1 on OSX 10.10.5. I got the error in the subject line the first time I used:
git clone ...
npm install
npm run dev

The second time I used npm run dev everything worked as expected. Here's a pastebin of the npm install / npm run dev session http://pastebin.com/DmvVFn5Q
I'm probably OK for now, but thought I should report this initial difficulty.

#965 #941 #14
@richb-hanover
Please search issues before post new one.

You're right - I had not searched the other issues, for which I'm sorry. But...
Has it been solved or not?
I don't mean to be snarky. But I'm looking for a base for a new project. I'm reluctant to consider a starter kit that seems to generate an error right out of the box... On the other hand, I did get a response ~30 minutes after my original post, so it sounds as if there's a community around the project that could help me again...
Any advice for me about using this as a base?

This project is almost the best starter kit for React Redux web project. I have searched & compared & tried many famous projects on github.


Try moving to lazy bytestring for rendering

Since warp responds with a bytestring, I figure it'll make rendering faster if it's a bytestring all the way through.
The tricky part is making sure this works nicely with OverloadedStrings, so that users still have a nice experience.

Well I tried it in #112, and it's actually slower for a simple render test?
With the move to lazy bytestring (run twice):
purview> benchmarks
Running 1 benchmarks...
Benchmark purview-perf-test: RUNNING...
benchmarking render/todo example
time                 7.905 ns   (7.686 ns .. 8.041 ns)
                     0.997 R²   (0.997 R² .. 0.998 R²)
mean                 7.589 ns   (7.512 ns .. 7.695 ns)
std dev              320.0 ps   (241.8 ps .. 378.4 ps)
variance introduced by outliers: 67% (severely inflated)

purview> benchmarks
Running 1 benchmarks...
Benchmark purview-perf-test: RUNNING...
benchmarking render/todo example
time                 8.056 ns   (7.978 ns .. 8.097 ns)
                     0.999 R²   (0.998 R² .. 0.999 R²)
mean                 7.742 ns   (7.616 ns .. 7.871 ns)
std dev              401.1 ps   (384.0 ps .. 409.2 ps)
variance introduced by outliers: 76% (severely inflated)

Without / as main is right now:
purview> benchmarks
Running 1 benchmarks...
Benchmark purview-perf-test: RUNNING...
benchmarking render/todo example
time                 6.392 ns   (6.196 ns .. 6.554 ns)
                     0.997 R²   (0.996 R² .. 0.999 R²)
mean                 6.165 ns   (6.106 ns .. 6.262 ns)
std dev              246.6 ps   (147.9 ps .. 348.5 ps)
variance introduced by outliers: 65% (severely inflated)

purview> benchmarks
Running 1 benchmarks...
Benchmark purview-perf-test: RUNNING...
benchmarking render/todo example
time                 5.681 ns   (5.476 ns .. 5.939 ns)
                     0.993 R²   (0.992 R² .. 0.997 R²)
mean                 5.956 ns   (5.843 ns .. 6.029 ns)
std dev              303.5 ps   (191.8 ps .. 404.9 ps)
variance introduced by outliers: 76% (severely inflated)

So literally: eh!  Not worth it and possibly a regression?


Add contact information for OpenAPI generation

Description:
Introduced email, and description fields to the openapi ServiceInformation for capturing the contact information in the generated directory.
public type ServiceInformation record {|
    ...
    string email?;
    string description?;
|};

openapi: 3.0.1
info:
...
  description: "This service provides the capabilities to convert an amount from one currency to one to many different currencies."
  contact:
    email<EMAIL_ADDRESS>

Close with the favour of https://github.com/ballerina-platform/openapi-tools/pull/1731


feat: Notifications system redesign

PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #10090
[x] Closes #10109

Needs QA check

@kodadot/qa-guild please review

Needs Design check

@exezbcz please review

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI;

new design

friendly error messages

@Jarsen136 added #10109 pls re-review
thanks

seems ok :white_check_mark: :

lacking background color(massmint mobile warning) :x: :

nice :white_check_mark: :

mobile seems good: :white_check_mark:

cancelling a transfer:  (maybe here change it to Transaction was cancelled like it is on drops?)

hover on warning working properly

was not able to reproduce a critical one but let's go, nice work!

Why does the first case has 2 diff styles

@vikiival did not specify the style yet, will be followup

@vikiival did not specify the style yet, will be followup

Ah so

cancelling a transfer:  (maybe here change it to Transaction was cancelled like it is on drops?)

yeah and the "report issue" should not be there

lacking background color(massmint mobile warning) ❌ :

this didn't change, checked with @exezbcz and he is ok with having these styles

cancelling a transfer:  (maybe here change it to Transaction was cancelled like it is on drops?)

yeah and the "report issue" should not be there

fixed 9d702b3

@Jarsen136 re-request a review from you by accident, srry


PowerToys Run extended functionality

Thanks for a great app! Lately I've found out few things that'd be cool to be added.
Currently Run can't 'run' for example control panel shortucts like that:

Also accessing system commands like :

It could allow people to use centered taskbar with no windows & search icons on the left which looks dope :D
screenshots are from app called ueli which is also a 'run' type of application https://ueli.app/#/features
If you'd like to see this feature implemented, add a 👍 reaction to this post.

1 ask per request.  System commands are coming in 0.31 which will be released in the next few days.
#6390 for settings.  #2408 for OS commands

1 ask per request.  System commands are coming in 0.31 which will be released in the next few days.
#6390 for settings.  #2408 for OS commands


[Core] Transformer model generator - JavaBean -> Immutable

given in input two types A and B, A following the JavaBean convention, B being immutable with an accessible constructor, generates the Transformer model through JavaPoet.
The output is: TypeSpec (from JavaPoet library)

archived


Update Chapter 3 of the Tutorial

Update Chapter 3 of the Monterrey Tutorial (July 2019) to reflect changes from METplus 2.2 to METplus 3.0

I've gone through Chapter 3.  Most changes are in the METplus section, and I'm not sure about the answers to Exercises 3.1 and 3.2 since the conf file contents and variable names may have changed

I'm done with this Chapter

Closed unless errors are found testing on supporting NCAR, NOAA platforms (#468)


Invalid Library Found in Documents/Arduino/libraries/ArduinoJWT-master

Hi,
I am trying to use your Library, and when I try to add library through Arduino IDE/Library Manager, I get the following error:
"Invalid Library Found in Documents/Arduino/libraries/ArduinoJWT-master"
Can you help me with this issue?
Thanks,
Shab

Zip the src folder as ArduinoJWT.zip then try with that zip and should work


Terminals created in the background by the API will not display/retain any output until the terminal panel is initialized

Upstream issue: https://github.com/sourcelair/xterm.js/issues/266

@dbaeumer FYI you will likely hit this eventually due with background tasks. Output will not be recorded until the terminal panel has been pulled up at least once.

@Tyriar thanks for pointing this out. Yes, would not be nice since we would loose output parsing...


PyPI publish on release

Fixes #988 .
Take two of publishing to PyPI. This builds on #1099 .
This PR introduces a completely new workflow called publish (original isn't it?). This new workflow is triggered by a release. The python-package also has a separate job to build the sdist.
Compared to #1099 , the publishing is no more triggered by pushing tags.
The release process would look like this:

Merge all PRs that needs to go into the release.
Create a pull request for bumping the version to the one we want to use for the release, add changelog, etc.
Merge PR from step 2 and wait for the build to finish.
If we want to test the release, now it's time. We can use maintainers/download_gha_artifact.py to download the wheels locally and manually upload them in https://test.pypi.org if we want.
Once the artifacts are confirmed to be working as expected, we can tag the commit that resulted from the merge at step 3.
Push the tag.
Create a release in Github.
The new publish workflow will kick in. It will download the artifacts from the tag associated to the release and upload them to https://pypi.org.
Now bump the version to the next version and a .dev... at the end.

I tested all this in my OpenTimelineIO fork. You can see the commit that I used for the tag (v0.14.0.dev5) here and the actual release here. The release can be seen here
This PR also introduces a script to download wheels from a build. Handy if you want to upload wheels in https://test.pypi.org for example. The script by default only requires to pass the commit hash (the full length one) and a GitHub Personal Access Token.
./maintainers/download_gha_artifact.py <commit hash> <your token>

Additional parameters can be used to set the workflow name from which to download the artifact., the artifact name and the directory where the artifact will be extracted to.
The output looks like:
Found workflow:
  Name:       OpenTimelineIO
  Branch:     pypi_upload
  Commit:     7c521b04a50df40596feae0c2802be7ff3198a16
  Committer:  {'name': 'Jean-Christophe Morin', 'email'<EMAIL_ADDRESS>  Run Number: 87
  Status:     completed
  Conclusion: success
  URL:        https://github.com/JeanChristopheMorinPerso/OpenTimelineIO/actions/runs/1356958062
Getting list of artifacts
Downloading 'wheels' artifact and unzipping to 'dist'
Writing 'jcmorin_OpenTimelineIO-0.14.0.dev5-cp27-cp27m-macosx_10_9_x86_64.whl' to 'dist/jcmorin_OpenTimelineIO-0.14.0.dev5-cp27-cp27m-macosx_10_9_x86_64.whl'
... truncated for the purpose of the PR description

I hope this covers what we discussed in the last TSC meeting. If not let me know and I'll adjust.

I propose we get an hour on the calendar, go through the workflow once with the TSC, and commit this, ASAP.

Makes sense. I'll let the TSC coordinate?
Also thanks @tin2tin for the time you took to test:)


ParameterFunction instances lack name

In holoviews, we often need to get hold of the name of a  ParameterizedFunction class (call it func). This is normally done using func.__name__ which works fine...unless you create an instance.
Once you create an instance __name__ no longer exists; working around this in holoviews would be extremely awkward and unwieldy. What I want is for instances to behave in a similar way to the original parameterized function - i.e. supply __name__.
In addition I would like the ability to set a new, custom name. Here is the diff to instance (in parameterized.py) that does what I want:
diff --git a/param/parameterized.py b/param/parameterized.py
index fa8ec29..92d8990 100644
--- a/param/parameterized.py
+++ b/param/parameterized.py
@@ -1719,6 +1719,8 @@ class ParameterizedFunction(Parameterized):

         inst=Parameterized.__new__(cls)
         Parameterized.__init__(inst,**params)
+        if 'name' in params:  inst.__name__ = params['name']
+        else:                 inst.__name__ = self_or_cls.name
         return inst

     def __new__(class_,*args,**params):

Alternatively, I can imagine changing instance so it accepts an optional argument instance_name:
   @bothmethod
    def instance(self_or_cls, instance_name=None, **params):

That way you could supply a customize name, with __name__ on the instance set to the source class __name__ by default (i.e. if instance_name is None).

That diff looks fine to me; I can't think of anywhere we are assuming that a ParameterizedFunction instance has no name.
--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Comitted in 2501b49e


[Infra] Favor SWIFTPM_MODULE_BUNDLE macro over C function in RC unit tests

Context
The name of the C function used to access the resource bundle is incorrect. I suspect the C function name changed as a result of reorganizing the target over time. I suggest the SWIFTPM_MODULE_BUNDLE macro as it is more future proof.
This was reproducible running swift test --filter FirebaseRemoteConfigSwift on master. I'm not sure how this didn't surface earlier.
#no-changelog

@paulb777, I think it has something to do with the difference between Xcode's SPM and regular SPM. I recall now that the C function is named differently!


[Bug]: connection refused:localhost 27017

Is there an existing issue for this?

[X] I have searched the existing issues

Description
stop 1.9.9 docker contanier
and run 1.9.10 image base on 1.9.9 volume,it show can't connect to mongodb

Steps To Reproduce
1、stop v1.9.9 docker contanier
2、and run v1.9.10 image base on v1.9.9 volume,it show can't connect to mongodb

Public Sample App
No response
Environment
Production
Issue video log
No response
Version
1.9.10

@wengad82 can you please share the full logs? Checkout this doc - https://docs.appsmith.com/learning-and-resources/how-to-guides/how-to-get-container-logs

Have you tried using host.docker.internal instead of localhost or <IP_ADDRESS>?


Progress Bars violate CSP style-src directive unless directive has 'unsafe-inline' in it

I see this in the docs for v3.3.5 but I'm using an older 3.x version and see the behavior in my application.
From the docs: http://getbootstrap.com/components/#progress
<div class="progress-bar" role="progressbar" aria-valuenow="60" aria-valuemin="0" aria-valuemax="100" style="width: 60%;">

That last attribute, the inline style, causes a CSP violation for me (and I assume anyone else using an effective CSP policy, since 'unsafe-inline' is considered, well, unsafe).
A bit of searching helped me find an existing workaround for this issue: https://github.com/danielnixon/bootstrap-hacks/blob/master/progressbar.css
One thing to note is that I had to do a round on my percent values in order to make the bootstrap-hacks package work properly (e.g. aria-valuenow="50.0" doesn't work but aria-valuenow="50" does).

That hack (add 100 declarations, one for each percentage point) is pretty gnarly; probably too gnarly for us to pursue.
attr() would be the obvious way to address this, but its browser support seems pretty lacking (https://developer.mozilla.org/en-US/docs/Web/CSS/attr#Browser_compatibility , https://github.com/Fyrd/caniuse/issues/1209). So this might be a WontFix situation.
CC: @mdo

An option a co-worker suggested to me ( @RobertWHurst ) was to put the style code into JS.

As JS is needed anyway to make the progress bar actually work, this may be an option. My preference for v4 would be to use actual <progress> in the markup, styled as much as possible with CSS, and then gently polyfill it (replacing it with a styled <div> with relevant aria-* attributes in browsers that don't natively support <progress>)

So this might be a WontFix situation.

I'm in favor of that.

then gently polyfill it (replacing it with a styled  with relevant aria-* attributes in browsers that don't natively support )

Woof, sounds like a lot of overhead for not a lot of gain.

Modals with the .fade class also trigger an error when CSP is active (causing the modal to fail to show and scripts to stop working requiring a page reload). This wasn't a problem in v3 and seems to be caused by the reflow function trying to eval() and inject javascript in the page. The temporary solution I've found is to remove the fade class and use other means to achieve the transition. I'm still trying to figure out a better way though, which can work out of the box.

I propose documenting this and deeming it WontFix: #18080.

As JS is needed anyway to make the progress bar actually work

Eh, not really, IMHO. Progress bars that are only updated on page load are a thing.
E.g. "[progress bar goes here] You are 75% done answering this survey. Here's the next set of questions:"

If you set the element's width through JavaScript it wont violate the CSP policy:
element.style.width = '30%';


Catalogue Services Special Treatment

typical GeoNetwork problem
[info] s.LuceneService - Loading data from CSW http://geodata.govt.nz/geonetwork
/srv/en/csw
[debug] s.LuceneService - Response status: 200 - OK
[debug] s.LuceneService - Response Content Type: Buffer(application/xml;charset=
UTF-8)
[debug] s.LuceneService - Response-Length: 112
[warn] s.LuceneService - Unknown response content. Body: <response>
  <info>No 'request' parameter found</info>
</response>

 [info] s.LuceneService - Loading data from CSW http://dc.niwa.co.nz/niwa_dc/srv/
eng/csw
[debug] s.LuceneService - Response status: 200 - OK
[debug] s.LuceneService - Response Content Type: Buffer(application/xml;charset=
UTF-8)
[debug] s.LuceneService - Response-Length: 112
[warn] s.LuceneService - Unknown response content. Body: <response>
  <info>No 'request' parameter found</info>
</response>

You just had the wrong URLs. See GetCapabilities for the Servers. For NIWA it has to be "https" not "http". GeoGovt it's /eng/ not /en/. If thats just weird config of the servers or our fault (because it is in the GetCapa) I leave to others to decide :-)
I opened a new Issue for "Parse GetCapa" #11


Milestone 1 Ponder Source RfP

Article by Manuel
my blog post
longer blog post (1a: "Definitions, Examples, Privacy and Security, Federation Protocol specification")
framing specific for task tracking (1c: "Investigate feasibility of supporting multi-homed data among federated systems without formal CRDT")

RfP amount should be 9700 euros (7000 for our part in 1a and 2700 for 1c)

Also https://github.com/federatedbookkeeping/research/issues/42 - this is coming from schema change across time instead of from data portability across systems, but the six challenges are well formulated and a great test for our theory in this milestone.


[NBS] Implement CSI driver for NBS

DoD:

using kubectl you can run pod with container with attached NBS-volume as a nbd device.
using kubectl you can run pod with container with QEMU with attached NBS-volume via vhost.
using kubectl you can create NBS-volumes from images

Implemented prototype.
Kubectl can run a pod with a container, and CSI driver forward a vhost unix socket to this container for qemu running (for kubevirt).
Also Kubectl can run a pod with a container, and CSI driver attach NBS-volume to container as nbd device (for infrakuber).
https://github.com/ydb-platform/nbs/pull/455

Next steps:

start endpoint with a connected nbd-device (NBS)
attach QEMU to vhost socket using kubevirt (Core)
add tests for CSI driver https://kubernetes-csi.github.io/docs/testing-drivers.html (NBS)
install YDB, NBS, CSI-driver in kubevirt_testing cluster


Error when trying to Install SIFT CLI #610

sudo sift install
<EMAIL_ADDRESS>sift-version: notinstalled

mode: desktop
downloading v2023.02.06

    downloading sift-saltstack-v2023.02.06.tar.gz.asc
    downloading sift-saltstack-v2023.02.06.tar.gz.sha256
    downloading sift-saltstack-v2023.02.06.tar.gz.sha256.asc
    /snapshot/sift-cli/sift-cli.js:357
    throw new Error(res.body)
    ^

Error
at Request. (/snapshot/sift-cli/sift-cli.js:357:17)
at Request.emit (events.js:400:28)
at Request.onRequestResponse (/snapshot/sift-cli/node_modules/request/request.js:1059:10)
at ClientRequest.emit (events.js:400:28)
at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:647:27)
at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
at TLSSocket.socketOnData (_http_client.js:515:22)
at TLSSocket.emit (events.js:400:28)
at addChunk (internal/streams/readable.js:293:12)
at readableAddChunk (internal/streams/readable.js:267:9)
at TLSSocket.Readable.push (internal/streams/readable.js:206:10)
at TLSWrap.onStreamRead (internal/stream_base_commons.js:188:23)
Thank you in advance for your help

Hi @lbudino , when @ekristen recommended for you to use Cast in place of the deprecated sift-cli, the intent was for you to download and install cast from here and use this to install SIFT.
You can find the commands to install SIFT using cast on the main page of the SIFT repo.
Cheers!

Hi @digitalsleuth, I am trying to install SIFT on VM (Ubuntu 22.04) with help of CAST. After 50 mins of installation it is showing Low disk space Filesystem root. I was trying this in Ubuntu-20.04 but facing same issue.
I have 52 GB free space but not able to resize it.

Hi @Devops-sudarshan , this isn't a Cast issue, and since you've already opened an Issue for this in the teamdfir/sift Github, I'll respond there.

Your root partition is only 13GB, you do indeed have 52GB of freespace but you have to expand your partition to include that space.

This isn't an issue with cast or sift, so I'm going to close this out.


Proxy + filter plugin?

1. What version of Caddy are you running (caddy -version)?
0.9.5
2. What are you trying to do?
Does the proxy directive work together with the filter plugin?
I setup Caddy as a proxy and have to rewrite some html content coming back from the upstream server. The filter plugin sounds like being able to rewrite content, but it seems to not kick in with the proxy. Is this possible somehow, or am I using it incorrectly?
3. What is your entire Caddyfile?
:1234 {
  filter rule {
    content_type text/html.*
    search_pattern Foo
    replacement Bar
  }
  proxy / http://www.foo.com {
    header_upstream Host www.foo.com
  }
}

4.  Please paste any relevant HTTP request(s) here.
open http://localhost:1234
6. What did you expect to see?
Bar
7. What did you see instead (give full error messages and/or log)?
Foo
8. How can someone who is starting from scratch reproduce the bug as minimally as possible?
Use Caddyfile from above, and start a caddy server w/ filter plugin.

Hey @larskluge, thanks for your question! But I think you'll have more success asking in the filter plugin's issue tracker: https://github.com/echocat/caddy-filter

Fair enough, will ask over there. Thanks @mholt


feat: Add properties story

This adds a properties story in storybook.
Closes #718

However, looks like this poses an issue to the linter:

Not sure if this is correct, but what happens if you give the linter what it wants?

Not sure if this is correct, but what happens if you give the linter what it wants?

To explain why this is bad idea, Storybook is not a run time dependency so should be listed in devDependencies. The linter doesn't realize Stories are special files that aren't in the production build.


Add prettier and reformat everything

As we discussed, added prettier with simple config, reformatted the sources and added a pre-commit hook to ensure prettier is always applied.
Any pending commit requires:

add prettier
yarn add prettier --dev --exact
format everything
node_modules/.bin/prettier --single-quote --trailing-comma es5 --ignore-path .gitignore --write 'app/**/*.js' 'addon/**/*.js' 'tests/**/*.js'

Before attempting to rebase on master.
Check it out and let me know what do you think.

pre-commit hook

I kinda hate these 😡 .  I think we would be better served to hook this into .eslintrc.js and use linting to enforce prettier in CI.

For example: https://github.com/emberjs/ember-test-helpers/blob/master/.eslintrc.js

Removed the pre-commit hook and configured ESLint.

Hm, fixed.

ok so

this is great, definitely like having automated formatting
some of the default config isn't great, if possible we should see if it could be fixed, to wit

leading . sucks (although it seems there is no config for trailing . at the moment)
expanding braces for trivial one-line early returns is an unfortunate waste of space.  If we can somehow configure that away it would be nice, but if not, oh well
that arrow expressions with method chains results in an immediate break leads to some really weird expressions for single-var arguments: see https://github.com/hjdivad/ember-m3/blob/ded129bc3eeeef3c6f12e5b0c76b1a85fb498706/tests/pages/index.js#L28-L33

also it looks like the git precommit hook is gone, which is good.  We are definitely not adding a precommit hook ^_^

none of the issues are significant enough to block the pr though

@hjdivad you have to choice the config from the following:
what is the formatting width
whether to add semicolons
use single or double quotes
indention space
whether to add trailing commas
use tabs instead of spaces
I think the prettier philosophy is to not allow configs and achieve something like the Go's community where there is single format for all Go code.

@dnachev yep that's a pity but as I said above, I'd still rather have automatically formatted code than manually formatted code.

I've restarted the builds since the failures looked to be just from the SETUID chrome sandbox issue.


(role/atshcu) add udev rule for /dev/gpiochip*

I guess this is fine, assuming it will be a no-op on RHEL7?

Correct. There will be no char device to match the name pattern, so nothing will happen.

Actually, now that I think about it, shouldn't this be part of the ccs_hcu module?

@glennmorris I feel like this is really in role/profile territory.  We are going to use the same udev rules for rpis so I think I'm going to turn this into a profile class.

This has been reworked to add a new profile::core::gpio profile.


Fix rendering tests

🦟 Bug fix
Targeted at https://github.com/gazebosim/gz-gui/pull/429
Summary
The tests below are still failing on Jammy github actions in https://github.com/gazebosim/gz-gui/pull/429:

INTEGRATION_transport_scene_manager
INTEGRATION_minimal_scene

The failing tests were supposed to be fixed by https://github.com/gazebosim/gz-gui/pull/535 but for some reason they are now happening again.
The "fix" is more of a workaround. The main change is to not unload the render engine on exit which is what's causing the segfault in these 2 tests. It's safe to remove the DestroyScene call in the tests as that's taken care of by the minimal scene plugin. The tests do not fail on other CI builds and I'm also not able to reproduce them locally.
We could either get this in to make CI green or spend more time finding the root cause of the problem.
Checklist

[x] Signed all commits for DCO
[x] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Do you think it's worth figuring out why unloading the engine fails?

I created https://github.com/gazebosim/gz-gui/issues/565 for this. I'll look into it as a background task.


Fix #1 by preloading libgcc_s.so.1

Fixes #1.

Nit: The commit message seems a bit unclear. IMO something like "Preload libgcc to avoid problems with pthread_exit" would be better


API documentation

should document things like setReplacementDac, possibly outlining its role in Chunity vs webchuck (e.g., we are not using it in webchuck, but this may be needed for Chunity)

closed with #14 #17


Unreadable text in dark mode with "Colorize by" options

I'm using dark mode and selected one of the "Colorize by" options. This leaves the text as white on very light backgrounds for the graph nodes, which is unreadable.

Fixed (finally!)


[Bug]: adding proper routes to the view reviews on listing page rendered from admin's dashboard

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
Right now, their are no proper links or routes to direct the proper page for show views button.
Expected behavior
When user click on the button proper page will be render to view the reviews for the individual listings.
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@dipexplorer can you give progress of #275 changes which i had mentioned

@dipexplorer can you give progress of #275 changes which i had mentioned

@Soujanya2004
I am working on that functionality, focusing on the environment variable check in admin.js to enhance security. Now I am raising an issue for that and also raised the PR shortly.

@dipexplorer sure, i will give you username password and email which has to be admin credentials


Added New Webapp

Codecov Report

:exclamation: No coverage uploaded for pull request base (beta@2b4cd3e). Click here to learn what that means.
The diff coverage is 85.14%.

@@           Coverage Diff           @@
##             beta     #129   +/-   ##
=======================================
  Coverage        ?   86.62%
=======================================
  Files           ?       31
  Lines           ?      501
  Branches        ?        6
=======================================
  Hits            ?      434
  Misses          ?       67
  Partials        ?        0

Impacted Files
Coverage Δ

...oooo/atcoder/runner/SubmissionScrapingRunner.scala
100% <ø> (ø)

...end/src/main/scala/com/kenkoooo/atcoder/Main.scala
0% <0%> (ø)

...scala/com/kenkoooo/atcoder/common/JsonWriter.scala
100% <100%> (ø)

...com/kenkoooo/atcoder/common/SubmissionStatus.scala
100% <100%> (ø)

.../scala/com/kenkoooo/atcoder/common/Configure.scala
100% <100%> (ø)

...kenkoooo/atcoder/model/ProblemSubmissionPair.scala
100% <100%> (ø)

...o/atcoder/runner/AllSubmissionScrapingRunner.scala
100% <100%> (ø)

...atcoder/runner/NewerSubmissionScrapingRunner.scala
100% <100%> (ø)

.../main/scala/com/kenkoooo/atcoder/api/JsonApi.scala
100% <100%> (ø)

...la/com/kenkoooo/atcoder/common/ReducedRanker.scala
100% <100%> (ø)

... and 21 more

Continue to review full report at Codecov.

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


TypeError: value.includes is not a function on passing custom fetch

Describe the bug

When passing a custom fetch to typescript-react-query I gave the following error:

To Reproduce
Steps to reproduce the behavior:
With the following configuration:
overwrite: true
schema: "[url]"
documents: "**/*.graphql"
generates:
  libs/backoffice/api/graphql-schema.ts:
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-react-query"
    config:
      fetcher:
        func: ./libs/backoffice/api/graphql-client.ts#fetchData

My GraphQL schema:

# Put your schema here

My GraphQL operations:

# Put your operations here

My codegen.yml config file:

overwrite: true
schema: "https://dev-api.yacooba.live/graphql"
documents: "**/*.graphql"
generates:
  libs/backoffice/api/graphql-schema.ts:
    plugins:
      - "typescript"
      - "typescript-operations"
      - "typescript-react-query"
    config:
      fetcher:
        func: ./libs/backoffice/api/graphql-client.ts#fetchData

Expected behavior

Environment:

OS: MacOS Big Sur 11.1
"@graphql-codegen/cli": "1.20.1",
"@graphql-codegen/introspection": "1.18.1",
"@graphql-codegen/typescript": "1.20.2",
"@graphql-codegen/typescript-graphql-request": "^3.0.1",
"@graphql-codegen/typescript-operations": "1.17.14",
"@graphql-codegen/typescript-react-apollo": "2.2.1",
"@graphql-codegen/typescript-react-query": "^1.1.0",
NodeJS: v15.3.0

Additional context

@vitorcamachoo can you please try
    config:
      fetcher: ./libs/backoffice/api/graphql-client.ts#fetchData

?

Closed due to inactivity. Feel free to create a new issue if the problem persists.


error: unsupported class file format of version 52.0.

Hi
I am using JDK 8 and javac -1.8. I also tried with JDK 11
I try to convert the file to a .CAP file but every time I run ant I receive the following error : error:  unsupported class file format of version 52.0.
Here is a snippet of my error :

Also, here is a snippet of my build.xml.  I tried several versions of the SDK.

Thank you!

Only post text logs please. No screenshots. Also look at samples in https://github.com/martinpaljak/ant-javacard/blob/master/tests-1.8.xml and I recommend to start again from scratch. If you don't need any options, don't specify them or you have to know what you are doing.
You can see targeting information and which SDK to use with which JDK here: https://github.com/martinpaljak/ant-javacard/wiki/Version-compatibility

Hello @Bianca988 ,
I got the same issue during convert phase.
This is linekd to the java compiler version used.
You can force the correct Java version during compilation using 'target' option.
With JCDK 3.0 I force the target to 6 for javac compile rule as below:
<javac srcdir="./src" target="6" includes="**/*.java" destdir="${build.classes}" classpath="${jc.jar};${jc_ETSI_TS_102.241.jar}"/>

Hello @HColt
Thank you for your reply. I understand what you are saying. Due to the fact that I already tried a lot of things ( some of them bad ) for that file and @martinpaljak's answer, I decided to start from scratch. It worked and I didn't even receive that error again. I will keep your advice in mind though.


new package: inotify

Please create a package for inotify

http://www.phoenixframework.org/docs/installation#section-inotify-tools-for-linux-users-

Isn't inotify already in the repo? I am using
run.config:
  engine: elixir

  dev_packages:
    - inotify-tools-3.14

and it works fine!


Better way to build project

Since we already updated webpack to v4, I think we needn't build bundle assets every time we build Android or iOS.

Develop: Run npm run watch in terminal and webpack will build for changes very quickly, and this will speed up Android and iOS build
Build for deploy: Run npm run build in terminal, webpack will generate minimal version for us, which make the installation package smaller

/cc @chrisgarrity


Reinstate Docker Swarm tutorial

it's pretty out of date and doesn't work.
Look at this: calico/node:v0.4.9  <-- from before the dinosaurs roam the 🌍
http://docs.projectcalico.org/v2.0/getting-started/docker/tutorials/docker-swarm

Might also be worth adding a vagrant demo for this

The swarm install doc has been removed by #285 .

@djosborne depends on the v2.0.1 timeline, but I'm hoping it should be a day worth of work (getting it working + updating the docs)

This is blocked on actually supporting Docker 1.12.0+ in swarm mode.


array key property

I'm trying to iterate through an array of items with
 but when I set a key property on

{
this.state.users.map((user,index)=>{
                    return
  ...
;
})
}

I have following error:
Warning: Unknown props `inHeader`, `responsiveTable` on
 tag. Remove these props from the element
and
Warning: Unknown prop `columnKey` on  tag. Remove this prop from the element.
When there is no key react will complain
Each child in an array or iterator should have a unique "key" prop.

Hey @neuronetio, you should be able to iterate with key props without warnings now. I just updated the example to use key. Let me know how it goes. 🙌🏻


Current transform/filter customized debug message for each filter

This can be done inside the closure created in Fly.proto.filter.
This is only visible when running with the DEBUG env.
DEBUG="fly*" fly ...

:airplane:  080e84bf348a3b3d485dd78e28e615062748d5ae


Introduce pre-commit-hooks

I think we should start using pre-commit-hooks as for example HA does!
See https://github.com/home-assistant/core/blob/dev/.pre-commit-config.yaml for reference
That way we could have nice things like black formatting, pylint or ruff for linting, isort for nice import order, and autoflake to remove unused imports and variables.
That way we can fix issues before we push code and GH actions show that there are improvements necessary.
Optinions?

Yes, having pre-commit hooks might add additional convenience. Since it can be disabled / ignored locally, we still need the important checks in in the CI/CD pipeline.
Should we just copy the essential stuff from Home Assistant?

Yes, that was my intention. I work on it right now, but I think I went down a deep rabbit hole 🙈

setup.py -> legacy, should be replaced with pyproject.toml
pyproject.toml -> looking at HA's pyproject.toml, jeez what are all these settings 🤯

A lot to cleanup I guess, maybe we should tackle that in a first PR and after that's done start with the pre-commit-hooks

@Bouni Any help you need here? I guess you're working on this already in the background and have already prepared some changes? Looking forward to those changes ;-).

I worked on this last week. The biggest issue is that I need to change many thing in order to get the pre-commit hooks to be statisfied 😆
I tink I'll add them commented out in the first place, then we can "activate them" one by one and change the necessary files. Otherwise we end up with a giant change set.
One more thing, I would really like to add black as the first pre-commit hook becuase that will solve a lot of ruff/pylint warnings/errors because it wraps long lines for example.
Are you ok with that?

Yes, for me that is totally fine and having black as pre-commit hook is also okay.
However I would not like to have automatic rewritting of code as part of the pipeline, i.e. we could run black only in some kind of reporting mode when we integrate it into the pipeline.
The "problem" with pre-commit is, that its more of a "nice-to-have", and not mandatory. So not everyone will execute it when submitting PRs.

We could run black with the --check flag: https://black.readthedocs.io/en/stable/usage_and_configuration/the_basics.html#writeback-and-reporting
but to be honest, I run black on almost all my projects and it never produced code that didn't work afterwards.
So in my opinion we could run black as a pre-commit hook in write mode, but if you still insist, I'm also fine with --check

It's fine to have it in pre-commit. I would argue to not add it in "rewrite mode" in the CI/CD pipeline. I saw projects doing that and committing code to the repository that no one has seen.

I did a quick test, and it seems to work with --check:
black................................................(no files to check)Skipped
[pre-commit d960df1] Adjust regex
 1 file changed, 1 insertion(+), 1 deletion(-)

But its rather pointless to run black in read only mode as I think more about it. The sole purpose of black is to take away the need for the programmer to fully format the code nicely.
When having black as a pre commit hook we could achive a contant code format quality level. Then e could add a GH action with black in read only mode so that the check fails if someone submits a PR without the proper black formatting.

😆 Oh snap, I was just a few seconds to late with my answer. Ok so I will have black in write mode in the pre-commit-hooks and will supply a PR for CI/CD with a read-only check.

Whta do you think of a PR that has black ran over all source files in order to get them to a level from where we can continue?

Also fine with me, should we do it along with #81 or afterwards in a new PR?

I think we could do it in the same PR, give me a second


Bright Disputes - Milestone 2

Delivery document for Bright Disputes - Milestone 2

Hi, I'd just like to check if everything's ok with our submission, is it visible for review? If so, when could we expect the evaluation? Thank you!

yes, we see the delivery!
The curators will review it soon, thanks

@bufta Hey, maybe this week or next depending on when @DoubleOTheven and I have time. Sorry, we're not the quickest with these reviews 😅

Hi, hope all is well. Could you kindly let us know when should we expect the reviewers' feedback?

@bufta I'll carve out some time for a review this week

Hey team!
Here's the form for payment details: https://forms.gle/BUCKfygkiEvpdYna6.
Once you've filled it out, please let me know and be sure to specify what it pertains to; you can include the link to this PR delivery! Further details can be provided under the section: "Please describe which Milestone you have completed and attach the link to the Milestone delivery."
Should you have any questions, don't hesitate to ask. Thank you so much!

For guidance on how to set up identity, refer to this guide.

Thank you! I've just filled the form @TtomaS7 👍

Hey @bufta
Can you try to claim the reward by using this guide?
https://scribehow.com/shared/How_to_claim_a_Child_Bounty_reward_on_Polkadotjs__t3V7NDUjQlus40EUjc-5Kw
you only need:
Parent ID - 19
Chain ID - 529

Thank you for the guide @TtomaS7, I followed the steps as described, however I experienced some error while trying to claim the child bounty:

Do you know maybe what could have gone wrong?

Hi @TtomaS7 did you maybe had a chance to check our issue with claiming the payment? Looks like the Child ID could be incorrect, however I could not find the correct one by browsing Polkassembly and Subsquare...

@bufta here is the child bounty info, you'll be able to claim it in seven days 😄

You can claim the reward in 1 day, thank you!
https://polkadot.subsquare.io/treasury/child-bounties/19_546

Thank you @HCastano @TtomaS7, worked this time 🙌


redirect to the correct place

Signed-off-by: Kamal Nayan<EMAIL_ADDRESS>Description
Now they redirect to the correct places.
This PR fixes #323
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

aha was this my first 🌟 but feels too good to see this.


import-style prevents vendoring

I just tried to vendor TUF into pip (in other words embed the tuf sources inside pip sources) and it fails (even with #1160 fixed) because of the import style used in TUF source code itself:
import tuf.download
Using this (instead of relative imports) means tuf needs to be installed to python path for the imports to work.
I've looked at the dozen other projects pip vendors and the system seems to cope with two styles:

Most projects use relative imports like

from . import treebuilders
from .treebuilders.base import Marker

The other method is

from toml.decoder import InlineTableDict

The second style works because vendoring (the tool) modifies import NAME to from vendored.path import NAME and from NAME.module import something to from vendored.path.NAME.module import something. I assume this is mostly done so vendored dependencies of vendored  projects work (so e.g. vendored tuf can "import securesystemslib"). In any case the TUF style cannot be automatically modified as far as I can tell.
I'll try to add reproduction instructions that don't require my pip branch...

Example you can run or have a look at:
git clone https://gist.github.com/22d5f08083c8b7b2f3e552f7ca6c301e.git

The issue is any "submodule import" really, not just internal submodule imports: import securesystemslib.util will be an issue as well

This reads like in order to support vendoring TUF (and securesystemslib) we need to change the way we do imports to either

explicit relative imports (from . import downloads)
importing functions (and other attributes) of a module into the current modules namespace (from tuf.download import safe_download)

All things being equal, I prefer absolute imports – I believe they make the code easier to read and follow. Indeed, I recently rejected a securesystemslib PR which added explicit relative imports (secure-systems-lab/securesystemslib#254), but now I'm wondering if that's the direction we should take?
I certainly prefer explicit relative imports to importing functions from a dependent module into our own namespace.

If the important bit is the complete code namespacing, I suppose that would still be possible if package initialization imported the submodules? As in you could do
import tuf
tuf.download.safe_download(...)

if init.py actually imported submodules (or a reasonable subset of them) . I don't know much about python library design so maybe there's a reason that isn't being done?

Two reasons not to do that today would be clients importing all of the repository logic and everyone who imported tuf would have log handlers modified #1148
If we had a clearer distinction between the client and repository logic, it might make more sense to have the package initialisation import submodules.

If we have to choose between relative imports and importing names (functions, globals, etc)  directly, I too vote for the former. At least this requirement will make it easy to choose an import style convention. :)
@jku, have you checked if we'd need to patch any of TUF's dependencies or transitive dependencies, except for securesystemslib?

All of TUF dependencies are already pip dependencies (so succesfully vendored) except SSL and iso8601 (which is a single file library).

If we have to choose between relative imports and importing names (functions, globals, etc) directly, I too vote for the former. At least this requirement will make it easy to choose an import style convention. :)

I'm researching more clever alternatives as both of these options mean a massive PR: ~700 actual code lines would need to change and the possibility of a namespace mistake is real. I'll try to have a possible solution for discussion by tomorrow.

There's a possible fix in a PR -- it might look like a large change but 70% of it is test changes that are completely optional: I just did those to make them the same style as the actual source.
I'm also speaking to the vendoring maintainer to make sure this is not a misunderstanding (I don't think it is -- it's just impossible for vendoring to handle the current imports)

other points that should maybe be bug reports?

repository_tool, developer_tool and repository_lib could live somewhere where they would not be confused for library parts: scripts/ maybe or a directory of their own?
unittest_toolbox should be moved to tests/

I've been looking at and testing the Draft PR and it works: the patch is reasonable size (most changes are in tests and completely optional), all current methods of importing keep working, and vendoring now works (apart from the securesystemslib imports that would also have to be fixed) ... but I'm not entirely happy:

the circular import (keydb.py: import tuf, __init__.py: from . import keydb) works but it just looks wrong. There were also issues with previous versions of this in python2: I can't promise the other interpreters will be just fine with this
I think defining package default imports(__init__.py) is fine but I'm not as convinced the contents should be defined by the purpose of avoiding code changes within the project source code... This could be avoided by renaming the common import file and doing something like import _internal as tuf

Documenting the core issue and main options for those who are not familiar with it:
Core issue
I'd like to vendor tuf into pip in the near future. Vendoring using the vendoring tool requires changes to the way tuf & securesystemslib do imports.
Options I see available

patch tuf and securesystemslib in pip: Vendoring does support patching so this is a potential stopgap solution for testing (I could use a trimmed down version of this patch). This is not a viable long term solution
avoid major code changes by using a common imports file like in my draft PR to  (see previous comment) or by other ugly trickery like this:

class Tuf:
  def __init__(self):
    from tuf import exceptions
    self.exceptions = exceptions
tuf=Tuf() # voila, tuf.exceptions now works as expected. Also ewww

bite the bullet and modify the code to replace references to tuf.<name> to just local <name>. This is a minimum of 1300 changed lines (counting both tuf and securesystemslib references here, not counting tests)
Fix vendoring tool or find a better solution that does not have this problem (see https://github.com/pradyunsg/vendoring/issues/15 for upstream discussion)

A related finding:
pylint does not understand the tuf import style at least in the unused-imports check: as a result we have some unused internal imports in our code.

We've talked elsewhere about adopting, with minimal modifications, the Google Python coding style.
That style guide recommends either:
import foo.bar
badger = foo.bar.BADGER

or
from foo import bar
badger = bar.BADGER

and explicitly recommends against using relative imports.
I think the second pattern above (from foo import bar) is compatible with vendoring but has the downside of being a fairly significant code change. Am I following correctly?

Yes, that seems correct to me. Bringing the example to TUF context:
Current style
import tuf.download

tuf.download.safe_download(...)

would become
from tuf import download

download.safe_download(...)

That is a big change and cannot be completely automated.
I don't think we have name clashes where a tuf module could be mistaken for another imported package or module... But the change is likely to lead to some local name clashes (in the sense that download might be a local variable already): We might be able to automate parts of the refactor... maybe something like this:

find potential name clashes with some clever grep
manually fix the name clashes first (+ test)
do the import switcheroo with another script
manual review step to find any unusual cases (+test)

Thanks for all the digging, @jku! Based on the from toml.decoder import InlineTableDict example in the PR description, I was under the impression that the symbol after import could not be a module in order to work with vendoring.
If that is not the case, and constructs like from tuf.client import updater are indeed compatible with vendoring, then I lean towards "biting the bullet" and refactoring the imports, so that we stay Pythonic/idiomatic and also align with the Google style guide we want to adopt.
I would only go with any of your proposed trickery, if it makes the refactor substantially easier and we make it very clear that it is only a temporary hack that won't survive the upcoming refactor.

Regarding the other pain points you mentioned ...

repository_tool, developer_tool and repository_lib could live somewhere where they would not be confused for library parts (assuming they are not parts of the library like I think): tuf/scripts/ maybe or a directory of their own?

Agreed but probably not worth to change before the planned refactor? Definitely something to consider together with #1136 and #881. Maybe this warrants a separate over-arching module architecture design issue? Also https://github.com/theupdateframework/tuf/issues/1134#issuecomment-690091176 seems related.

unittest_toolbox should just be moved to tests/

Agreed but IMO low-prio.unittest_toolbox should probably also be subjected to a revision.

download and mirrors should probably be moved to tuf/client/

Agreed but see both comments above and #1135.

pylint does not understand the tuf import style at least in the unused-imports check: as a result we have some unused internal imports in our code.

I know. :/ I've been meaning to at least submit an issue for this for a long time (I will do this right now).  FWIW, I've fixed this a long time ago in in-toto and have created a ticket in securesystemslib, which both adopted their linter config from tuf (see https://github.com/secure-systems-lab/securesystemslib/issues/243).

we are not very consistent in imports: lots of files use e.g. securesystemslib modules without importing them (and trust that someone else is importing them)

I know. :/ I think a sensible linter config would catch this (see above).

Thanks for all the digging, @jku! Based on the from toml.decoder import InlineTableDict example in the PR description, I was under the impression that the symbol after import could not be a module in order to work with vendoring.

right I can see how that was ambiguous. vendoring can cope with any form of from X import Y I believe but the specific limitation is that the local imported name cannot have a dot in it (as from X import Y.Z is not valid). So the local name can refer to anything (module, class, ...) as long as it's just the name "without path".

I've been meaning to at least submit an issue for this [pylint configuration] for a long time

--> https://github.com/theupdateframework/tuf/issues/1178

well this one's done already


AssemblyInfo.cs file absent

Just FYI, the develop branch has AssemblyInfo.cs inside the Portable.iOS project, but it does not exist:

Thanks for the heads up - was missing a BeforeBuild target in the .csproj for Portable.iOS and Portable.MonoTouch. Fixed now.


None of the Kernel8 img  working on Raspberry Pi3

My SD card includes config bootcode start.bin kernel8.img.
The Part3 Tutorial worked but None of the codes in this repository have worked on my Pi3 yet.
A blank screen shows up when the raspberry pi3 is turned on,

Yes there was a bug with screen resolution in AARCH64 which has been resolved


Added commitish as input

In this PR, we would like to add the target_commitish property for creating a release. This is also contained in the original repository here. The problem we want to solve with it, is that the action is always tagging the default branch (main in most cases) but not the branch the action is running on. By providing the target_committish property, you can steer where to put the newly created tag.
Edit: We made the test run through but they need another look. Right now the tests are not bullet proof. The jest mocks are created with the assumption that core.getInput is always called in the same order. This was the case in the original version but it is not anymore.

After exploring the inner workings of Jest, I discovered that we are providing getInput as an argument in our function call and anticipating the correct sequence, which can be confusing and difficult to interpret.
However, I learned that Jest offers a helpful solution through its spyOn function. This approach can help us write more comprehensible tests in the future.
You can find more information on this here
If the tests are unreliable, it's important to question their value. We should consider removing them if they aren't providing the accuracy and consistency that we need.

Please merge.

👋 hi team, any updates on if this will be merged? i think this will be useful for my team.
see: https://zendesk.slack.com/archives/C0206JAJFPU/p1684414448842399

I guess this will not happen. I close this now

I guess this will not happen. I close this now

I hope you reconsider, since this is an absolutely essential fix.
I too do see that this action seems to be largely abandoned, but it still works perfectly fine with your changes. I've forked this change https://github.com/Jimdo/action-create-release and have personally tested it by using it for months now over various repos and hundreds of deployments, and it has worked flawlessly 100% of the time[*].
It's a small change after all and doesn't break any existing functionality. It's currently impossible to use multiple branches, create mixed releases/prereleases, or create releases from earlier commits than the latest master without this. Nothing will change for existing users who so far could only use a single master branch and create releases from the latest commit, as that will keep working just as it did. This is not a breaking change, and there is absolutely no reason to not merge this. And the version tag would be bumped from v2 to v3 anyway after the merge.
Using the fork obviously works fine too, but ultimately it'd be better to get it merged to this main project as this action is widely used and referenced to. It'd save the headache of troubleshooting and having to dig for this working fork. Also by closing the PR, it gets buried to the closed PR's and makes it harder for other people find the fix, and also if the maintainer ever comes back to check on this project, they'll probably miss the problem altogether.
It doesn't hurt to have this issue open till the end of time if necessary, right?
[*]: With the exception of GitHub outages, but obviously nothing works during outages due to no fault of the script itself.

I guess this will not happen. I close this now

I hope you reconsider, since this is an absolutely essential fix.
I too do see that this action seems to be largely abandoned, but it still works perfectly fine with your changes. I've forked this change https://github.com/Jimdo/action-create-release and have personally tested it by using it for months now over various repos and hundreds of deployments, and it has worked flawlessly 100% of the time[*].
It's a small change after all and doesn't break any existing functionality. It's currently impossible to use multiple branches, create mixed releases/prereleases, or create releases from earlier commits than the latest master without this. Nothing will change for existing users who so far could only use a single master branch and create releases from the latest commit, as that will keep working just as it did. This is not a breaking change, and there is absolutely no reason to not merge this. And the version tag would be bumped from v2 to v3 anyway after the merge.
Using the fork obviously works fine too, but ultimately it'd be better to get it merged to this main project as this action is widely used and referenced to. It'd save the headache of troubleshooting and having to dig for this working fork. Also by closing the PR, it gets buried to the closed PR's and makes it harder for other people find the fix, and also if the maintainer ever comes back to check on this project, they'll probably miss the problem altogether.
It doesn't hurt to have this issue open till the end of time if necessary, right?
[*]: With the exception of GitHub outages, but obviously nothing works during outages due to no fault of the script itself.

I really appreciate your commitment to this. Also a huge thanks to your comment about the commitish. The PR was open now for almost half a year and so far there is not a single reaction at all from the maintainers. This is why I don't expect that anything will happen on that matter.

I really appreciate your commitment to this. Also a huge thanks to your comment about the commitish. The PR was open now for almost half a year and so far there is not a single reaction at all from the maintainers. This is why I don't expect that anything will happen on that matter.

I do appreciate when stuff works properly, so thank you. @zendesk is not personal account but a company one, and it's quite possible this PR has just slipped under the radar. I'd say give it a bit more time, but ultimately it's up to you.


Add new Spotify OAuth 2.0 Provider to the 3rd party providers list

This new provider is fully compliant with League's OAuth 2.0 Client v2

Thanks for the PR.
Before removing a link to someone else's project, I'd prefer to give them the opportunity to comment and approve. IMO, it's okay to have multiple libraries listed for the same provider, since each library might provide different functionality.
@jonjomckay, this concerns your spotify-web-api library. Is that project still active? Should we leave the link in place here?
Thanks!

I wouldn't call my library active, but as far as I'm aware, it still works!
If doesn't meet your activity requirements, I'm totally OK for it to be removed from the list though.

We don’t have any activity requirements. I just wanted to make sure the library is still maintained. Since it is, and since some may still use older versions of oauth2-client, I’d like to keep it in the list.
@ker0x, would you mind updating your PR to keep the link to @jonnomckay’s Spotify library, while adding yours?
Thanks!

Hello @ramsey,
Thanks for your feedback, I just updated my PR !

Thanks!


Feature/specification improvements

This PR is a collection of smaller changes to the specification. Posting it as draft to make sure this doesn't get merged before getting the proper feedback in.

@LeeHoff @joecircello could you please check if those changes are ok?


Freezes in support list

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA, JP
FGA build number
1669
Describe the bug
In support screens, fga stops and didnt do anything. Aldo, the support image maker dont show up when I try to presa play on support list. My vídeo ia from the inside built screen recorrer.
Video

Device model
Poco F3
Android version
12
Screen size
2000x1080
RAM
6gb

That's a screenshot, not a video.
I need it for diagnosing your bug.

Video: https://youtu.be/_UAXCP4t2f4
My Android is not rooted

That's a screenshot, not a video.
I need it for diagnosing your bug.

Sorry, the video was too big

I also need debug rectangles.

I also need debug rectangles.

Ok, i'm uploading the New one

I also need debug rectangles.

https://youtu.be/_RS_Qtv9zlU

Something is very wrong on your device. Did you change any fine tune settings?

No, I didnt. I installed like the video shows me how to do.

I use betterfgo, not the original app. My game plays in 60 dps. Maybe is that?

The battle has no bugs, the only problem is on select support.

Could be, the fast flashing rectangles are not normal.

I am also having this issue and I do not run BetterFGO

It's not because of BetterFGO, I think the original issue is because of battery optimization.
@Crescent07891 Check the troubleshooting guide. If that doesn't help, open a new issue. I need a lot more information.

I don't want to open another thread so while not the exact problem faced by OP, I have faced this problem of being stuck in the support selection screen several times in the past (Samsung Note 9), usually only reinstalling it works. I have tried the following which did not work:

Restarting and force closing the app
Restarting the phone
Turning off servant card recognition
Turn on debugging.

When I encountered the problem again, I found that selecting the support manually once would continue the loop as normal. It has been fine until now but if the bug persists will try this solution again to see if it will fix it.
Video link: https://youtu.be/BtX57lLAyCU
To clarify, the scrolling down around 2:20 was done manually by me. At 4:40 the bug was not longer present and the scrolling by FGA works as intended.
Hopefully, this can help.

@darwinlinardi Your play button was in the way at 2:20 but you moved it before 4:40.
Never place the play button inside of red rectangles.
That's why we tell people to put it into the bottom left.

Thanks @reconman

I'm closing this because the original author doesn't respond anymore.


power output from code not Equal to power from formula

thanks for you create this library.  but i have some problem with power value that i get from example code
here my output:

i Calculated power  by using P = U * I.  so i test with my current and voltage data that i get but Calculated  value from formula not Equal or adjacent  power from example code output.
power output Equal to power from formula?.
i'm use nodemcu broad.

This formula is true only for active load.
See https://en.wikipedia.org/wiki/AC_power#Active.2C_reactive.2C_and_apparent_power

@xang555 many "whole house" energy meters are not particularly accurate at very low power usage so that might be some of your problem. The other issue is that real power is not simply U * I.
If the load has a power factor of 1 (or 100%) then it would be U * I but some loads have a pF of 0.7 etc.

thanks for your fast reply. i'm understand and close this issue AC not DC.  i'm stupid hahahah


In-line HELM monomers are not connected

I can add the following HELM to the webeditor and the monomers are displayed as connected.
PEPTIDE1{[C[C@@H](N*)C(*)=O |$;;;_R1;;_R2;;$|].[O=C(*)CN* |$;;_R2;;;_R1;$|]}$$$$V2.0

However, the properties

and structure view

show that they are not connected.,

The problem is the web service drops R# information when converting SMILES into Molfile:
"http://<IP_ADDRESS>/WebService/service/Conversion/Molfile"
Input SMILES: CC@@HC()=O |$;;;_R1;;_R2;;$|
Output Molfile:
{"SMILES":"CC@@HC()=O |$;;;_R1;;_R2;;$|","Molfile":"\r\n  CDK<PHONE_NUMBER>\r\n\r\n  7  6  0  0  0  0  0  0  0  0999 V2000\r\n    0.0000    2.2500    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0\r\n    1.2990    1.5000    0.0000 C   0  0  1  0  0  0  0  0  0  0  0  0\r\n    2.5981    2.2500    0.0000 N   0  0  0  0  0  0  0  0  0  0  0  0\r\n    3.8971    1.5000    0.0000 *   0  0  0  0  0  0  0  0  0  0  0  0\r\n    1.2990   -0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0\r\n   -0.0000   -0.7500    0.0000 *   0  0  0  0  0  0  0  0  0  0  0  0\r\n    2.5981   -0.7500    0.0000 O   0  0  0  0  0  0  0  0  0  0  0  0\r\n  2  1  1  1  0  0  0 \r\n  2  3  1  0  0  0  0 \r\n  3  4  1  0  0  0  0 \r\n  2  5  1  0  0  0  0 \r\n  5  6  1  0  0  0  0 \r\n  5  7  2  0  0  0  0 \r\nM  END\r\n"}

Hi Markus,
Could someone have a look at this?

It looks like there are two things going on here.
The webservices can take in SMILES without square brackets and will generate an image which has the monomers connected (albeit the free connection points are capped with H rather than being left as stars).
However, the webeditor does not use the webservices to create the atom/bond structure. It relies on the webservices to convert the SMILES to the molfile and then connect the R groups on the molfile. The conversion of SMILES to molfile results in a molfile containing *s, but not numbers therefore is not suitable for connecting up the monomers. It is as if it strips off the ChemAxon section which numbers the connection points.
So are there two choices:

Either use the webservices to get the atom/bond structure.
Or fix the SMILES to molfile conversion.

Could someone comment?


chore: update 'check-wasm' command to check fedimint-client

Locally I get the following error, @douglaz said he gets the same on linux:
error[E0432]: unresolved import `super::sysrand_chunk`
   --> /Users/justin/.cargo/git/checkouts/ring-236810bb234b0c6b/52a1294/src/rand.rs:307:16
    |
307 |     use super::sysrand_chunk::chunk;
    |                ^^^^^^^^^^^^^ could not find `sysrand_chunk` in `super`

Pushed another commit that makes fedimint-client use a WASM-compatible ring (like fedimint-client-legacy does) and now just check-wasm works for me.


Provide DSSP and Stride binaries

          It has taken quite some time, but I think we now have a working build script for DSSP in BinaryBuilder (https://github.com/JuliaPackaging/Yggdrasil/pull/6998). I was forced to build DSSP without using the `libcifpp_jll` build, as it still has a bug on windows, so at the moment everything is built inside the DSSP `build_tarballs.jl`, linked statically, and only the `mkdssp` binary is installed. Maybe we can fix the dynamic linking and building a shared library `libdssp.so` later.

Originally posted by @marcom in https://github.com/m3g/ProteinSecondaryStructures.jl/issues/2#issuecomment-1621949867
Thanks @marcom. As I understand we need now to create a simple package DSSP_Jll.jl or something of the sort and register it, which will provide the interface for the binaries?
Same goes for the stride binary, correct?

Once the pull request gets merged in the Yggdrasil repo, everything should happen automatically and there should be a new package DSSP_jll in the general registry that we will be able to install like every other package or add to the Project.toml of this repo. In detail, the BinaryBuilder infrastructure runs the build_tarballs.jl for all platforms specified in the build script, and then automatically creates a new repo for the _jll package (example: https://github.com/JuliaBinaryWrappers/ViennaRNA_jll.jl) with the generated binary artifacts. This repo then gets automatically registered as a new package in the Julia registry.
Until the DSSP pull request gets merged, you can try it all out locally:
# In the following, I am assuming you are on linux.
# On another OS it should work in a similar way.

# Check out the pull request to the Yggdrasil repo
git clone https://github.com/marcom/Yggdrasil -b dssp pr-dssp
cd pr-dssp/D/DSSP

# Run the build_tarballs.jl script, see `build_tarballs.jl --help` for options.
# You can use `julia +1.9` or other versions, but `julia +1.7` is what BinaryBuilder repo runs at the moment AFAIK.
# Change the target platform `x86_64-linux-gnu-cxx11` to your target platform.
# If you don't specify a platform, all platforms will be built (takes some time).
# Info on the env vars is here: https://docs.binarybuilder.org/stable/environment_variables/
BINARYBUILDER_USE_CCACHE=false BINARYBUILDER_NPROC=1 \
    julia +1.7 ./build_tarballs.jl --verbose x86_64-linux-gnu-cxx11

# If you want to deploy to an installable julia package, use the --deploy argument.
# Use --deploy=local to install the package into ~/.julia/dev/
julia +1.7 ./build_tarballs.jl --verbose --deploy=local x86_64-linux-gnu-cxx11

# Now you can use this package locally from julia
using Pkg
Pkg.dev("~/.julia/dev/DSSP_jll.jl/")

Oh, nice. It's even better. Let's wait then.
Do you think we are all convinced by the state of the STRIDE build and it's license?

To me the license issues sound ok, but I don't know how Mosè sees it. He might also just be busy at the moment preparing for JuliaCon.
Maybe also put the email from Dmitrij in the m3g/stride repo where he states that he grants usage under the MIT Expat license in the repo (perhaps under the docs dir).
What we could do in the meantime if we want to try everything out is:

deploy the builds to github under our own usernames with build_tarballs.jl --deploy=<username>/STRIDE_jll.jl, and the same for DSSP. Best to build for all platforms, then it should work everywhere julia works.

create a branch in this repo and start making the changes necesary to work with the jll packages, the packages can be added with Pkg.add("https://github.com/username/STRIDE_jll.jl")

But if it's not urgent it's easiest to wait for the BinaryBuilder pull requests to get merged.


Rename 'hierarchies' to 'nodes'

There is no reason why the root nodes of a hierarchy should be in a list named differently to nodes of lower levels. So a list of 'node' is always 'nodes' at all levels.
Attention, there is a dependency with #28.

Implemented with schema 1.2


refactor: enhance hyperlink handling in markdown shortcuts

Recognize url in hyperlink shortcuts. This is similar to GitHub.

Thank you for your prompt response. Here is my intended outcome: when I select a text segment resembling a URL and press cmd+k, I want it to be the link section wrapped by the parenthesis.


TexlFunction clean-up - removing DisabledFor[Commanding|DataComponent] virtuals

Unused in Power Fx

✅ No public API change.

✅ No public API change.

✅ No public API change.


UI/UX of Event.html

Description
Colour combination ...
It's colour combination does not look like professional..
Expected Behavior
I will change the colour combo... which will looks more attractive.
would you please assign me to this task..
Enviroment:

OS: Mac Linux Windows
Browser: Chrome Safari Firefox
Version:
Device: Desktop Mobile

Please assign me this task under GSSOC 23

Yes sure, go ahead @BadshahYadav . Open a PR with required screenshots, we will review it soon!

I have raised a issue regarding this, further conversations can be continued there!


Support of CodeStep using Composer

Is your feature request related to a problem? Please describe.

Describe the solution you'd like
Currently I do not see any Code Step that can be added in the Composer Application in the Dialog files. We were using several custom Code Steps while using AdaptiveDialog. Can we have this feature in Composer?
Describe alternatives you've considered

Additional context

@cwhitten do you have any updates on this?


docs: Update testing with disabled retries

When testing my app with jest + enzyme I had a lot of problems trying to resolve the useQuery api call, then I found on this blog post explaining that disabling the default retries can make things easier, and that indeed worked for me.
So I just took a piece of the doc written on that blog post (because it was already well written and clear) and added it to the official docs, I really think that'll help out new react-query users test their apps if they come across that issue 🤘

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add role option when starting dkeyserver

Signed-off-by: wanghouqi<EMAIL_ADDRESS>

title: dokcer -> docker

title: dokcer -> docker

fix


Classes to define response structure from graylog

Graylog sends us data structures that follow patterns. Part of the power of TypeScript is being able to define classes that represent these structures, so that we can

Validate that we receive data in the shape we expect
Validate that we are using it correctly in our code
Have code completion in our IDEs when playing with this data.

For this issue, take the structures that we currently receive from graylog and define classes to represent it, then use them in place of objects.

https://github.com/DiamondLightSource/logpanel/pull/18#discussion_r1575092300

https://github.com/DiamondLightSource/logpanel/pull/18#discussion_r1575096336

https://github.com/DiamondLightSource/logpanel/pull/18#discussion_r1575096336

https://github.com/DiamondLightSource/logpanel/pull/20#pullrequestreview-2028528468

https://github.com/DiamondLightSource/logpanel/pull/20#discussion_r1583273434


Fix invalid cargo key for docs.rs

Part of gtk-rs/gir#845
cc @sdroege @EPashkin @sfanxiang

👍

Thanks @GuillaumeGomez!

Correct me if I'm wrong: should this be merged to gtk4, gsk4, graphene and maybe gtk as well?

I'm going through crates at my own pace. :)


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/opstest2/docs-archive-test-source.git

Docs Build status updates of commit 7a88f16:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: RepositoryUnauthorizedWithSourceCommit] Git data access to 'https://github.com/opstest2/docs-archive-test-target' (branch: Release_Archive_main_2022-03-08-05-27-07) is not authorized.. It looks like this might be the first time user: v-alji submitted a pull request to this repo. Before user can run builds in a pull request, he/she can enable 'v-alji' GitHub account in Docs by visiting Docs Portal (https://ops.microsoft.com). After enabling his/her account (v-alji), close and then reopen this pull request to start another build.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


CATS v0.12.2 Join Selected Meshes joins All

On separating meshes of a model I want to use, and specifically selecting some meshes on the model, pressing "Selected" on the Join Meshes options joins "All" instead.
Naming doesn't seem to be the issue, as even if I have the main body mesh named that, everything still gets rejoined. I'm also not seeing any errors pop-up what so ever.
Tested to see if it worked with CATS version 0.12.1, and it works as expected there, but not 0.12.2.
Also, small suggestion, can you add a function to the "Selected" option of Join Meshes to preserve naming? Maybe through selecting a "master" mesh from a drop-down after the button is pressed, just to use for the sake of a name? May be a little nitpicky, sorry.

That bug is fixed in the development version of cats.
And about the name preservation, that's a good idea. I will probably remove the renaming


Use tracemalloc for memory measurements.

Addresses https://github.com/SciTools/iris/issues/5947
Replaces the current process RSS ("resident set size") based mechanism.
See #5946 for info on how they compare.
N.B. this is hard to test, possibly only takes effect when merged ?
@trexfeathers can you advise? I'm a bit vague on this.

Thanks @stephenworsley !


Transparent cover - which filament?

Hello,
I am sorry if I'm abusing issues but are you able to recommend from your experience a filament which would make a proper transparent or semi-transparent cover to see the content of the enclosure?
Thanks!

Im afraid I do not have any experience with transparent filament, perhaps someone else will have some advice on this then I can add a note to the readme.

I found this great article which hopefully solves this question:
https://www.3dsourced.com/rigid-ink/clear-3d-printer-filament/

A really nice explanation!
"While it’s impossible to print 100% clear models, printing simple designs with thin walls will certainly help."
Are we able to select how thin is the cover in the app?

I have made some updates and it is now also possible to configure the thickness of the lid.


Added definitions for v1.3.5 of the socket.io lib

I've moved the old definitions to legacy/socket.io-1.2.0 etc. The tests are the same, as the actual implementation hasn't changed.
When running the tests for the server lib, I get the following errors:
../node/node.d.ts(260,26): error TS2304: Cannot find name 'DataView'.
../node/node.d.ts(274,21): error TS2304: Cannot find name 'Map'.
../node/node.d.ts(283,21): error TS2304: Cannot find name 'Set'.
../node/node.d.ts(293,25): error TS2304: Cannot find name 'WeakMap'.

Which I guess is linked to Issue #4249? In any case, the errors with the node definitions, not the socket.io ones.

Hm, the two errors in Travis are:
socket.io/socket.io.d.ts(762,51): error TS1005: ';' expected.
socket.io/socket.io.d.ts(762,70): error TS1005: ';' expected.

but the line in question is:
broadcast( packet: any, opts: { rooms?: string[], except?: string[], flags?: {[flag: string]: boolean} } ):void;

51 and 70 are just after the "t" in "string" - am I missing something?

I fixed the problem with the broadcast() method, though I guess someone edited the socket.io-client file in the meantime. There was a merge conflict with my changes, but my changes encompass the edit, so everything should be fine

To be more precise, there was a merge conflict when I updated my forked repo, but the edits I've made should be fine

socket.io-client/socket.io-client.d.ts
to author(@divillysausages). could you review this PR?
:+1: or :-1:?
check list

[ ] pass the Travic-CI test?

socket.io/socket.io.d.ts
to author(@divillysausages). could you review this PR?
:+1: or :-1:?
check list

[ ] pass the Travic-CI test?

please fix travis ci.

Finally :) Sorry about that; I'm a bit new to pull requests and travis.
On the contributions page it says: "If you need many attempts to fix errors then please flatten the history and clean the commit message." - need me to do this? Also, how do I do it?

@divillysausages np.
@progre could you review this PR?

@vvakame LGTM

@progre thanks!
@divillysausages thanks mate!


geeks for geeks of 100x devs introducing 100x blogs

PR Fixes:

every ed tech busiiness at some point will start their blogs i think this is the time for that.

lets introduce 100x blogs

get notion like editing experience

preview the blog

post it

Resolves #[Issue Number if there]
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

Hey!
While I love this, this is already happening on https://github.com/code100x/daily-code/pulls
Pretty much is very similar to what you've built here
It'll be very hard to keep both in sync so will have to close it unfortunately


Remove deprecated CiliumEndpoint fields

This change is

Coverage decreased (-0.01%) to 45.613% when pulling 9281012e96e154047a107f363ea81759a72d17f7 on pr/tgraf/remove-deprecated-endpoint-fields into 0d7d76c3f7e27f46a4978b6e571d0e93adcb6ae3 on master.

test-me-please

test-me-please

Also, by bumping that version, we will brake downgrade path as that structure will no longer exist if the user wants to downgrade from 1.8 to 1.7.

Why does it need to be bumped? None of the fields are changing. The CRV remains identical. Why would downgrade break? If an upgrade occurred then the old CEP CRD is already registered so it will be unchanged and rollback is possible. The removed fields have been marked as deprecated for a long time and no code should depend on it. If it depends on them, it should break.

Also, by bumping that version, we will brake downgrade path as that structure will no longer exist if the user wants to downgrade from 1.8 to 1.7.

Why does it need to be bumped? None of the fields are changing. The CRV remains identical. Why would downgrade break? If an upgrade occurred then the old CEP CRD is already registered so it will be unchanged and rollback is possible. The removed fields have been marked as deprecated for a long time and no code should depend on it. If it depends on them, it should break.

I had the impression that we had a CRV for CEP.

I had the impression that we had a CRV for CEP.

Thanks for double checking


Add St. Cloud Technical Community College scraper

https://webproc.mnscu.edu/registration/viewCourseOutlines.do?campusid=208
Two option form.  Pretty straightforward.

@HarrisonGregg I changed the style around a lot.
One of the things I realized while testing is that a lot of the semester/subject searches give empty results with no links to any syllabi.  However, because I make a call directly to self.parse_for_files, I still download those empty search result pages.  Is that problematic?

I haven't been worrying about yielding unnecessary PageItems given that the general scraper produces a ton of extraneous WARC files.  But, if we wanted to prevent it, we could distinguish somehow between whether or not parse_for_files should save a PageItem if no links are extracted.  We could do this with a separate function or a flag or something.

@HarrisonGregg Looks like the require_files flag from #48 helps a lot.


Step 2 of Creating a distribution ticket appears wrong for VS

I'm using VS 2022 17.4.4 and 17.6.0 Preview 2.0 and in neither version is there a 'View Details' option.
There is an Add and Remove button to add or remove an account, but once the account is added, selecting it shows the Apple Id, Issuer, and Key.  There is no option to view details.
I'm referring to the Visual Studio under 'To create a distribution certificate'
2: In the Apple Developer Accounts dialog, select a team and click the View Details... button.
I see the same issue with both versions of Visual Studio, 17.4.4 and 17.6.0 Preview 2.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: d7ee5865-403a-3d47-ce50-69f42c5d012b
Version Independent ID: d7ee5865-403a-3d47-ce50-69f42c5d012b
Content: Publish a .NET MAUI iOS app for App Store distribution - .NET MAUI
Content Source: docs/ios/deployment/publish-app-store.md
Product: dotnet-mobile
Technology: dotnet-maui
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @DanTravison
I guess you'll be using an individual account, due to the presence of issuer and key data.
What you should see is a Team box below the issuer/key data that lists your Team and role. When you select the Team the View Details button enables.

You may need to resize your dialog to see all this.

I do not have a 'View Details' button when selecting the team.
I've see the same problem with the following Visual Studio versions:

Preview 2, Preview 3
17.5.4 (Community) and the previous version.
17.5.4 (Enterprise) and the previous version.

Yes, I am using an individual account.

Hi @DanTravison
It'll either be an account setup problem with your Apple Developer Account, or a product bug. If it's a product bug, it needs logging in Developer Communityhttps://developercommunity.visualstudio.com/home.


Upping grpc message size

From 4MB to 256MB to allow reconstruction metadata for really large files

https://cprimozic.net/notes/posts/rust-tonic-request-response-size-limits/
https://linear.app/xethub/issue/CLI-191/unable-to-download-large-file-with-s3-or-xet-cp


[beta] possible mistake, FCC: Test Suite

I decided to work the projects on beta just to test everything out, it seems that the projects test suite, checks for almost every html element to have an id....
I think that is a mistake for class instead...

Also I am having a hard time getting this test to pass...
Layout #2
The  element should be centered within its parent element.
For the project: Tribute page

@tommygebru please follow the "Report Bug" link within the test suite and report this issue there if you don't mind. That is the correct repo for opening test suite related issues. Also, it is not a mistake that the test suite checks for IDs. This is an essential part of how the test suite works - we are singling out specific elements using IDs in some cases, where appropriate.
When you open the issue on that repo - please also include a link to your project (if it's in CodePen) or additional code, so that we are able to diagnose the problem.
Also, please be sure to share your browser info - if you saw the alert when you first opened the suite - the app is currently optimized for chrome, and their may be issues in other browsers.
Thanks. Please close this issue once you open it in the correct place.

@tommygebru Also, not sure where the actual issue is here - sounds like you were able to follow the directions and got the test to pass


Notifications are not working through ruby_gntp

I see that the recommended gem to enable Growl notifications is ruby_gntp.
I'm just defining these gems in my Gemfile:
group :development do
  gem 'guard'
  gem 'guard-rspec'
  gem 'guard-spork'
end

group :test, :development do
  gem 'rspec-rails'
  gem 'spork'
  gem 'growl'
  gem 'ruby_gntp'
end

group :test do
  gem 'rb-fsevent'
  gem 'webrat'
end

I run guard and it gives me the ERROR: Error sending notification with gntp: Connection refused - connect(2):
Guard uses GNTP to send notifications.
Guard is now watching at '/Users/david/Sites/rails_tutorials/rails_tutorial'
Starting Spork for RSpec
NOTE: Gem.latest_load_paths is deprecated with no replacement. It will be removed on or after 2011-10-01.
Gem.latest_load_paths called from /Users/david/.rvm/gems/ruby-1.9.3-p0/gems/spork-0.8.5/lib/spork.rb:112.
NOTE: Gem.all_partials is deprecated with no replacement. It will be removed on or after 2011-10-01.
Gem.all_partials called from /Users/david/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems.rb:603.
NOTE: Gem.all_partials is deprecated with no replacement. It will be removed on or after 2011-10-01.
Gem.all_partials called from /Users/david/.rvm/rubies/ruby-1.9.3-p0/lib/ruby/site_ruby/1.9.1/rubygems.rb:603.
Using RSpec
Loading Spork.prefork block...
Spork is ready and listening on 8989!
Spork server for RSpec successfully started
ERROR: Error sending notification with gntp: Connection refused - connect(2)
Guard::RSpec is running, with RSpec 2!
Running all specs
ERROR: Error sending notification with gntp: Connection refused - connect(2)

I have enabled the "Listen for incoming notifications" option in my Growl settings.
By the way, iTunes notifications work fine through Growl, as well as Adium and other apps. So I think my Growl installation is ok.
My system is OS X Lion 10.7.2, and my Growl version is 1.2
Is this issue related to the ruby_gntp gem?

Also it seems that the option :notification => false in the guard 'rspec' block in the Guardfile is ignored.

ruby_gntp needs at least Growl 1.3 as described in the Guard README.

Oh, you're right. Sorry, I didn't read it carefuly, my bad!

Just for anyone that also has the problem of being on OS X Lion and Growl 1.2, just download the latest 1.2 version from the growl website, and install growlnotify from the extras folder. Then just install the growl gem, and notifications will work out of the box.
This was (very well) explained in the Guard README, but just for the record :)

What about people on Snow Leopard with 1.2?

Just use the growl notifier.

Oh okay never mind sorry, I had some crossed wires (still had to gem uninstall ruby_gntp)

I am having the same issue on OS X Lion and Growl 1.2.2. I'ved tried to install the growlnotify and growl gem. But still has that error message. And it's ignoring the :notification => false flag. What I want is just to remove this annoying message.....


Feature Add: Sync Obsidian Notes DB with RAG notes DB

As a user, I would like to be able to 'sync' my obsidian notes for immediate usage/export from tldw.
I would like to be able to select the path to my obsidian installation, and have the notes imported. I would also like the ability to export all notes in the same manner.

Combining this and the other one, adding LogSeq might not be a bad idea as well, since both are very MarkDown-centric, only difference is that LogSeq is very outline-centric compared to Obsidian being paragraph-centric. Other PKM options are also popping up, so it would be nice to keep an eye out. https://github.com/logseq/logseq
https://github.com/rmusser01/tldw/issues/314


[StreamExecutor C API] Lazy getting device count to provide more feasibility

This PR allows plugins provide the device count at runtime instead of loading stage, which provides more feasibility, for example, plugin can register a virtual device during the loading time(import tensorflow), and can select another backend through some plugin specific API, so the device count needs to be changed.

@penpornk can you help to have a review or suggest other reviewers? Thanks.

Removing the API review tag. Will do this internally instead.


Add model_runs directory

This makes it easier to iterate over all the runs by calling dir_ls on model_runs and also makes it easier to locate collated  plots and other files that apply to all the model runs.

Seems like the baseline forecasts are not being fit.

Seems like the baseline forecasts are not being fit.

Are are we making updates to the structure without having a test run facility to check which parts of the code base are affected by any change?

@SamuelBrand1 #135 was supposed to help with that. It's not written as a formal test, but that is the plan in #126. Surprisingly, for this PR, it runs without throwing an error, even though the baseline forecasts aren't being fit.

That suggests that we want something to return this failure in part of the run?

@SamuelBrand1 #135 was supposed to help with that. It's not written as a formal test, but that is the plan in #126. Surprisingly, for this PR, it runs without throwing an error, even though the baseline forecasts aren't being fit.

This will be addressed in https://github.com/CDCgov/pyrenew-hew/pull/143

The default "Files Changed" view is borked, but you can see the actual changes here.

@dylanhmorris Ready for your review. Would appreciate some guidance on modification to the collation scripts. You're welcome to adjust them directly on the branch.


Wanb logger

Hi @magehrig  is there any way we can set the logger to offline mode and save the checkpoint could you please tell how do we do it
1.Even after i set my wandb logger to offline mode using API key its trying to connect to the internet and throwing an SSL error can i avoid this or is this a part of wandb we cannot skip
2.if we can skip can you please tell how or if we cannot how can we go on with SSL error
3.How can we start training without the visualization part so that it does not use wandb every time i run its going into wandb site
I tried training it setting wandb to offline mode i get a SSL error and it does not log the checkpoint

Please check out this related issue: https://github.com/uzh-rpg/RVT/issues/19
atm I don't have the time to adapt and test the code for offline logging but the above issue should be useful to implement this yourself.


Fix unsoundnes in insert remove and despawn

EntityMut::move_entity_from_remove had two soundness bugs:

When removing the entity from the archetype, the swapped entity had its table row updated to the same as the removed entity's
When removing the entity from the table, the swapped entity did not have its table row updated

BundleInsert::insert had two/three soundness bugs

When moving an entity to a new archetype from an insert, the swapped entity had its table row set to a different entities
When moving an entity to a new table from an insert, the swapped entity did not have its table row updated
See added tests for examples that trigger those bugs

EntityMut::despawn had two soundness bugs

When despawning an entity, the swapped entity had its table row set to a different entities even if the table didnt change
When despawning an entity, the swapped entity did not have its table row updated

bors r+


Windows: Add unix fifo-pipe equivalent so vmaf distorted can be converted to the same pixel format

On Linux a fifo file pipe is used during VMAF so both reference and distorted files can be converted into a yuv stream in the same way before passing to VMAF.
Windows does not support fifo, so currently not conversion is being done on the distorted. This means Windows vmaf scores suffer. Ideally windows would do the same thing.
Linux impl: https://github.com/alexheretic/ab-av1/blob/37272016bf0d471fea67c90b24a0545a95aebe62/src/yuv.rs#L45..L70

https://github.com/alexheretic/ab-av1/issues/63#issuecomment-1314953259
Perhaps interprocess unnamed pipes could also work?

I've had a look but I can't get a fifo-like to work on Windows. I just don't really understand how to use the named-pipe/sockets available there.

I'm not knowledgeable enough for trying this out, but here's another
possible solution, as it seems to be cross platform.
https://crates.io/crates/ipipe
On Tue, 15 Nov 2022, 14:00 Alex Butler, @.***> wrote:

I've had a look but I can't get a fifo-like to work on Windows. I just
don't really understand how to use the named-pipe/sockets available there.
—
Reply to this email directly, view it on GitHub
https://github.com/alexheretic/ab-av1/issues/65#issuecomment-1315276477,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARDH3722JVDN2FLUEYYIE3WIOCNBANCNFSM6AAAAAASANLQRM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sorry, I'm not a programmer, I have no idea about rust and I'm not familiar with those concepts. I had a look at that part of the code and I didn't understand much.
But if there is a possible solution I could test it out and report the results.
I wish I could be of more help.

Turns out tokio has built-in support for windows named pipes. I got it to work by creating 2 pipes and an async task to copy between them. It's much simpler using fifo on Linux!


chore(deps): update common-dev-assets digest to 5d664dd

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
f02a1bb -> 5d664dd

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.2.14 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: