Update promote for modified repo structure

odo pipeline init creates GitOps repos that use a modified version of the gitops repository spec, as per https://github.com/rhd-gitops-example/manifest-documentation. See for example https://github.com/bigkevmcd/gitops/.
In order to support multiple environments, a path /environments/environment-name/ is added to the top of the directory structure.
Currently we use
services promote --from [path] --to [git url] --service [name]

This means, copy [name]/config/* to /services/[name]/base/config/* in the [git url] repo via a PR. In the new case, the target path is /environment/[environment-name]/services/[service-name]/base/config/* and the question is, How do we determine [environment-name] when preparing the pull request, if the [service-name] subdirectory does not exist?

We could add another command line arg, --env env-name
We could say, ‘if /environment contains only one subdirectory, use it’
We could say, ‘if /environment is empty, create a subdirectory whose name is the same as the target repo’

Under this issue implement option 2 and either implement option 1 or raise a follow-on issue to do so.
Also update our example projects (gitops-exampl-dev and -staging) to conform to the new format.

I'll take a look at this one

Added the flag (in the most basic sense, not doing anything but printing its value!) and the next piece of work is to get the directory structures matching up and making the necessary adjustments to the promote commands (for both local to remote and remote to remote repositories), will work with @mnuttall on getting this part right
I'll work on the updated structure over at https://github.com/a-roberts/gitops-example-dev and https://github.com/a-roberts/gitops-example-staging as well.

I have
We could add another command line arg, --env env-name
We could say, ‘if /environment contains only one subdirectory, use it’

implemented now, working on tests and idyllic repository structure next.


GDExtension Editor Shortcuts Not Working

I'm using Godot 4.2.1 with the LimboAI latest master branch commit (0ff93fa) GDExtension, and the editor shortcuts don't work. For example I can't use delete to delete a task, and I can't use Ctrl + D to duplicate a task.

Strangely, it works as expected on my system with the latest build and GDExtension 4.2 branch. Which platform?
Anyone else experiencing this issue?

I'm on Windows 11. Maybe the shortcuts are getting eaten by the scene hierarchy?

In my setup shortcuts stop working only when this area is not focused:

Using input fields in the inspector(like custom_name) and using search bar in task list and clicking anything outside of LimboAI tab  removes focus from that area

Still not sure how I can reproduce this. As masterthdev noted, the LimboAI editor accepts shortcuts only when it is focused. Which is reasonable, since you don't want LimboAI eat those shortcuts from the scene editor.

This issue might be fixed in #122

Closing this one, because issues that I found in shortcut processing I already fixed. Reopen if you still have this issue.


[release-1.20] make the auto scale behave in gateway configurable

This is an automated cherry-pick of #47318

this seems more like a new feature, rather than a bugfix.

I think it's fine to add this since it's not risky, IIRC we did this kind of thing before.


Add support for sequential handling on Patch jobs and objects

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[ ] Documentation Update

Description

Sequential execution runs all objects in a job iteration before reiterating
It allows delaying between objects and/or job iterations
Add PatchExecutionType for backward compatibility
Related Tickets & Documents

Related Issue #
Closes #713

@rsevilla87 I've made the change we discussed regarding running list on every run and added a test that verifies that it in fact works.
As for documentation, I already had a section on the different execution mode. I guess that because I wrote the code, I don't see what's missing. But, please LMK what information you think is missing


[SP-5267] Backport of PDI-15704 - Mail Send (transformation) step fai…

…ls when receive the parameter that contains an encrypted password. (8.3 Suite)
Cherry-pick of #6870 into 8.3 branch.
@ssamora @ppatricio

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'engine' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  engine/src/main/java/org/pentaho/di/trans/steps/mail/Mail.java
  engine/src/test/java/org/pentaho/di/trans/steps/mail/MailTest.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes: +0.1% (click to expand)
org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.4% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Branch Change: -2.6% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.singlethreader.SingleThreaderMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.ui.repository.pur.repositoryexplorer.model.UISecurityRole

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

PR consistent with base bug


Add crucial integration tests

Add integration tests to ensure the code dependencies work.

[x] Ensure the etcd client works with a locally spun up etcd instance (docker)
[ ] kubeadm tests This will become a whole lot simpler after #31. For now:

[ ] kubeadm phase cert
[ ] kubeadm phase kubecfg

[ ] kmm/kubelet - requires systemd service (may use for e2e test also)

Out of scope (for this ticket):

kube api dependant tests - see e2e https://github.com/UKHomeOffice/keto-k8/issues/35
etcd certs generate - this will probably be broken out into separate tool as this feature has a different release cadence and dependency list to the rest of the tool.

Fixes https://github.com/UKHomeOffice/application-container-platform-board/issues/373


feat: implement get space buyers endpoint

See : https://developer.twitter.com/en/docs/twitter-api/spaces/lookup/api-reference/get-spaces-id-buyers

Blocked until https://github.com/redouane59/twittered/issues/326 is solved


Cherry-pick commits from master to r0.5 branch

Problem description
Cherry-Pick following commits from master to r0.5 branch
c41a99ea257108da4442f65531dfcaaf8d7da7d7 [issue-224] Fix unwanted logging in system test
0c6fd355fb3ea77e7ec678183d4cd429dc82915c [issue-89] FlinkPravegaReader fails to achieve exactly-once semantics
3a756d37badc0fbde68a14c739e7d4f8ae8c8751 [Issue 222:] Version changed from v0.4.2 to v0.5.0 in documents
cb1982f9e658feba2cd0c94559ba9090e1eed88d [issue-228] Allow configuring maximum outstanding checkpoint request
bccc44f73953f19a5890adab791d25758f19bbee [issue-134] FlinkPravegWriterITCase testExactlyOnceWriter fails random
043274b21ea167d4b1229cf39d28816b9eaa73e8 [issue-234] Fix TLS security configurations

Problem location
r0.5 branch
Suggestions for an improvement

closed https://github.com/pravega/flink-connectors/pull/246


Postgres PREPARED STATEMENT example

The documentation doesn't appear to provide any examples of how to execute a prepared statement.  The only reference I was able to find was a reference to use a struct but this seems at odds with creating prepared statements on the server and then executing them.
Is there any documentation or examples of executing a prepared statement from the client.  The normal await client.query() doesn't appear to work.

@duncangroenewald You don't need to create the statements manually on the server. PostgresNIO handles that over the wire protocol.
See these links to the implementation and a test, as an example of how to make a prepared-statement query:
I haven't taken a proper look at the docs, so can't comment on that. We should add an example if there is no such example in the docs currently.

Thanks, I figured it out.   Conceptually it is a little confusing at first so an explanation or at least a link to the test examples in the documentation would be a help.

@duncangroenewald we agree that this issue is still valid then 🙂.


Configuration for non-default formatter?

Hi @rohit-gohri 👋
I would like to run a non-default formatter on a specific file (namely the TypeScript and JavaScript Language Features, in order to format SQL in tagged template literals), and I was wondering whether you would be open to adding support for other, non-default formatters (eg. "Format Document With...")?
Not sure how the configuration would look, maybe something like:
{
  "editor.codeActionsOnSave": [
    "source.fixAll.format['vscode.typescript-language-features']"
  ]
}

Or, as an example, to format using Prettier if it's not the default:
{
  "editor.codeActionsOnSave": [
    "source.fixAll.format['esbenp.prettier-vscode']"
  ]
}

Not sure if that kind of configuration is supported though. I guess the minimal version of this feature would be to provide a single key like:
{
  "editor.codeActionsOnSave": [
    "source.fixAll.formatWithVscodeFormatter"
  ]
}

But then again, that would mean a key for any supported formatter. However, maybe it's an ok tradeoff... 🤔

I don't think this would be possible. In the current implementation I'm calling VSCode's Format Document action that in turn calls the default formatter (in this case prettier). I can't directly call a specific extension AFAIK. This is my first VS Code extension, so my knowledge is very limited.
You may try changing your default formatter for typescript files or in that particular workspace:
  "[typescript]": {
    "editor.defaultFormatter": "vscode.typescript-language-features",
    "editor.formatOnSave": false,
    "editor.codeActionsOnSave": ["source.fixAll.format", "source.fixAll.eslint"]
  },

Hm, yeah.. wonder if there's another API to call Format Document With... . Maybe that's something to look into...

You may try changing your default formatter for typescript files or in that particular workspace

The use case is to actually use multiple formatters in a row 😓

Oh.. Will try to look into if that's possible and expose multiple actions.
You might be interested in https://github.com/prettier/prettier-vscode/issues/1555
If prettier adds their own action, then you can use this with TS/JS Lang Features.

You might be interested in prettier/prettier-vscode#1555

Oh, nice - thanks for the heads up! I've subscribed over there too.


Methods for toString() toFormat() toRepr() that uses stringRepersentation() sholult be defined in separate utils class

No we won't do this so classes could be self-contained


Per-field spec validation hooks

Allow me to move more post-load validation to the c42 spec file, by setting an arbitrary con4m hook on any field (really, would be okay to run one for the whole file, but I think avoiding one big mondo function is a good idea).

Wow this was a lot more work than expected, as I had to do things like allow type declarations to make this usable enough.


ST_WeaponRaiseLower may have a bug with ISM soldiers

Soldiers seem to snap to lowered position. Didn't seem to happen with ST_Soldier. Should get fixed with https://github.com/HaywireInteractive/OnAllFronts/pull/247.

Duplicate of https://github.com/HaywireInteractive/OnAllFronts/issues/242


ARROW-13674: [CI] PR checks should check for JIRA components

@pitrou I think this does what you were describing in the Jira, what do you think?

@amol- I think it does... but can you try to consolidate the Javascript helpers as suggested in the JIRA description?
(also, add comments/docstrings to those helpers so that they are easier to reuse)

@amol- I think it does... but can you try to consolidate the Javascript helpers as suggested in the JIRA description?
(also, add comments/docstrings to those helpers so that they are easier to reuse)

Refactored utility functions into their own module and document them 👍

This looks good to me, I hope it will give satisfaction.


[0.43, 0.44] Source maps trigger error in Firefox & Chrome: path issue

Originally reported here:

How to use source maps with Hugo 0.43?

Test reproduction Hugo project here:

Hugo source maps error repository

Setup
hugo env
Hugo Static Site Generator v0.44/extended windows/amd64 BuildDate: unknown
GOOS="windows"
GOARCH="amd64"
GOVERSION="go1.10.3"

The problem

Source maps do not work. Firefox and Chrome developer tools only show the rendered .css file, not which .scss actually hold the files.

Error messages
In Firefox, in the Console tab of the Developer tools, the following appears:
Source map error: SyntaxError: JSON.parse: bad escaped character at line 6 column 16 of the JSON data
Resource URL: http://localhost:1313/assets/css/style.css
Source Map URL: style.css.map[Learn More]

Note: To see the error message you'll first need to inspect an element.
In Chrome, in the Console tab of the Developer tools, the following shows:
DevTools failed to parse SourceMap: http://localhost:1313/assets/css/style.css.map

Problem in the source map
The generated source map looks like:
{
	"version": 3,
	"file": "style.css",
	"sourceRoot": "C:/Temp/hugo-source-maps",
	"sources": [
		"themes\test\assets\assets\css\style.scss",
		"themes/test/assets/scss/_content.scss",
		"themes/test/assets/scss/_footer.scss",
		"themes/test/assets/scss/_header.scss"
	],
	"sourcesContent": [
		"\r\n@import \"themes/test/assets/scss/_content.scss\";\r\n@import \"themes/test/assets/scss/_footer.scss\";\r\n@import \"themes/test/assets/scss/_header.scss\";",
		"main, p {\r\n    font-size: 15px;\r\n}\r\n",
		"footer {\r\n    font-size: 20px;\r\n}",
		"h1 {\r\n    font-family: Cambria, Cochin, Georgia, Times, Times New Roman, serif;\r\n    color: orange;\r\n}\r\nheader {\r\n    font-size: 20px;\r\n}"
	],
	"names": [],
	"mappings": "ACAA,AAAA,IAAI,EAAE,CAAC,CAAC;EACJ,SAAS,EAAE,IAAI,GAClB;;ACFD,AAAA,MAAM,CAAC;EACH,SAAS,EAAE,IAAI,GAClB;;ACFD,AAAA,EAAE,CAAC;EACC,WAAW,EAAE,uDAAuD;EACpE,KAAK,EAAE,MAAM,GAChB;;AACD,AAAA,MAAM,CAAC;EACH,SAAS,EAAE,IAAI,GAClB"
}

The line number that Firefox complains about is:
"themes\test\assets\assets\css\style.scss",

The problem seems to be that the \ should be /, since the other paths in the source map use this format:
"themes/test/assets/scss/_content.scss",
"themes/test/assets/scss/_footer.scss",
"themes/test/assets/scss/_header.scss"

I'm seeing the same problem on Windows. \ is actually a JSON escape character, so it isn't valid to be used there. I'm assuming this is a problem upstream in LibSASS, but I'll have to check to be sure.

I suspect it's an issue with the paths Hugo sends LibSASS. We send windows paths on Windows, so "\" is the separator.

https://github.com/gohugoio/hugo/blob/d6fde8fa131f3852fa98a8ec5c360e736486cf54/resource/tocss/scss/tocss.go#L83-L90
I think on Windows sourcePath ends up with \s from WorkingDir and FilePathSeparator.  Then that gets inserted into the JSON without being escaped.  Probably could just escape it, but may work better to just replace \ with / in that string?

@machee I suspect the way to go is to use Unix-style slashes on all paths sent to LibSass, but someone has to test it ... I have a Windows VM floating around somewhere... It sounds a little bit counter-intuitive, and is sounds like a LibSASS bug, because we send in absolute file paths here, so it is c:\ \myproject\\scss etc.

Seems like the bug comes after LibSass has run, when replacing "stdin" in the SourceMapContent.  At least with the current example LibSass is not returning invalid JSON and does not generate paths with \ even on Windows.  It's the Replace on line 90 that is making the JSON invalid by inserting unescaped \.
I may try a Windows build tomorrow but seems like 0236f74f2fd8e65c63ce0cfd383e8acc5819e752 would fix it.


Running into issues while installing Azimuth on Windows, Need more clear installation docs

Hey,
I've been trying to install Azimuth on Windows 10 and have been running into problems even after installing http://aka.ms/vcpython27
It'd be nice to have some clear documentation of the setup process and the list of required libraries needed to get this running. Here's the log
https://gist.github.com/sudheesh001/2b70e0ed4371032cab58d1efa367cee3

Have you tried using the Anaconda python distribution? https://www.continuum.io/downloads
You can then run "conda install biopython", which should solve your problem.
We are going to add a note in the readme page pointing users to Anaconda as the preferred python distribution. Thanks!

I've done conda install biopython and then re ran the python setup.py install to set up azimuth but it seems to fail again with the same result. FreeType and PNG look like required dependencies which are failing but that's in building matplotlib.
Any workarounds ?

Have you tried running conda install matplotlib before python setup.py install? Can you post the full error message?

Yup, I've done the following
conda install biopython
conda install matplotlib
python setup.py install
Here's the log: https://gist.github.com/sudheesh001/9cc04fbf7df9813d479221409a04f0fd
It ends with
OPTIONAL BACKEND EXTENSIONS
                macosx: no  [Mac OS-X only]
                qt5agg: no  [PyQt5 not found]
                qt4agg: no  [PySide not found; PyQt4 not found]
               gtk3agg: no  [Requires pygobject to be installed.]
             gtk3cairo: no  [Requires cairocffi or pycairo to be installed.]
                gtkagg: no  [Requires pygtk]
                 tkagg: yes [installing; run-time loading from Python Tcl /
                        Tk]
                 wxagg: no  [requires wxPython]
                   gtk: no  [Requires pygtk]
                   agg: yes [installing]
                 cairo: no  [cairocffi or pycairo not found]
             windowing: yes [installing]

OPTIONAL LATEX DEPENDENCIES
                dvipng: no
           ghostscript: no
                 latex: no
               pdftops: no

OPTIONAL PACKAGE DATA
                  dlls: no  [skipping due to configuration]

============================================================================
                        * The following required packages can not be built:
                        * freetype, png
error: Setup script exited with 1

C:\Users\susingan\Documents\Microsoft\Azimuth>

Installation instructions have been updated. If you still haven't resolved your issue, please try the following.
Run pip install ./ --no-cache --upgrade from the root directory of the Azimuth repository. Make sure the pip and python binaries are pointing to those in your the anaconda installation:
PS > where.exe pip
C:\Users\{username}\AppData\Local\Continuum\Anaconda2\Scripts\pip.exe


Parse require() and include() functions?

Now that would be interesting :grinning:

Done!
Only thing missing is that the system cannot resolve file inclusions through variables...


Destructuring props no longer works without experimental features

Vue version
3.3
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-hbtqav?file=src/App.vue
Steps to reproduce
Open the example in a new tab to see the console.log's.
You can see that the destructured variable in the Works component has been logged, but the one in the NotWorks component is undefined.
What is expected?
Both props are available. This worked below 3.3
What is actually happening?
Looking at https://github.com/nuxt/nuxt/issues/20789 and https://github.com/nuxt/nuxt/pull/20795 it seems like when we do not enable reactivity transform or the new props destructuring feature, then the destructured props are just lost after compilation.
Probably related to this code path: https://github.com/vuejs/core/blob/main/packages/compiler-sfc/src/script/definePropsDestructure.ts#L31
System Info
No response
Any additional comments?
No response

If this feature graduates from experimental to stable, snippets like Nuxt's would break, anyway, because error prop would suddenly become reactive, right? So, while destructuring props might be a valid pattern that should be considered by the compiler, just regressing to previous behavior may not be future-proof.


support light theme

Currently, the style of filename is bold white:
https://github.com/charliermarsh/ruff/blob/6733aad216295a9f7850d16291f7831cc31ec7fa/src/message.rs#LL59C71-L59C71
This means, if users are using a light theme, it's almost invisible.

I wonder if this can be another color.

Nice idea, for sure.


What does node2vec expect in .wv method?

Hello,
I;m working through chapter 4. In the prediction of the test set, you use train_mask_str in the book but in your  gh code you use train_mask. Depending on which one you use one gets very different results.
if you pass the integer mask you get something that won't go pass 60% accuracy.
y_pred = clf.predict(node2vec.wv[test_mask])
acc = accuracy_score(y_pred, labels[test_mask])
print(f'Node2Vec accuracy = {acc*100:.2f}%')
>>>Node2Vec accuracy = 59.09%

But if i pass the string mask i get what you report both in gh and the book . Which seems really high considering how many samples you pick out in the train and test.
y_pred = clf.predict(node2vec.wv[test_mask_str])
acc = accuracy_score(y_pred, labels[test_mask])
print(f'Node2Vec accuracy = {acc*100:.2f}%')
>>>Node2Vec accuracy = 95.45%

How can one explain this discrepancy?

Hi, sorry for the very late reply! Thank you for noticing this discrepancy between the book and the code. Unfortunately, I can't replicate your issue. The data type should not matter here because it's masking the same nodes.

No problem. thanks you for the reply (and amazing book). I think this is more of an issue with node2vec. I'll take what I learned conceptually and move on 😊 thanks!


rpi_gpio home assistant  not working 2024.3.1 on Raspberry pi 5

After switching to Home Assistant on Raspberry Pi 5, GPIO management is no longer available. does anyone have any ideas on how to resolve this? Thank you
This entity is no longer provided by the rpi_gpio integration. If the entity is no longer used, delete it in settings.
Registratore: homeassistant.components.switch
Fonte: helpers/entity_platform.py:350
integration: Interruttore (documentazione, problemi)
Prima occorrenza: 09:15:54 (2 occorrenze)
Ultima registrazione: 09:17:40
Error while setting up rpi_gpio platform for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 350, in _async_setup_platform
await asyncio.shield(awaitable)
File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/rpi_gpio/switch.py", line 69, in setup_platform
RPiGPIOSwitch(
File "/config/custom_components/rpi_gpio/switch.py", line 100, in init
setup_output(self._port)
File "/config/custom_components/rpi_gpio/init.py", line 39, in setup_output
GPIO.setup(port, GPIO.OUT)
RuntimeError: Cannot determine SOC peripheral base address

Duplicate of https://github.com/thecode/ha-rpi_gpio/issues/225


Change var names to standard camel casing

Work for this issue will begin begin on branch work-liquid-labs/regex-repo/80.


Options.java:71-75: Options ctor. According to new...

Puzzle 558-e98f4792 in src/main/java/org/takes/http/Options.java:71-75 has to be resolved: Options ctor. According to new qulice version, constructor must contain only variables initialization and other constructor calls. Refactor code according to that rule and remove ConstructorOnlyInitializesOrCallOtherConstructors warning suppression.... The puzzle was created by Maksimenko Vladimir on 7-Feb-2016.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code.

@essobedo the task is for you now, follow these guidelines. Don't hesitate to ask any technical questions right here
The cost of this task is 30 mins (this is exactly how much will be paid, not less not more), when the task is done

@davvd the PR is ready to be reviewed thx in advance

@yegor256 I added milestone 1.0 to this issue, let me know if there has to be something else

@davvd The PR has been merged, could you please close the ticket and proceed with the QA. Thank you in advance.

@davvd please close the ticket and proceed with the QA.

@davvd please close the ticket and proceed with the QA.

@davvd please close the ticket and proceed with the QA.

@davvd please close the ticket and proceed with the QA.

@yegor256 The issue is closed

@ypshenychka please, help us to evaluate quality here, as per par.24

@davvd Quality is good.

@davvd Quality is good.

@ypshenychka thanks a lot

@davvd everything is ok here could you please proceed?

@essobedo 10 mins was added to the account of @ypshenychka (for QA review), in transaction 78972384. Thanks so much! Your account was topped up for 30 mins (transaction ID is 78972560, the task took 399 hours and 41 mins). +30 added to your rating, at the moment it is: +225

@davvd thank you very much!

@davvd thank you very much!

@essobedo sure, you are welcome


Allow registering a service that relies on the Service Container

Implemented through the ServiceFactory delegate.
When a Registration with an ImplementationFactory is added to the Dependency Injection container, the ImplementationFactory can be passed a new ServiceFactory delegate, which will be the GetService method of the Dependency Injection container.


Release 0.4.0

The plan is to release LiberTEM 0.4.0 this week.
What issues still need to be resolved before we cut the first RC?

[x] Release LiberTEM-blobfinder and let LiberTEM depend on it, part of #261, see also https://github.com/LiberTEM/LiberTEM-blobfinder/issues/7
[x] Info on restructuring in changelog - #579
[x] Open a browser after starting the server - #580
[ ] I'd also like to work on a rewriting the cache stats stuff - depending on how far I get, it may still be part of this release

QA Using a release candidate

[x] Review open issues and pull requests
[ ] Full documentation review and update, including link check using sphinx-build -b linkcheck "docs/source" "docs/build/html" -- partly done in #590, continue later (@uellue)
[x] Update the expected version in notes on changes, i.e. from 0.4.0.dev0 to 0.4.0 when releasing version 0.4.0.
[x] Update and review change log in docs/source/changelog.rst, merging snippets in docs/source/changelog/*/ as appropriate.
[x] Update the JSON files in the packaging/ folder with author and project information
[x] Create a release candidate using scripts/release. See scripts/release --help for details.
[x] Confirm that wheel, tar.gz, and AppImage are built for the release candidate on GitHub
[x] Confirm that a new version with the most recent release candidate is created in the Zenodo.org sandbox that is ready for submission.
[x] Install release candidate packages in a clean environment (for example: pip install -i https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple 'libertem==0.4.0rc1')
[x] For the GUI-related items, open in an incognito window to start from a clean slate

[x] Correct version info displayed in info dialogue?
[x] Link check in version info dialogue
[x] Include floats, ints, big endian, little endian, complex raw data
[x] Open each test file

[x] Are parameters recognized correctly, as far as implemented?
[x] Any bad default values?
[x] Does the file open correctly?
[x] Have a look at the dataset info dialogue. Reasonable values?

[x] Perform all analyses on each test file

[x] Does the result change when the input parameters are changed?
[x] All display channels present and looking reasonable?
[x] Reasonable performance?
[x] Use pick mode.

[x] Re-open all the files

[x] Are the files listed in “recent files”?
[x] Are the parameters filled from the cache correctly? see #599 for one bug found

[x] Try opening all file types with wrong parameters: Proper understandable error messages?
[x] Pick one file and confirm keyboard and mouse interaction for all analyses: Correct bounds check for keyboard and mouse?
[x] Check what happens when trying to open non-existent files or directories in the GUI.

[x] Proper understandable error message?
[x] Possible to continue working?

[x] All workers reaped?

[x] Check what happens when trying to open non-existent files by scripting: Proper understandable error message?
[x] Check what happens when opening all file types with bad parameters by scripting: Proper understandable error message?
[ ] Run all examples

[x] center_of_mass
[ ] pcmclustering (don't have the data here...)
[x] peak_selector
[x] radialfourier
[x] simple libertem API
[x] basic.py
[ ] digital-micrograph-basic.py (@uellue postponed, first update GMS)

[x] Run libertem-server on Windows, connect to a remote dask cluster running on Linux, open all file types and perform an analysis for each file type.
[x] Use the GUI while a long-running analysis is running: Still usable, decent response times?
[x] Confirm that pull requests and issues are handled as intended, i.e. milestoned and merged in appropriate branch.

After releasing on GitHub

[x] Confirm that all release packages are built and release notes are up-to-date
[x] Install release package
[x] Confirm correct version info
[x] confirm package upload to PyPi
[x] Publish new version on zenodo.org
[ ] Update documentation with new links, if necessary
[x] Add zenodo badge for the new release to Changelog page
[x] Send announcement message on mailing list
[x] Bump version to 0.5.0.dev0

First changes unrelated to release

[ ] Bump optional dependency in libertem-blobfinder to libertem>=0.4.0,<1 - see https://github.com/LiberTEM/LiberTEM-blobfinder/pull/20

Btw: I think we can drop "Copy test files of all supported types to a fresh location or purge the parameter cache" from the checklist, if we are using an incognito window for testing.

As the release was done some time ago, I'm going to close this. The only major outstanding item is the documentation review, which is independent of any releases IMHO.


APEXCORE-413 - Collision between Sink.getCount() and SweepableReservoir.getCount()

@tweise Please review

A more general question: Is there any benefit of AbstractReservoir implementing BlockingQueue and hence carrying all the extra methods that we don't need but every concrete implementation must provide?

There is no benefit of AbstractReservoir implementing BlockingQueue other than reusing already defined interface currently. As CircularBuffer implements BlockingQueue and DefaultReservoir extended CircularBuffer, I made AbstractReservoir implement BlockingQueue interface as well. As AbstractReservoir implementations delegate BlockingQueue implementation to CircularBuffer, SpscArrayQueue or ArrayBlockingQueue, and both CircularBuffer and ArrayBlockingQueue implement BlockingQueue, if SpscArrayQueue adds support for BlockingQueue, it may be possible to use other methods from BlockingQueue in AbstractReservoirs.


Abstract Deepcell_Postprocessing.ipynb

Addresses issue #148 .

I made a few assumptions about the directory and file name structure for MIBItiff files. Let me know if a different format would be better.


Neural Network

http://www.cnblogs.com/xbf9xbf/p/4737525.html

https://github.com/mnielsen/neural-networks-and-deep-learning/blob/master/src/network.py

http://neuralnetworksanddeeplearning.com/about.html


Feature: Multiline text fields

There is a multiline prop in Material UI that allows you to render a textarea that starts with one line, and dynamically expands its heights to allow for new lines rather than scrolling. RMWC seems to only allow static height textareas, but I think this would be a convenient additional especially when migrating apps from Material UI.
It's worth noting that there's also a reusable TextareaAutosize component that's maintained by material UI but not coupled with their styles. I wonder if we could use this, but I don't have a very good understanding of how MDC's adapters work.

I agree, this would be very useful.
I've built a 101 of these in the past, there are some really easy ways to make it happen. I'll look into it.


Investigate why cognitive services has networkAcls: Allow

networkAcls: Allow was added to cognitive services here:
https://github.com/Azure-Samples/azure-search-openai-demo-csharp/pull/147/files#diff-8a64001dc63e4053382af7bbd6519e074e3a637a9e0a50b5b6e8ca136b4224ce
There's an issue to add it here #129
We should research the security implications of this and remove if not needed.

Work completed by #236. However, there's still #250 which is related and might require further investigation.


Invalid : Update "Clone From URL" mirror_address via GUI in v1.17.0/v1.17.1

Description
Invalid : Update "Clone From URL" mirror_address via GUI in v1.17.0/v1.17.1
But, valid in v1.16.9
Gitea Version
v1.17.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
linux
How are you running Gitea?
run by systemd
Database
SQLite

already fix by :
https://github.com/go-gitea/gitea/pull/20850


Spike: Research Solana Wallet Support in Masa React and/or Masa App

We are planning to deploy smart contracts to solana. To make sure we can actually use the contracts from our frontend with the given infrastructure we must research the different wallet types available for solana.
Acceptance Criteria

[ ] Try different solana wallets that work with rainbow kit
[ ] Make decision proposal how to proceed and which wallet to integrate
[ ] the wallet must support ledger hardware wallets

Output
List of most used Solana Wallets
Phantom
The most used Solana wallet on the ecosystem is Phantom. It could be compared with Metamask on its dominance on the market share. Aside from Solana, it has integration with:

Ethereum
Polygon
Bitcoin Taproot
Bitcoin Native Segwit

Solflare
There were some competitors back in 2021 to Phantom like Sollet eventually died off but one of the oldest that stayed strong in the community is Solflare. Lost the initial battle with Phantom due to UI/UX but still has a following.
Another thing worth noting is that it is Solana only, not like Phantom.
Ledger
Although this is a hardware wallet, it has its own wallet application to use across the web. Phantom and Solflare provide integration with Ledger but having Ledger on its own integrated into our apps might be worth considering.
How to proceed
First of all we must update rainbowkit and wagmi to the latest version. See #590
Based on the previous decision making on which wallets to support, I'm assuming that we would like to offer the most popular one as we are doing with Metamask for the SBT app. Thus my suggestion would be to just focus integrating Phantom since it is the most popular and it's already supported on Rainbowkit (Phantom's how-to, Rainbowkit's mention of Phantom).
Implementation steps (high-level)

Integrate Solana into the Masa-SDK
Add Solana as a valid chain/network on the Masa-React repo
Add Solana to the SupportedNetworks list
On the SBT app, add Phantom to the list of allowedWallets at src/layout/Providers.tsx

🟢 [UPDATE] Adding Phantom to our list of accepted and available wallets
First time working on SDK + Masa-React + SBT integration repos. In this case, I added the Phantom wallet but I'm not able to connect as shown on the video below. I think I'm not configuring the connecter well, will follow that path

🟢 [UPDATE] Adding Phantom to our list of accepted and available wallets
First time working on SDK + Masa-React + SBT integration repos. In this case, I added the Phantom wallet but I'm not able to connect as shown on the video below. I think I'm not configuring the connecter well, will follow that path

there is no configuration for solana networks on the sdk, therefore we can not connect to them right now. I am working on that right now

I think you must fix this with synthetic data somehow

I think you must fix this with synthetic data somehow (in the time being)

In other words, mocking the SDK, right?

Since I'm having trouble figuring it out from just looking and browsing the codebase, I'm gonna look for some PR where we add a new wallet to know how to do it.

DISCLAIMER: I'm not focusing on Solana itself since Phantom also works for ETH. When solana gets finally added to the SDK (SDK#334 we shall test this completely)

In other words, mocking the SDK, right?

probably yes, always keep in mind. a spike must not necessarly yield code or a PR but rather a solid base for decision making so it can be estimated or implemented easier in the future.

In other words, mocking the SDK, right?

probably yes, always keep in mind. a spike must not necessarly yield code or a PR but rather a solid base for decision making so it can be estimated or implemented easier in the future.

Okay, so I'll be updating the list of wallets to have in mind in this ticket's description and continue understanding how the integration of said wallets would work

Below you can find the same output of the spike I added to the Description of this ticket (sharing it here just to freeze it in case it changes).
Moving this to review since I find this work to be done. Nonetheless, I'd continue digging deeper into Masa-React to understand how the actual implementation would look like (due to my lack of context of this side of the application)

 Click to toggle expand/collapse

Output
List of most used Solana Wallets
Phantom
The most used Solana wallet on the ecosystem is Phantom. It could be compared with Metamask on its dominance on the market share. Aside from Solana, it has integration with:

Ethereum
Polygon
Bitcoin Taproot
Bitcoin Native Segwit

Solflare
There were some competitors back in 2021 to Phantom like Sollet eventually died off but one of the oldest that stayed strong in the community is Solflare. Lost the initial battle with Phantom due to UI/UX but still has a following.
Another thing worth noting is that it is Solana only, not like Phantom.
Ledger
Although this is a hardware wallet, it has its own wallet application to use across the web. Phantom and Solflare provide integration with Ledger but having Ledger on its own integrated into our apps might be worth considering.
How to proceed
Based on the previous decision making on which wallets to support, I'm assuming that we would like to offer the most popular one as we are doing with Metamask for the SBT app. Thus my suggestion would be to just focus integrating Phantom since it is the most popular and it's already supported on Rainbowkit (Phantom's how-to, Rainbowkit's mention of Phantom).
Implementation steps (high-level)

Integrate Solana into the Masa-SDK
Add Solana as a valid chain/network on the Masa-React repo
Add Solana to the SupportedNetworks list
On the SBT app, add Phantom to the list of allowedWallets at src/layout/Providers.tsx

First time working on SDK + Masa-React + SBT integration repos. In this case, I added the Phantom wallet but I'm not able to connect as shown on the video below. I think I'm not configuring the connecter well, will follow that path

i rewatched the video and i think its because we are not running the lastest wagmi and viem there is a PR for that that got stale: https://github.com/masa-finance/masa-react/pull/514

i have tried it myself and it does not seem to detect the phantom wallet extension at all on chrome in the current version of rainbowkit/wagmi:

@juanmanso have you tested connecting a ledger to the phantom wallet?

I haven't since I got no Ledger myself 😞

I haven't since I got no Ledger myself 😞

ok, i tested that, it works well with Phantom

Closed with these follow-up tickets:

#591
https://github.com/masa-finance/masa-next-sbt/issues/1444

From other projects that support both ETH and SOL I found they either:

Have a selector for network and then wallet (birdeye.so, marginfi, magiceden.io)
Use something else that integrates the selection into a single modal that does not differentiate networks (dextools.io)

Either way solutions are not straight forward as it seemed, so we need to reassess priorities :disappointed:

As pointed out by @H34D this depends on how we want to handle the UX on the app. Currently we connect the wallet first and then select the network.
With the current findings, we might need to first have the user select the network and then give them the connect button so they select wallets.
For this UX/UI change to be determined, we need to sync with @giovaroma to find a solution on then move forward with implementation.

As pointed out by @H34D this depends on how we want to handle the UX on the app. Currently we connect the wallet first and then select the network.
With the current findings, we might need to first have the user select the network and then give them the connect button so they select wallets.
For this UX/UI change to be determined, we need to sync with @giovaroma to find a solution on then move forward with implementation.

In parallel, I'll look at ways to connect any solana wallet into our frontend (with emphasis in supporting Phantom which is the one we found most popular)

As per solana's docs, I'm trying out dynamic. Looks promising so far.

As per solana's docs, I'm trying out dynamic. Looks promising so far.

It looks like it's working fine. The only issue is that it's a paid service. $99 for the first 2k MAUs and $0.05/MAU after that.

Joining to pair and try a free alternative here

Made a spike based on this docs integrating @solana/wallet-adapter-wallets:
Made it work but it diverges from our own UX on the SBT app:

Summary loom video to show current status (1.5x or more recommended 😄):
https://www.loom.com/share/111851fc49bb446c87eaf1c1de224d7a?sid=81cc0b47-7e23-444b-b4d3-fca3b7c5aec9

Added blocked label hoping it gives more visibility

Since it seems that we are gonna move forward with the free option, I'm trying to make the connection work on masa-react.
As it can be seen on the image below, the UI seems to be working but when clicking the Select Wallet button, nothing happens:

It may be due to the initiation of the providers, where we are passing an empty wallet's array whereas the example passes a new UnsafeBurnerWalletAdapter. We are not using it because by using it we break the Storybook receiving the following error message:

We are still investigating what's going on with this issue and will update soon

🟢 [UPDATE]
Fixed the webpack errors but still not popping up the Phantom wallet.
First I tried with this stack overflow suggestion to change the webpack.config.js. Tried everything and no success there. Then I asked myself if it might be a storybook issue rather than a global webpack thing (which would come up eventually but I'm testing on Storybook first).
So, I found this other stack overflow answer, that suggested to change the .storybook/main.js file which I did and errors are no longer showing.
Now, I have to figure out why Wallet connection is not showing on Phantom

Closing this task since we are not gonna make it to the deadline since we won't get the definitions in time


#48in24: Meetup 2024-08-20 and PHP is a featured language

Meetup will be the only exercise with PHP as featured language during #48in24! Let's prepare it well:

[ ] Run bin/configlet sync -u -e meetup --yes --docs --filepaths --metadata --tests include (updates the Markdown files and maybe tests.toml)

docs: instructions unsynced: meetup
metadata: unsynced: meetup

[ ] Drop strict types comments from test file and example code (these are useless)
[ ] Add and sync test meta data to tests (uuid / @testdox in DocBlocks)
[ ] Decide on adding / adjusting / ordering test cases to match current problem specs

Do not redesign the student's interface or add test cases that would invalidate existing community solutions. These are extra tasks, which should be discussed in advance.
In addition to the other sync-ing tasks, consider doing these:

[ ] Polish the tests to be really readable (e.g. add failure messages to assertions)
[ ] #617
[ ] Go through the track docs and update installation instructions, help resources etc.
[ ] Add approaches and articles

Hi,
If this is the featured task for next week, I could have a look today/tomorrow?

@sarad1p1ty Yes, you are welcome! The first 4 checkpoints are some kind of minimum points to have (but there might be nothing to do). And hopefully there are no surprises in the 4th point.
The data for UUID, @testdox nice test name and the 4th point is taken from this file: https://github.com/exercism/problem-specifications/blob/main/exercises/meetup/canonical-data.json
To locally test against the changed test cases, you may copy the example.php contents into the student stub Meetup.php and run PHPUnit against it: vendor/bin/phpunit --no-configuration --do-not-cache-result exercise/practice/meetup/MeetupTest.php. Or use composer ci if you solved the problems you had with that.
In case of any trouble: I do have little time until Monday. But I'll do my very best to answer all questions.

That's really helpful. Thank you!
I will let you know if I run into any problems.


After breaking the copper cell in survival, it stops storing embers

Apart from Embers Rekindled no other mods have been used

fixed in version 1.3.8


Error: Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free

Error: Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free
I have the same question

Hey - thanks for the report! This should generally only happen if either a) you're using an older version of node-inspect or something else is genuinely blocking the port. The latter would happen if you'd try to start 2 CLI debuggers on the same machine.
Can you share an example script & command that was used to generate the error?

there could also be the possibility, you are running node debug and try to run node inspect on another terminal.

Hi ,I got the same issue. Does any one know how to fix that?
The script is very simple:
var person={
name:'Michelle'
};
person.age=25;
person.name='Mike';
console.log(person);
Command: node inspect app.js

@Michelle0609 The most likely issue is that something else is running on port 9229. You can try running it on a different port using the following command:
node --inspect-port=9228 debug app.js

Alternatively you can try finding the thing blocking port 9229 on your machine. If neither of those options gets you anywhere, can you share the OS and version of node you're using?

Hi Jan,
Thanks for the email. I tried "node --inspect-port=9228 debug app.js"
But got the following issue
(node:12276) [DEP0068] DeprecationWarning: node debug is deprecated.
Please use node inspect instead.
There was an internal error in node-inspect. Please report this bug.
Timeout (2000) waiting for <IP_ADDRESS>:9228 to be free
Error: Timeout (2000) waiting for <IP_ADDRESS>:9228 to be free
at Timeout.setTimeout [as _onTimeout]
(node-inspect/lib/_inspect.js:63:14)
at ontimeout (timers.js:478:11)
at tryOnTimeout (timers.js:302:5)
at Timer.listOnTimeout (timers.js:262:5)
My OS is windows 10 and node version is 9.1.0
Thanks
Michellle
On Wed, Nov 8, 2017 at 1:18 PM, Jan Olaf Krems<EMAIL_ADDRESS>wrote:

@Michelle0609 https://github.com/michelle0609 The most likely issue is
that something else is running on port 9229. You can try running it on a
different port using the following command:
node --inspect-port=9228 debug app.js
Alternatively you can try finding the thing blocking port 9229 on your
machine. If neither of those options gets you anywhere, can you share the
OS and version of node you're using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node-inspect/issues/48#issuecomment-342688597,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Afd7iRdk8Sq1EQtu1js6bQbYKJmxf8caks5s0Q-CgaJpZM4O7CL9
.

Thanks for the details!
Wonder if there are any important error cases we're ignoring while trying. I don't have Windows around right now but I might be able to try debugging it when I'm back in the office tomorrow.

Thanks Jan!
On Wed, Nov 8, 2017 at 1:59 PM, Jan Olaf Krems<EMAIL_ADDRESS>wrote:

Thanks for the details!
Wonder if there are any important error cases we're ignoring while trying
https://github.com/nodejs/node-inspect/blob/49d7f88e3466d5b4b46886cb1f997b2dfc123d8b/lib/_inspect.js#L74.
I don't have Windows around right now but I might be able to try debugging
it when I'm back in the office tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node-inspect/issues/48#issuecomment-342695361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Afd7ib6rifgpRGVsHnd5p_inSo0jmD1lks5s0RkJgaJpZM4O7CL9
.

To anyone making it to this thread with this issue, make sure you are exiting out of inspect using ctrl^c, not ctrl^z. If you use ctrl^z the debugger is still blocking the port and the only way to fix it is to exit and reenter terminal.

@Michelle0609 I got a good laugh from your example because it was identical enough to mine to know we were doing the same tutorial! Cheers.

I'm not sure if anyone is still interested, but the solution is to use node --inspect instead of node inspect.

i'm having this issue as well and only have one terminal up still has same error
Node.js:12.2.0
OS: Windows 10
on VSC
$ node inspect app.js
Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free

Hey @4rch1m3d35 did you figure this out? I am having the same problem!

@kerryja nope nothing yet

I'm having the same problem, did anyone figure this out? I already tried changing the port, but the error message is the same.
Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free
No matter what port I'm typing

I'm having the same problem, did anyone figure this out? I already tried changing the port, but the error message is the same.

@AleArmengol To clarify your comment: Do you mean the message literally keeps talking about 9229 or just that you keep seeing timeouts for the various ports? If the port in the error stays the same, can you share the command you are using to set different ports?

this is the command to change ports
node --inspect=<IP_ADDRESS>:9230

To clarify, the command to start the CLI debugger on a custom port is node inspect --port=9230 path/to/script.js.
When using node --inspect, the error above shouldn't appear since that's the program being debugged, it's not starting the CLI debugger (node-inspect).

same issue here.
Node v10.13.0
Windows 10
Tried running in VSC and then another attempt in PowerShell.
Tried changing the ports and for all of then, the same error message appears.
Timeout (2000) waiting for <IP_ADDRESS>:12903 to be free
Timeout (2000) waiting for <IP_ADDRESS>:25612 to be free
Timeout (2000) waiting for <IP_ADDRESS>:5122 to be free

@victorgutemberg When you say "tried running in VSC", do you mean its integrated terminal? Also, can you share the exact command you ran?

I wonder if this is something specific to Windows since so far that seems to be a common thread. I don't have a Windows machine anymore to test that on, so if somebody could do some debugging, it would be much appreciated. :)

I ran this commands
node inspect --port=9229 app.js
Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free
node inspect --port=9230 app.js
Timeout (2000) waiting for <IP_ADDRESS>:9230 to be free

@jkrems yeah, I meant the integrated terminal. I've tried using the default cdm and PowerShell, same result on both.
And the command that I was running is the same as just mentioned by @AleArmengol.

same problem Windows 10 Pro, Build 18362:
node inspect myScript.js gets "Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free".
Reproduced on various ports (9228, 9227)
Also, not specific to the VSC terminal.  Reproduced in windows cmd and in powershell
Seems to work fine on the Windows 7 machine

I am also having this issue on different ports in Windows 10, both in VSC integrated terminal and regular powershell

Had the same issue, the problem was that I was starting multiple instances of docker containers running node app, so the first instance that starts occupies <IP_ADDRESS>:9229 and other instances cannot get to the port, thus trowing the error. After I set docker to start a single node app instance, error was gone

unfortunately i am not using docker and i am only starting one instance of the integrated terminal

Same problem : Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free
Windows x64 18362.207
Node 12.6.0

node debug ...
node inspect ...
node-inspect ...
all 3 of them gives the same error.
there is nothing using that port, nor firewall has any rules against. true for any port i tried with these command.
i tried with node v10.16.0 , v11.12.0 and v12.6.0 on latest Windows 10 1903. I have nothing installed to prevent ports, as port numbers are irrelevant as explained below.
i looked at the source code of node-inspect and saw "port=0" will open a random port. i tried command with "--port=0" and all above commands start at a random port without a problem. setting the port in chrome manually, debugging is also has no problem on chrome.
the problem is, exiting the debug process after a random port session, and trying to start a new session with appearently made available from previous session, this very same timeout error occurs.
in source code for "node-inspect"s "_inspect.js", i changed timeout to 5000 in "portIsFree" function, and voila, happy (!) ending. i am really not sure if this timeout is the real culprit behind the scenes, but nodejs developers should give it a try.
i am not much good on github forks and pull&push things, so can someone please do this change?

use --inspect-brk

guys this works. just type node --inspect-brk "your filename.js" for eg: mine is app.js so
node --inspect-brk app.js

@kaluogh  @Aayuarch

use --inspect-brk

it is nice to know it. this is working.
but it is not the solution for the timeout problem. also it is not opening the debugger session in the same console, and also it is a blocking process on that console.
it is still possible to connect from another terminal or chrome, but that means extra work to do
(ie. >node inspect localhost:9229 )
there is an issue here about timeout on opening ports, and this must be fixed by at least giving the host pc more time to initialize ports. that is why i asked if someone can supply a fix with an increased timeout value.

@kaluogh  @Aayuarch
use --inspect-brk
it is nice to know it. this is working.
BUT it is not the solution for the timeout problem. also it is not opening the debugger session in the same console, and more it is a blocking process on that console.
it is still possible to connect from another terminal or chrome, but that means extra work to do
(ie. >node inspect localhost:9229 )
there is an issue here about timeout on opening ports, and this must be fixed by at least giving the host pc more time to initialize ports. that is why i asked if someone can supply a fix with an increased timeout value.

yeah bro the debugger sesson isn't opening

@kaluogh  @Aayuarch
use --inspect-brk
it is nice to know it. this is working.
BUT it is not the solution for the timeout problem. also it is not opening the debugger session in the same console, and more it is a blocking process on that console.
it is still possible to connect from another terminal or chrome, but that means extra work to do
(ie. >node inspect localhost:9229 )
there is an issue here about timeout on opening ports, and this must be fixed by at least giving the host pc more time to initialize ports. that is why i asked if someone can supply a fix with an increased timeout value.

This command is for the debugging of node file via chrome ……… type : node --inspect-brk app.js
then open google chrome and type : chrome://inspect ………...Now you are all set to debug

In case it's unclear to anyone: this is not a matter of the port being in use. Using any port at all will result in the timeout error on Windows.
I know sometimes people on GitHub don't get what ports are and that they're in use. That isn't the case here.
node inspect --port=9230 file.js will fail.
node inspect --port=9999 file.js will fail.
node inspect --port=3000 file.js will fail.
The port is not in use.
As others also note

I created a pull request, and until it is accepted or at least reviewed, please do the following manual patch:

go to install folder of node's global packages. (it should be shown by npm config get prefix)
find node_modules\node-inspect\lib\ and open _inspect.js file
get to line 52, change timeout value to 9999 in portIsFree function

(also applies to issues #54 and #70)

Hrm @yilmazdurmaz  I don't have node-inspect as a global npm module. Are you sure that's the right file?

Thanks @yilmazdurmaz .
https://nodejs.org/en/docs/guides/debugging-getting-started/ says:

node-inspect
CLI Debugger supported by the Node.js Foundation which uses the Inspector Protocol.
A version is bundled with Node and can be used with node inspect myscript.js.

But I can't find node-inspect - npm config get prefix shows me C:\Users\mikem\AppData\Roaming\npm but the only files in node-modules are npm itself (which makes sense as avoid global modules, installing buil tools locally and using npx).
Do you know where the node-inspect bundled with node is installed?

(which makes sense as I avoid global modules, installing build tools locally and using npx in most cases).
Do you know where the node-inspect bundled with node is installed?

I havent used "npx" before, but is seems you need to do "npm install package_name -D" prior to use it.
If so, that means it is a local installation, and npm-inspect should reside in "your_project_folder/node_modules/npm-inspect" folder.
In other words, in step 1, go to any of your local projects' folder where you install&use node-inspect and continue steps in there.
Good Luck

but is seems you need to do "npm install package_name -D" prior to use it.

Well yes - and thanks for trying to help - but that's nor really the point. I don't want to install an additional copy of node-inspect, I want to use and fix the version included in node, as mentioned at  https://nodejs.org/en/docs/guides/debugging-getting-started/

A version is bundled with Node and can be used with node inspect myscript.js.

Ie, I want to run node inspect not node-inspect

Unfortunately the code of the bundled version is part of the node binary (node.exe). It's not stored separately on disk. You could also try the following:

Run node --inspect-brk your-script.js.
Run node inspect localhost:9229 in a separate terminal tab/window.

Restarting the target is now a bit more more annoying (it requires both restarting the actual script being debugged and then using the restart (or r) command in the node inspect repl to reconnect. But it may be easier as a workaround.

Ie, I want to run node inspect not node-inspect

The thing is you (any other coder to have the same issue) have some options here:

you wait for a fix until @jkrems is available to publish a fix
you may try his suggestion above which is exhaustive
or you can try (as I myself prefer) the third option mentioned in the same article you linked with the fix I described.

The latest version can also be installed independently (e.g. "npm install -g node-inspect") and used with "node-inspect myscript.js"

The choice is yours,
Cheers :)

@yilmazdurmaz yeah I know the --inspect-brk workaround (and yes that works fine, thanks for suggesting it) but I was hoping to be able to land a patch in node itself (I still don't get if node-inspect the package is actually the same thing as node inspect since I assume the later may involve some native code.

(I still don't get if node-inspect the package is actually the same thing as node inspect since I assume the later may involve some native code).

The way it works is that the code for this library gets copied into the node source (example PR) on a somewhat regular basis. Node then runs the code using its internal require system that also powers things like the JS bits of built-in modules like fs. So if a fix in node-inspect is merged, it can be forwarded to node itself fairly easily without any additional code.

@mikemaccana  Today, I am in a bit of debugger/patcher mood, so here is 4th, but surely unsupported method. After this, node inspect works without timeout error.

find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value, I suggest 9999.

While doing that, you will notice that Node.js actually holds packages almost as is. If you look at the beginning of the file, you will see the "native" codes. Native codes are only read by machine logic (assembler). In contrast, packages are hold as their human readable form.
Actually I didn't expect this result. Anyone may apply this method on their free will, just should not expect support if something else gets broken.

still don't get if node-inspect the package is actually the same thing as node inspect since I assume the later may involve some native code).

find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value

Woo @yilmazdurmaz that was what I was confused about! So node.exe includes the JS itself. Mystery solved. Thanks! 💯

use --inspect-brk

Thanks, it worked for me!

use --inspect-brk

not working for me... :(

@gauthamgauda ... and? what happens when you try?

@yilmazdurmaz
Thanks! I opened node.exe in a hex editor and changed delay in portIsFree from 2000 to 3000. That was enough. Your comment was very helpful.
Windows 10 x64
Node 10.16

Anyone knows whats the difference between node inspect app.js & node --inspect app.js
I was trying the first one and was facing the same Timeout issue. When i tried the latter it worked fine.

Anyone knows whats the difference between node inspect app.js & node --inspect app.js

Yeah, those two commands look more similar than they should. The difference is:

node --inspect: Run app.js but expose the remote debugging interface that things like vscode, Chrome devtools, Intellij, etc. can attach to. Otherwise app.js will run just like always and have full control over the terminal.
node inspect: Start the interactive CLI debugger that's bundled with node. It's an alternative for visual debuggers like vscode or Chrome devtools. The CLI debugger will then use node --inspect to start the script in a separate process and attaches to it.

The relationship between the two is more obvious in the more explicit flow that also supports remote debugging across machines:
# Start app.js with the inspect interface exposed, by default on port 9229:
node --inspect app.js
# In a separate terminal, start the inspect client against port 9229:
node inspect -p 9229

Now the CLI debugger (node inspect) is connected to the node process with the debug interface enabled (node --inspect). Hope that helps. :)

Anyone knows whats the difference between node inspect app.js & node --inspect app.js

Yeah, those two commands look more similar than they should. The difference is:

node --inspect: Run app.js but expose the remote debugging interface that things like vscode, Chrome devtools, Intellij, etc. can attach to. Otherwise app.js will run just like always and have full control over the terminal.
node inspect: Start the interactive CLI debugger that's bundled with node. It's an alternative for visual debuggers like vscode or Chrome devtools. The CLI debugger will then use node --inspect to start the script in a separate process and attaches to it.

The relationship between the two is more obvious in the more explicit flow that also supports remote debugging across machines:
# Start app.js with the inspect interface exposed, by default on port 9229:
node --inspect app.js
# In a separate terminal, start the inspect client against port 9229:
node inspect -p 9229

Now the CLI debugger (node inspect) is connected to the node process with the debug interface enabled (node --inspect). Hope that helps. :)

Thanks! got the diff b/w the two 👍

guys this works. just type node --inspect-brk "your filename.js" for eg: mine is app.js so
node --inspect-brk app.js @ @ @ @yilmazdurmaz @kerryja

node: ../deps/uv/src/unix/core.c:117: uv_close: Assertion `!(((handle)->flags & (UV_CLOSING | UV_CLOSED)) != 0)' failed.
Aborted (core dumped)```

@jkrems  is there a way you may put a summary at the end and then put this discussion on a hold? it is too long that people miss the important parts we talked about.

I have tried --inspect-brk app.js,  it works,
But I can't debug in crome when using this method. I press the play button in crome inspect, and nothing happens in the even I had typed debugger in my code.
And after typing --inspect-brk app.js the timeout error is happening again. So have anyone solved this issue?  How do I get out of this timeout error?

use --inspect-brk

you're magician

@mikemaccana Today, I am in a bit of debugger/patcher mood, so here is 4th, but surely unsupported method. After this, node inspect works without timeout error.

find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value, I suggest 9999.

While doing that, you will notice that Node.js actually holds packages almost as is. If you look at the beginning of the file, you will see the "native" codes. Native codes are only read by machine logic (assembler). In contrast, packages are hold as their human readable form.
Actually I didn't expect this result. Anyone may apply this method on their free will, just should not expect support if something else gets broken.

you are a god!

any Of This is not working

try this:
node --inspect-brk app.js
it works fine with me.

node --inspect-brk app.js solves the problem

Thanks Now its Working😅

We need to move the
node --inspect-brk app.js to the top of this feed instead of the bottom.

"--inspect" and "--inspect-brk" does things in slight different ways, and depending on what you need the second does the jobs.
we have a fix about the "timeout" for "--inspect" already committed&merged, so possibly the next node version change will include it. as for the fix, it is an increased value on the setTimeout function, 2000 to 9999, because the problem here is that Windows is somehow slow on taking the requested port, about 3-5 seconds, thus timeout was happening.
keep an eye on it and update your node installation when the fixed one comes out.

Update: A change increasing the timeout has landed here and there's an open PR to pull it into node (https://github.com/nodejs/node/pull/33447).

Error: Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free
I have the same question

try node --inspect-brk filename.js

Still I am facing issue with debugging. Didn't worked for me. Using node version v12.18.0.
node --inspect-brk index.js
Debugger listening on ws://<IP_ADDRESS>:9229/93410f83-bdd1-488d-bcc9-595904b41697
For help, see: https://nodejs.org/en/docs/inspector

Go to your chrome browser and enter the url: chrome://inspect
then you will find something under remote target, then just click on the inspect option given over there and you are good to go.
If you donot find anything under remote targets then click upon configure option there and enter the ip that you got on the console that is <IP_ADDRESS>:9229

@vivekvking , i have updated chrome://inspect and added configuration - discover network targets as <IP_ADDRESS>:9229. But the issue resists to
Error: Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free
then realized, under https://nodejs.org/en/docs/guides/debugging-getting-started/  for latest version we need to install independently [npm install -g node-inspect] and  [node-inspect myscript.js] worked for me.

If you want to debug your code use    node --inspect yourJs.js
not    node inspect yourJS.js

Tried everything and none worked but
node --inspect app

@mikemaccana Today, I am in a bit of debugger/patcher mood, so here is 4th, but surely unsupported method. After this, node inspect works without timeout error.

find a hex editor, open node.exe, search for portIsFree, currently 2 results comes up, one of them has timeout = 2000 nearby, replace it with a higher value, I suggest 9999.

While doing that, you will notice that Node.js actually holds packages almost as is. If you look at the beginning of the file, you will see the "native" codes. Native codes are only read by machine logic (assembler). In contrast, packages are hold as their human readable form.
Actually I didn't expect this result. Anyone may apply this method on their free will, just should not expect support if something else gets broken.

You're great❤❤❤

Typed up a whole gosh darn thing and after reading the docs I got it working finally! After installing globally with "npm install -g node-inspect" and restarting the terminal, I was able to use "node-inspect fileName.js" and it successfully starts and keeps the debugger running in that terminal. I suggest trying that if you're still struggling. I did try "node inspect" and "node --inspect" but they didn't work. What a strange issue!

Hey there all future newcomers to the topic (and some old still struggling).
TL:DR - we have many possible solutions. please try to read comments.
I wish comments were not this long and we had the habit of reading long things, impossible by our nature.
just know that, we know the problem and we have the solutions.
PROBLEM: newer version of windows is slow to assign debug port that takes about 3-5 seconds, but this debug utility had a predefined (working in the past) 2 seconds timeout. this is the only reason we have this issue.
SOLUTION: we already have the fix submitted to Node.JS codebase, and sometime in the future, depending on Node's own release schedule. until then there are many working solutions depending on your expectation, so please, please, please read these comments and try solutions.
thanks for patience
PS: the solution in above comment works now without any modification because we really have it fixed here. two post above works too because of the nature of the problem; we need a simple timeout increase.
PS: I really hope new readers will at least read the last post in the line, and keep this one as the last post.

To clarify, the command to start the CLI debugger on a custom port is node inspect --port=9230 path/to/script.js.
When using node --inspect, the error above shouldn't appear since that's the program being debugged, it's not starting the CLI debugger (node-inspect).

I'm having

i'm having this issue as well and only have one terminal up still has same error
Node.js:12.2.0
OS: Windows 10
on VSC
$ node inspect app.js
Timeout (2000) waiting for <IP_ADDRESS>:9229 to be free

Same Issue is there but this Command Works for Mine.
node --inspect=<IP_ADDRESS>:9230 app_name.js
Thanks

Hi all
Latest Node v12.19.0 and v15.0.1 now has the fix in them (timeout set to 9999ms). Please update your installations when you are ready.
@jkrems , this #48 and #54 issues should be safe to be marked as solved.


se model loading error!!!

! pip install modelscope==1.6.1 -f https://modelscope.oss-cn-beijing.aliyuncs.com/releases/repo.html
or
! pip install modelscope==1.7.0 -f https://modelscope.oss-cn-beijing.aliyuncs.com/releases/repo.html
! pip install tts-autolabel==1.1.2 -f https://modelscope.oss-cn-beijing.aliyuncs.com/releases/repo.html

得到报错
[SpeakerEmbeddingProcessor] Speaker embedding extractor started
[SpeakerEmbeddingProcessor] se model loading error!!!
[SpeakerEmbeddingProcessor] please update your se model to ensure that the version is greater than or equal to 1.0.5
[SpeakerEmbeddingProcessor] try load it as se.model
[SpeakerEmbeddingProcessor] Speaker embedding extracted successfully!
Processing speaker embedding done.
Processing done.

please try to use the latest modelscope library and latest model


Add testString parameter

Hi Sindre,
It would be a nice-to-have option to specify a different test string to detect the indentation. If the main string is whitespace-only or kind of broken, it won't work.
My use case: I am now writing a postCSS plugin that unwraps a container, and can only change the node.raws.before (usually some newlines and spaces/tabs) - so need a different source to analyse the indentation.
Hope it does not break the simplicity.
Cheers,
Bartosz

Closing since replaced by a different approach - #9. Has the TS def issue fixed.


sylt-format

Something that can parse the syntax and format it into something that is "correct".
This tool could then also be used to port versions of the code.

Continued in #374


Accessing file size on complete

Hi,
I apologize that this is not an issue but a general question.
So I know file size is available in the file added action, but how do I access file size on file complete to store in the database like your demo?

Hi @mmacdonald1 ,
for this you can use the dbms_lob.getlength database function, e.g.
SELECT c001 AS filename,
       c002 AS mime_type,
       d001 AS date_created,
       n001 AS file_id,
       blob001 AS file_content,
       dbms_lob.getlength(blob001) AS file_size_byte
  FROM apex_collections
 WHERE collection_name = 'DROPZONE_UPLOAD';


Swap Nevada GPS network prod and dev servers

Benefit
Success Criteria

Generate new NAD83 coordinates using OPUS projects
Connect all existing stations to new server

Benefit -
The current NevadaGPS Network is setup with an outdated coordinate frame NAD83/94 (HARN) which is not compatible with current NGS coordinates, and by configuring a new server using NAD83 (2011) coordinates the GPS network will be compatible with todays equipment and software.
Success Criteria -
-Work with DTS Hosting to bolster up the current Dev server (grwgps02gp) to make it capable of running Trimble Pivot.
-Work with Cloud hosting team and networking to assign correct IP Addresses

Was this completed also?

All of these items have been completed and grwgps02gp is now active and being used in a NAD83 (2011) coordinate frame using IP address <IP_ADDRESS>.


Tests failing with docker command 'CreateNetwork' returned with non-zero exit code

Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=807077
Build error leg or test failing: Aspire.Playground.Tests.*
Pull request: https://github.com/dotnet/aspire/pull/5684
Full error message: docker command 'CreateNetwork' returned with non-zero exit code 1: command output: Stdout: '' Stderr: 'Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network

Error Message
Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "docker command 'CreateNetwork' returned with non-zero exit code",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation
Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=807077
Error message validated: [docker command 'CreateNetwork' returned with non-zero exit code]
Result validation: :white_check_mark: Known issue matched with the provided build.
Validation performed at: 9/13/2024 6:49:19 AM UTC

Report

Build
Definition
Test
Pull Request

807341
dotnet/aspire
Aspire.Hosting.Milvus.Tests.MilvusFunctionalTests.Aspire.Hosting.Milvus.Tests.MilvusFunctionalTests.WithDataShouldPersistStateBetweenUsages
dotnet/aspire#5701

807292
dotnet/aspire
Aspire.Playground.Tests.AppHostTests.Aspire.Playground.Tests.AppHostTests.TestEndpointsReturnOk
dotnet/aspire#5699

807319
dotnet/aspire
Aspire.Hosting.SqlServer.Tests.SqlServerFunctionalTests.Aspire.Hosting.SqlServer.Tests.SqlServerFunctionalTests.WithDataShouldPersistStateBetweenUsages(useVolume: False)

807077
dotnet/aspire
Aspire.Playground.Tests.AppHostTests.Aspire.Playground.Tests.AppHostTests.TestEndpointsReturnOk
dotnet/aspire#5682

Summary

24-Hour Hit Count
7-Day Hit Count
1-Month Count

0
4
4

After multiple running, I got this error too:
Aspire.Hosting.Dcp.dcpctrl.NetworkReconciler: Error: could not create a network	{"NetworkName": {"name":"aspire-network"}, "Reconciliation": 2, "error": "docker command 'CreateNetwork' returned with non-zero exit code 1: command output: Stdout: '' Stderr: 'Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network\n'"}

This problem occurs because the app-host doesn't clean up networks after stop/shutdown.
This is the list of networks on my machine.

cc @davidfowl @danegsta

This seems to primarily be an issue with Docker being slower to respond when running multiple tests in parallel; there's a timeout set on the resource cleanup to avoid leaving zombie processes if cleanup never completes, but it's too aggressive when running this many simultaneous resources. In the short term we're making some tweaks to try to improve the reliability of resource cleanup and test runs (including a longer default+configurable duration for the resource cleanup phase and retry on network creation if a subnet wasn't available from the default pools) that should land today.

@radical are we still seeing this issue with the latest DCP updates? We should be better about cleaning up resources as well as retrying to reconnect if we can't initially allocate a network subnet.

@radical are we still seeing this issue with the latest DCP updates?

I haven't seen this been hit in the last few days. We can close the issue after some time, since it still has entries in the last 7 days.

We should be better about cleaning up resources as well as retrying to reconnect if we can't initially allocate a network subnet.

We are doing explicit docker network prune -f at the beginning, and end of each test run on helix. Is that no longer needed?

It doesn't hurt to keep that prune in to be on the safe side; Docker is pretty limiting in the maximum number of default networks you can create.

What's the timeout for these networks getting cleaned up by dcp? Just trying to get a sense of how many networks would be too many (IOW, dcp hasn't been able to cleanup) at end of a test run of N minutes.

Current default timeout is 2 minutes to cleanup resources, but it can also be configured via environment variable (DCP_SHUTDOWN_TIMEOUT_SECONDS sets the timeout in seconds).

This hasn't been hit in weeks now. Closing.


Add fremont for volume

Coverage remained the same at 71.281% when pulling 1b027c8719daa160ab20daaa09317594de446693 on eatonphil:add-fremont-for-volume into 7c350da7fb9097a881f402197153503db8d2e242 on linode:master.


add getVisibleChildNodes

I don't know if this is too niche, but I've used this in my past projects while iterating over page elements to find elements that contain text & images or images and other elements. Any elements that only have images then get a style="line-height:0;" applied to them

Additionally, I don't think this overlaps much with elementIsVisibleInViewport as this isn't checking if the child node is currently visible in the browser but rather returns all the child nodes (text, elements) that the browser can render.


fix wrong tag url in sitemap

My site always generate wrong tag urls when using this plugin, so I just dived into it for details. I find that this plugin always encode Chinese characters twice so that urls with Chinese characters can't be visited right. I guess the tag.permalink would result encoded link so that the function of encodedURLAndEscape just works the wrong way.
Here's my sites' package version:
hexo: 4.2.1
hexo-cli: 3.1.0
os: Darwin 19.6.0 darwin x64
node: 14.5.0
P.S. I only changed the tag because I didn't know whether others are use the same way.
Thanks.

Here's the wrong tag sitemap from my site:
http://ryzn.me/tag-sitemap.xml

Here's the wrong tag sitemap from my site:
http://ryzn.me/tag-sitemap.xml

I've fix this bug, so that content of this url is correct right now.


Make cycling torque map with up/down category

This involves to create a new field called for example up_down and run UPDATE to get for every point if the cyclist is going up or down using a window function resulting in  up or down  result so you can later use it on a widget or for a category torque.
TIP: Here there's an example of something similar.

hey @jsanz - happy ato work on this ticket, but would need some help understanding the SQL query to generate the UP or DOWN result. if you have time to touch base on friday, that would be great or we can talk when I get back from vacation.

Let's talk today yes, no problem

Hey Jorge! I added directions on styling by category, can you remind me in what other ways you wanted me to show styling the data in the tutorial? So far I just have the basic info on styling by value. With  my vacation, I have forgotten the other way(s) we discussed styling the data. :)

That was all, if you have added animated map by category that's all was
needed. I can't remember if I finally uploaded the dataset with the up/down
field to the repo
On Tue, Jan 24, 2017 at 9:24 PM, Michelle Chandra<EMAIL_ADDRESS>wrote:

Hey Jorge! I added directions on styling by category, can you remind me in
what other ways you wanted me to show styling the data in the tutorial? So
far I just have the basic info on styling by value. With my vacation, I
have forgotten the other way(s) we discussed styling the data. :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/carto-workshop/issues/15#issuecomment-274927695,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALfaDyTlbZ7R17Bk3cfSQzD1v4FdMqMks5rVl4PgaJpZM4LDSe5
.

--
Jorge Sanz
Solutions Engineer
CARTO - Predict through location

You did upload the dataset with the up/down field in the repo! I will modify what I have to be about creating an animated category map.
However, it seems to further customize the colors, the user would need to change the cartocss. Did you end up reporting the issues with the UI for changing colors?

yep https://github.com/CartoDB/cartodb/issues/11250
On Wed, Jan 25, 2017 at 6:03 PM, Michelle Chandra<EMAIL_ADDRESS>wrote:

You did upload the dataset with the up/down field in the repo! I will
modify what I have to be about creating an animated category map.
However, it seems to further customize the colors, the user would need to
change the cartocss. Did you end up reporting the issues with the UI for
changing colors?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CartoDB/carto-workshop/issues/15#issuecomment-275166931,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALfaBdLPz1OMaYWf0ljshJcKUEhuh9iks5rV4BVgaJpZM4LDSe5
.

--
Jorge Sanz
Solutions Engineer
CARTO - Predict through location

Changes pushed, ready to be reviewed!


num_epochs does not work in modified cifar10

I am running cifar10 examples and have made some changes. I would like to evaluate every example only once, while the original example can only do mass evaluation. My question are described here. And was suggested by changing function 'tf.train.string_input_producer'.
But it failed and I also found a similar question but with no final solution given, @mrry .
And this problem can also solve other problems including this one here.
Thank you in advance.

Dear All,
I managed to solve it at the cost that I have to set every thread reads only one test example. I think the queues and threading mechanism of TensorFlow should re-design: the threading should be able to read the rest of queues automatically.
Thank you very much. And I would also appreciated if better solution to be given

What version of tensorflow are you using on what operating system and version? Have you tried it with r0.9?
Original Error was
with NotFoundError: Tensor name "input_producer/limit_epochs/epochs" not found in checkpoint files

I used 0.8 and I believe the problem, that evaluation on each example only once, need redesign. Although in the post, I proposed a go-round solution, but it can only applied to test. For real evaluation, each example should feed and evaluate only once, I still can not find a proper way.

Can you confirm it is still a problem in 0.9?

Automatically closing due to lack of recent activity. Please reopen if additional information becomes available.


Allow limited processing of imported high scores

Aims to resolve https://github.com/ppy/osu-infrastructure/issues/25.
This PR allows a limited subset of PP-related processors to run for legacy scores, and changes the score import job to push imported scores for aforementioned processing when running in watch/indefinite mode.
I am very intentionally opening this as draft to first ensure that I am in the correct wheelhouse when it comes to what the issue above intended to convey. Therefore, this is extremely untested code. It passes tests, but that means nothing for the import job. I have not attempted to run the import job. It only works in my head. Please give this a quick general review, but please do not merge this until I have tested it.
I will attempt to run it and test it, to the best of my ability, using ad-hoc means, namely manual database inserts - these are the only means I have, given that stable and surrounding infra is a closed-off system - when I receive confirmation that this looks roughly correct when it comes to the general shape and meets the general expectations. I'll also add extended test coverage for the pp processors, ensuring that they do in fact process legacy scores.

Direction looks correct, if we ignore the conflicts with the other PR 😅 .

Have rebased (fixing no less than two back-to-front conditionals along the way), but haven't tested properly yet. Hopefully will get that done tomorrow.

So I began trying to test this. Didn't get very far, because of other screw-ups (tl;dr: I accidentally nuked my local osu-web setup's db by running this project's test suite on it, as it truncates osu_beatmaps among others), but there is one apparent possible issue.
To be sure whether it is an issue, I would need an answer to a few questions that requires implicit knowledge, and those are:

What inserts rows to score_process_queue?
Will whatever inserts these rows continue to insert said rows after osu-performance is shut down?

Because if it will not, then there are several checks in the import job for watch mode that rely on score_process_queue to be able to tell where to pick up from. And I'm not sure what to do with those. The answer is probably delete them?
When I attempted to run the job, the following happened:

I ran queue import-high-scores without ever having ran anything before. It correctly recognised that I was "bootstrapping a local dev setup" - after I fixed a defective check (see https://github.com/ppy/osu-queue-score-statistics/pull/181/commits/353795f840098d7ef1713b6d14b4facca2fac444) - and proceeded to import all seeded high scores from start to end. This is good.
Then I ran queue import-high-scores again, hoping to enter watch mode proper. But I was not attempting to even simulate score_process_queue insertions in any way, so the job again assumed I had never done anything before and was trying to bootstrap, and thus tried to import everything again, which seems... undesirable?

And so I'm not super sure where I'm going wrong here, but something isn't quite right. Either I'm not manually simulating stable submission properly, or there is an actual issue with the code.

What inserts rows to score_process_queue?

Score submitting, web-10, which will continue happening into the foreseeable future.

Then I ran queue import-high-scores again, hoping to enter watch mode proper. But I was not attempting to even simulate score_process_queue insertions in any way, so the job again assumed I had never done anything before and was trying to bootstrap, and thus tried to import everything again, which seems... undesirable?

You'll need to insert into the score_process_queue table yeah. If there's no rows it assumes there's no ongoing processing. This is expected behaviour since it's guaranteed to have rows on production.

You'll need to insert into the score_process_queue table yeah. If there's no rows it assumes there's no ongoing processing. This is expected behaviour since it's guaranteed to have rows on production.

Right. osu-performance updates this table to mark completion of processing. So I assume if this job is to eventually be the replacement for osu-performance, then I presume I will need to mimic that too? (maybe behind a flag?)

If we're back-populating the old table then that will be the case, yes.
An alternative which may sit better is leaving osu-performance running and updating osu_scores_*_high but not updating user totals.

Haven't tested it, but have done the above in https://github.com/ppy/osu-performance/pull/177

I'm going to merge this as it's too hard to maintain multiple code changes on this single file with these changes pending any longer.


Volume Control Issue on iPhone7

We are using the microphones input to do some DSP and AudioKit for output. Now with the current setup we are having some volume issues. So pulling down the volume does notmute it. On iphone7 we are also experiencing extremely loud playback from AudioKit.
Any idea what the reasons could be? Here is the demo project. Its working fine for lower devices (until iphone6splus) but starting from iphone7 the volume is highly unpredictable. Especially on iphone7 we cannot properly control the volume
https://github.com/mlostekk/AudioKitSampleRate/tree/issue/volumeControl
The branch is issue/volumeControl
P.S. Maybe worth to mention, we are using the audio component subtype kAudioUnitSubType_VoiceProcessingIO to enable echo cancellation

I'm not sure what your issue is, but I will say that AKAudioPlayer is no longer being maintained. You might try your project with AKPlayer instead.

to be honest, meanwhile i think its not audiokit related. I have created this SO question. The volume control issues seem to happen with the voiceProcessingIO.
https://github.com/mlostekk/AudioKitSampleRate/tree/issue/outputVolumeNoAudiokit (branch outputVolumeNoAudiokit)

I assume AudioKit just amplifies this issue that is already underlying. The volume control is pretty weird when AK is used on top of this setup as described in the branch / link above

Since you don't think its AudioKit, I think I will close the issue here. Reopen if necessary. I upvoted the question on SO, hopefully with a high enough rating someone will answer it.