[Bootstrapper] Should not request Github while cache is valid

Description
The following behavior was noticed in a netcore project when restoring stuff with the bootstrapper in magic mode:
EXEC : The remote server returned an error : (429) Too Many Requests. (Github - cached (temporarily ignore updates)) [C:\PROJ\FAKE\src\app\Fake.DotNet.Testing.NUnit\Fake.DotNet.Testing.NUnit.fsproj]
C:\PROJ\FAKE\.paket\Paket.Restore.targets(17,5): error MSB3073: The command ""C:\PROJ\FAKE\.paket\paket.exe" restore --project "C:\PROJ\FAKE\src\app\Fake.DotNet.Testing.NUnit\Fake.DotNet.Testing.NUnit.fsproj" --target-framework netstandard1.6" exited with code -1. [C:\PROJ\FAKE\src\app\Fake.DotNet.Testing.NUnit\Fake.DotNet.Testing.NUnit.fsproj]
EXEC : The remote server returned an error : (429) Too Many Requests. (Github - cached (temporarily ignore updates)) [C:\PROJ\FAKE\src\app\Fake.DotNet.Testing.XUnit2\Fake.DotNet.Testing.XUnit2.fsproj]
C:\PROJ\FAKE\.paket\Paket.Restore.targets(17,5): error MSB3073: The command ""C:\PROJ\FAKE\.paket\paket.exe" restore --project "C:\PROJ\FAKE\src\app\Fake.DotNet.Testing.XUnit2\Fake.DotNet.Testing.XUnit2.fsproj" --target-framework netstandard1.6" exited with code -1. [C:\PROJ\FAKE\src\app\Fake.DotNet.Testing.XUnit2\Fake.DotNet.Testing.XUnit2.fsproj]
EXEC : The remote server returned an error : (429) Too Many Requests. (Github - cached (temporarily ignore updates)) [C:\PROJ\FAKE\src\app\Fake.IO.Zip\Fake.IO.Zip.fsproj]
C:\PROJ\FAKE\.paket\Paket.Restore.targets(17,5): error MSB3073: The command ""C:\PROJ\FAKE\.paket\paket.exe" restore --project "C:\PROJ\FAKE\src\app\Fake.IO.Zip\Fake.IO.Zip.fsproj" --target-framework netstandard1.6" exited with code -1. [C:\PROJ\FAKE\src\app\Fake.IO.Zip\Fake.IO.Zip.fsproj]

It seems like the bootstrapper still does a lot of requests when it shouldn't (that would improve speed in this scenario as well)
$ .paket/paket.bootstrapper.exe --max-file-age=720 --run --version
Checking Paket version (version 5.0.0-beta006 requested)...
Hash file of version 5.0.0-beta006 not found in cache.
Starting download from https://github.com/fsprojects/Paket/releases/download/5.0.0-beta006/paket-sha256.txt
Hash file of version 5.0.0-beta006 not found in cache.
Starting download from https://github.com/fsprojects/Paket/releases/download/5.0.0-beta006/paket-sha256.txt
No hash file of version 5.0.0-beta006 found in cache.
Copying version 5.0.0-beta006 from cache.
Done in 1.33 second(s).
Paket version 5.0.0-beta006

Known workarounds
Do not use magic mode

/cc @vbfox

It's a regression introduced by the hash file download, the cache for it never works (File is download to a temporary location and never moved to the cache) it's not really linked to magic mode :)
Any use of the boostrapper would produce the same effect.
I'll fix it anyway 🦊

@vbfox Yeah I know (see my bug report which is without magic mode). It's just that this bug renders magic mode unusable with solutions containing a couple of netcore projects, because github is blocking quite fast...
Yeah I fix would be highly welcome because it is quite frustrating that I had to remove magic mode for now. (Sorry usually I'd just fix this myself but atm I'm trying to focus on a FAKE 5 release)


fix ulimits and isolation fields

https://github.com/rancher/rancher/issues/6614

https://github.com/rancher/rancher/issues/6587

@alena1108  Could you please review this PR? tested locally, it should fix the issues.

@StrongMonkey please add corresponding test logic to test_transform_inspect.py

@cjellick PR updated

@cjellick flake8 error corrected.


[TFLite] Add int8 and int16x8 support for LOG operator

Hello,
This PR adds int8 and int16 quantization support for the LOG operator using a lookup table.
Thanks,
Thibaut

Hi @Tessil, one error left to fix. The E2E tests (whose params are in part generated by elementwise.py) are failing. Specifically when quant_16x8=True for rsqrt fails with "Type INT16 is unsupported by op Rsqrt." Then, some of the log tests are generating different numbers from what is expected. Let me know if you have any troubles reproducing, thanks.

Hi @grantjensen I wasn't able to reproduce the issues.
I ran the following two commands with success:
bazel run //tensorflow/lite/testing:generate_examples -- --zip_to_output=log -- --output_path=test
bazel test //tensorflow/lite/kernels:elementwise_test
I have updated the PR though to remove QI16 from the MLIR TFL_LogOp definition as it's not necessary currently (no official support for int16x8 MLIR quantizer).

 bazel test //third_party/tensorflow/lite/testing:zip_test_log
 bazel test //third_party/tensorflow/lite/testing:zip_test_rsqrt


fix(nextjs): Handle __nextGetStaticStore returning undefined

Description
Bug fix: Handle nextGetStore.getStore() returning undefined. Previously a TypeError would occur, when pagePath was accessed.

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/astro
1.0.12-snapshot.v5a90f37

@clerk/backend
1.6.3-snapshot.v5a90f37

@clerk/chrome-extension
1.2.1-snapshot.v5a90f37

@clerk/clerk-js
5.14.1-snapshot.v5a90f37

@clerk/elements
0.13.0-snapshot.v5a90f37

@clerk/clerk-expo
2.1.1-snapshot.v5a90f37

@clerk/express
0.0.28-snapshot.v5a90f37

@clerk/fastify
1.0.30-snapshot.v5a90f37

@clerk/localizations
2.5.8-snapshot.v5a90f37

@clerk/nextjs
5.3.1-snapshot.v5a90f37

@clerk/clerk-react
5.4.1-snapshot.v5a90f37

@clerk/remix
4.2.14-snapshot.v5a90f37

@clerk/clerk-sdk-node
5.0.27-snapshot.v5a90f37

@clerk/shared
2.5.1-snapshot.v5a90f37

@clerk/tanstack-start
0.2.1-snapshot.v5a90f37

@clerk/testing
1.2.10-snapshot.v5a90f37

@clerk/themes
2.1.20-snapshot.v5a90f37

@clerk/types
4.13.1-snapshot.v5a90f37

@clerk/ui
0.1.8-snapshot.v5a90f37

Tip: Use the snippet copy button below to quickly install the required packages.
@clerk/astro
npm i<EMAIL_ADDRESS>--save-exact

@clerk/backend
npm i<EMAIL_ADDRESS>--save-exact

@clerk/chrome-extension
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-js
npm i<EMAIL_ADDRESS>--save-exact

@clerk/elements
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-expo
npm i<EMAIL_ADDRESS>--save-exact

@clerk/express
npm i<EMAIL_ADDRESS>--save-exact

@clerk/fastify
npm i<EMAIL_ADDRESS>--save-exact

@clerk/localizations
npm i<EMAIL_ADDRESS>--save-exact

@clerk/nextjs
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-react
npm i<EMAIL_ADDRESS>--save-exact

@clerk/remix
npm i<EMAIL_ADDRESS>--save-exact

@clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>--save-exact

@clerk/shared
npm i<EMAIL_ADDRESS>--save-exact

@clerk/tanstack-start
npm i<EMAIL_ADDRESS>--save-exact

@clerk/testing
npm i<EMAIL_ADDRESS>--save-exact

@clerk/themes
npm i<EMAIL_ADDRESS>--save-exact

@clerk/types
npm i<EMAIL_ADDRESS>--save-exact

@clerk/ui
npm i<EMAIL_ADDRESS>--save-exact


Spyder fails to start on Ubuntu 16.10: No module named 'PyQt4.QtWebKit'

Description of your problem
What steps will reproduce the problem?

Install spyder3 on a new Ubuntu 16.10 system.
Open terminal
Type spyder3 and press Enter.

What is the expected output? What do you see instead?
~$ spyder3
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/spyderlib/spyder.py", line 2331, in main
mainwindow = run_spyder(app, options, args)
File "/usr/lib/python3/dist-packages/spyderlib/spyder.py", line 2215, in run_spyder
main.setup()
File "/usr/lib/python3/dist-packages/spyderlib/spyder.py", line 734, in setup
message=_("Spyder Internal Console\n\n"
File "/usr/lib/python3/dist-packages/spyderlib/plugins/console.py", line 74, in init
self.find_widget.set_editor(self.shell)
File "/usr/lib/python3/dist-packages/spyderlib/widgets/findreplace.py", line 260, in set_editor
from spyderlib.qt.QtWebKit import QWebView
File "/usr/lib/python3/dist-packages/spyderlib/qt/QtWebKit.py", line 10, in
from PyQt4.QtWebKit import *  # analysis:ignore
ImportError: No module named 'PyQt4.QtWebKit'
Please provide any additional information below
Versions and main components

Spyder Version: 2.3.8
Python Version: 3.5.1-4
Operating system: Ubuntu 16.10 x64

Dependencies
Please go to the menu entry Help > Optional Dependencies (or
Help > Dependencies), press the button Copy to clipboard
and paste the contents below:
No chance. Spyder3 doesn't start at all.
Regards,
Ettore

Spyder was deliberately broken by Debian/Ubuntu maintainers when they removed the PyQt4.QtWebKit module from their repositories and didn't even care to patch Spyder for this.
We can't do anything about this, so our recommendation to you is to download and install the Anaconda Python distribution:
http://continuum.io/downloads.html

Thanks for the workaround hint.
I've created a bug report on Launchpad for this problem.
Regards,
Ettore


Request for Feature to Customize Ticket Format in Commit Messages

Hello,
I'm a developer working with a team where we follow a specific commit message convention: type(scope): [jira_id] Commit_title. We are interested in using the better-commits tool to streamline our development process. However, we have encountered an issue that better-commits does not seem to support customizing the ticket format in the check_ticket configuration, particularly adding brackets around the ticket ID.
Our team's convention requires the JIRA ticket ID to be enclosed in square brackets ([jira_id]), which is a crucial part of our workflow. Currently, the better-commits tool allows adding a ticket to the title but does not support this specific format.
I would like to inquire if there is any consideration for introducing a feature that allows customizing the ticket format, particularly for adding brackets around the ticket ID. If there's an interest in supporting this feature, I would be very eager to contribute to the project, ideally starting in early February.
Thank you for your time and consideration, and I look forward to any guidance or suggestions you may have on this matter.

Hey thanks for taking the time to write this up!
We have an issue: #70 that should solve this (and other problems like it).
That ticket might take me a while to get to that since it's a noticeable paradigm shift in how the title would be built (and I'm currently on paternity leave). - Alternatively, and I'm not 100% on this direction. But, I may just add another property to check_ticket to add a wrapper such as () or [] or {}.

Hey thanks for taking the time to write this up!
We have an issue: #70 that should solve this (and other problems like it).
That ticket might take me a while to get to that since it's a noticeable paradigm shift in how the title would be built (and I'm currently on paternity leave). - Alternatively, and I'm not 100% on this direction. But, I may just add another property to check_ticket to add a wrapper such as () or [] or {}.

Thank you so much for responding to my query, and I apologize for missing the earlier issue.
I find the design in your issue incredibly well-thought-out and perfectly suited to meet our needs while offering great flexibility. I really appreciate and like this approach.
I plan to attempt an implementation based on your concept in early February. However, I might not achieve a perfect result since I primarily work with Go and have only recently started learning TypeScript as a hobby. If there are quicker or better implementations, please feel free to merge others' code.
Finally, congratulations on becoming a father, and I wish your family happiness and fulfillment.


Add Database Isolation Unit Tests

This PR adds unit tests that verify the database isolation level of the database implementation. The following unit tests are added:
test_dbtx_insert_elements
test_dbtx_remove_nonexisting
test_dbtx_remove_existing
test_dbtx_read_own_writes
test_dbtx_prevent_dirty_reads
test_dbtx_find_by_prefix
test_dbtx_commit
test_dbtx_prevent_nonrepeatable_reads
test_dbtx_rollback_to_savepoint
test_dbtx_phantom_entry
test_dbtx_write_conflict
The idea is to isolate each anamoly that can happen at isolation levels that are lower than serializable or snapshot isolation. Adding new db implementations should be much easier because running these tests again the implementation should reveal if it's isolation level is sufficient or not.
Currently, rocksdb is the only implementation that satisifies all the tests and prevents all anamolies. MemoryDB satisifies all anamolies except Lost Writes, which should be fine for testing since we don't expect write-write conflicts. SledDB doesn't currently support non-repeatable read, phantom record, and lost write. It should ideally be removed soon.

Codecov Report
Base: 59.21% // Head: 58.90% // Decreases project coverage by -0.31% :warning:

Coverage data is based on head (0519203) compared to base (7c2b706).
Patch coverage: 83.33% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #877      +/-   ##
==========================================
- Coverage   59.21%   58.90%   -0.32%
==========================================
  Files         107      108       +1
  Lines       16900    17285     +385
==========================================
+ Hits        10008    10181     +173
- Misses       6892     7104     +212

Impacted Files
Coverage Δ

crypto/hkdf/src/lib.rs
100.00% <ø> (ø)

fedimint-api/src/db/mod.rs
82.01% <78.19%> (-4.44%)
:arrow_down:

fedimint-api/src/db/mem_impl.rs
91.34% <100.00%> (+0.81%)
:arrow_up:

fedimint-rocksdb/src/lib.rs
86.41% <100.00%> (+2.83%)
:arrow_up:

fedimint-sled/src/lib.rs
79.43% <100.00%> (-13.11%)
:arrow_down:

fedimint-api/src/task.rs
50.87% <0.00%> (-14.98%)
:arrow_down:

fedimint-server/src/lib.rs
79.12% <0.00%> (-8.38%)
:arrow_down:

fedimint-server/src/config.rs
58.54% <0.00%> (-3.27%)
:arrow_down:

modules/fedimint-wallet/src/config.rs
69.49% <0.00%> (-3.08%)
:arrow_down:

... and 13 more

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Great documentation! Did you try rendering it though using cargo doc? Looks a little bit broken :sweat_smile:


Menu Tools > Catalog > Export Laravel 5 Migration not appearing

OS: Ubuntu 16.04.2 LTS x86_64
Python 2.7.12

Is there any other dependency?

sorry, I mistakenly placed the issue here, it was intended for this repo - https://github.com/beckenrode/mysql-workbench-export-laravel-5-migrations


Node version detection is mixed up

I'm using nvm and it's set to switch node versions whenever enter a new dir and a .nvmrc is present. I created a new project with twilio serverless:init. When I now enter the created dir the node version is changed to 8.10.0 (as my bash prompt shows me).
I now run twilio serverless:start and am facing a node version warning because it detects node 10.16.0. 😲 What's interesting about this is, is that my default nvm node version is 12.4.0.
Running node -v inside of the dir correctly returns 8.10.

This behavior persists across terminal sessions. :)
Twilio twilio binary is the one installed via brew.
🐬  ➡ which twilio
/usr/local/bin/twilio

Running twilio-run in the same directory works fine.
/tmp/your-project-name  ⬡ v8.10.0

  ➡ npx twilio-run
┌────────────────────────────────────────────────────────────────────┐
│                                                                    │
│   Twilio functions available:                                      │
│   ├── /hello-world | http://localhost:3000/hello-world             │
│   ├── /private-message | http://localhost:3000/private-message     │
│   └── [protected] /sms/reply | http://localhost:3000/sms/reply     │
│                                                                    │
│   Twilio assets available:                                         │
│   ├── /index.html | http://localhost:3000/index.html               │
│   ├── [private] /message.js | Runtime.getAssets()['/message.js']   │
│   └── /style.css | http://localhost:3000/style.css                 │
│                                                                    │
└────────────────────────────────────────────────────────────────────┘

This has to be something to do with how the CLI installs/references Node itself. If twilio-run inside the directory works then create-twilio-function and twilio-run are both doing their job correctly.

This popped into my head, so I went investigating.
When you install the CLI via homebrew it installs Node 10.16.0 along with it.
We might want some messaging here that if you are running Node on a Mac and you want to write serverless functions and use the CLI then the best way to install it is via npm.

Pushed an update to homebrew twilio-cli earlier today (v1.8.3). Try it out and let me know how it goes.

Thank you! Looks like it is resolved for me. :)


Migrate wasm_bindgen crate's tests to wasm_bindgen_test

The test framework is shaping up quite nicely now, so we should purge the last and final use of wasm-bindgen-test-project-builder! The steps for this will be to:

First, wait for https://github.com/rustwasm/wasm-bindgen/pull/602 to merge
Next, select a test module (for example tests/all/foo.rs) to migrate. Comment here so make sure work isn't duplicated!
Move the file to tests/wasm/foo.rs
Add pub mod foo; to tests/wasm/main.rs
Copy all JS into tests/wasm/foo.js
Migrate #[test] to #[wasm_bindgen_test]
Copy all Rust directly into #[wasm_bindgen_test] functions, or leave them as separate exported functions
Run cargo test --target wasm32-unknown-unknown until tests pass!

All tests currently live in their own namespace so there's a lot of name conflicts (lots of class Foo classes in JS). When copying out JS and Rust exports they may need to be renamed appropriately to avoid conflicting with other names throughout the test suite.
An example of how tests/all/api.rs was moved can be found at https://github.com/rustwasm/wasm-bindgen/pull/602
Tests to migrate:

[x] api.rs
[x] char.rs
[x] classes.rs
[x] closures.rs
[ ] comments.rs
[x] dependencies.rs
[x] duplicates.rs
[x] enums.rs
[x] import_class.rs
[x] imports.rs
[x] jsobjects.rs
[x] math.rs
[x] node.rs
[x] non_debug.rs
[x] non_wasm.rs
[x] simple.rs
[x] slice.rs
[x] structural.rs
[ ] typescript.rs
[x] u64.rs
[x] validate_prt.rs

I'm working on import_class.rs

Done now!


Fn.importValue fails ssoInstanceArn validation

Describe the bug
Cannot use Fn.importValue to set SSO instanceArn of permission set
To Reproduce
#166
Expected behavior
Expect Fn.importValue to pass arn validation

This should now be resolved in 0.1.150
See https://github.com/RenovoSolutions/cdk-library-aws-sso/commit/d01e11da95cf621ddb9a4280f7c4881eddb4e642 for specific fix.


Backend: Bookmark question

Describe the bug

Requires unnecessary bookmark variable in the payload
questionId payload is requested via param which does not go with the rest of endpoints
Error codes are wrong in the response handler

Do you want to work on this issue - [Yes/No]
Yes

YES


Fix compile error in android example app.

Coverage remained the same at 87.619% when pulling aaec5ac4dd744b99cb75d4b7ccdb100d50d8fa8b on fix-android-example into 9e0d25691a0001664fac21bca35f87a52cc9a6f0 on master.


Move require

Makes more sense IMO

We can't do it like this. The require was placed inside of the if because otherwise serverside rendering would fail (at the moment of writing that code Tether did not support server side rendering).

Hmm, okay. Looks like its still failing for people: #179

Yeah we should probably set up automated testing if we want to keep supporting SSR


Edit New issue AutoIT #cs and #ce syntax highlighting

(Original issue 1047 created by None on 2014-10-22T22:53:14.655978+00:00)
#comment-start starts a comment section in a script, it has an alias of #cs. #comment-end ends a previously opened comment section, it has an alias of #ce. However, unlike regular comments prefixed with ';', text within #cs and #ce still has some syntax highlighting present within.

(Original comment by birkenfeld on 2015-03-08T06:49:27.611437+00:00)
Closes #1047: allow newlines in # comments in AutoIt.
→ <<cset 5916dcc5adba>>


[Support] IExpandable Add multiple items on expand but add duplicate children

I have tried to have an item as a parent item and an inside item that would expand on clicking on parent item.
//- ONLY METHODS THAT SEEMED RELEVANT ARE ADDED
// Adapter initialization
adapter =
			new FlexibleAdapter<>(items, this);

		adapter.expandItemsAtStartUp()
			.setAutoScrollOnExpand(true)
			.setAnimateToLimit(Integer.MAX_VALUE)//Size limit = MAX_VALUE will always animate the changes
			.setRemoveOrphanHeaders(false)
			.setAnimationOnScrolling(true)
			.setAnimationOnReverseScrolling(true);

//
public class ParentItem extends AbstractFlexibleItem<ParentItem>
	implements IExpandable<ParentHolder, ChildItem>,
	IHeader<ParentHolder> {
//Constructor
public ParentItem(){
this.mTimeStampBean = timeStampBean;
		this.mExpanded = isExpanded;
		setDraggable(false);

		setEnabled(true);
		setSelectable(true);
}

@Override
	public boolean isExpanded() {
		return mExpanded;
	}

	@Override
	public void setExpanded(boolean expanded) {
		mExpanded = expanded;
	}

	@Override
	public int getExpansionLevel() {
		return 0;
	}

	@Override
	public List getSubItems() {

		return mSubItems;
	}

	public void addSubItem(AddTimeStampItem subItem) {
		if (mSubItems == null)
			mSubItems = new ArrayList<>();
		if (mSubItems.size() == 0) {
			mSubItems.add(subItem);
		}
	}
}

public ChildHolder extends ExpandableViewHolder {
	@Override
	protected boolean isViewExpandableOnClick() {

		if (type == Holder.EXPAND){
			return  true;
		} else {
			return false;
		}

	}
@Override
	protected void expandView(int position) {
		super.expandView(position);
}
@Override
	protected void collapseView(int position) {
		super.collapseView(position);
}
}
public class ChildHolder extends FlexibleViewHolder
	implements IFlexible<ChildHolder> {
	public ChildHolder(View view, FlexibleAdapter adapter) {
		super(view, adapter);

	}
@Override
	public boolean isEnabled() {
		return false;
	}

	@Override
	public void setEnabled(boolean enabled) {

	}

	@Override
	public boolean isHidden() {
		return false;
	}

	@Override
	public void setHidden(boolean hidden) {

	}

	@Override
	public boolean isSelectable() {
		return false;
	}

	@Override
	public void setSelectable(boolean selectable) {

	}

	@Override
	public void setDraggable(boolean draggable) {

	}

	@Override
	public void setSwipeable(boolean swipeable) {

	}

	@Override
	public int getLayoutRes() {
		return 0;
	}

	@Override
	public ChildHolder createViewHolder(FlexibleAdapter adapter, LayoutInflater inflater, ViewGroup parent) {
		return null;
	}

	@Override
	public void bindViewHolder(FlexibleAdapter adapter, AddTimeStampViewHolder holder, int position, List payloads) {

	}
}

public class ChildItem extends AbstractModelItem<ChildHolder>
	implements ISectionable<ChildHolder, IHeader>, IFilterable {

	IHeader header;

	public ChildItem(String id) {
		super(id);
	}

	@Override
	public boolean equals(Object o) {
		return false;
	}

@Override
	public boolean filter(String constraint) {
		return false;
	}

	@Override
	public IHeader getHeader() {
		return header;
	}

	@Override
	public void setHeader(IHeader header) {
		this.header = header;
	}
}

As you could see I implemented all of the interfaces and extended all of the class showed in the example, current status:

What Happens

items that I want it to be expanded do expand but it expand/collapse and add a new duplicate child item, which isn't what I want. It simply doesn't collapse. ( This isn't the first issue I do see with the library, I don't know why it work with the example but not with me, are the examples updated with the last version released for the library ?!!!)

Expected :

Expand/Collapse child view without adding duplicate children.

@Sifrazooy, ok no worries, but I'm sorry you didn't read the Wiki page Headers and section#initialization: You need to distinguish sections with IHeaders + ISectionable, from sections with IExpandable involved.
Since you start with Expandables with the flag expanded=true, it's the Adapter that will do the job to expand the Expandables at startup, you don't have to add subItems in your original list (I'm sure you did it) and you must keep this structure also when filtering and updating the list.
If you add subItems yourself and you also call the method expandItemsAtStartUp(), I think it's obvious that they come duplicated.
Sorry but, I didn't find any solution yet, to know in advance what the user will add into his list that he passes to the Adapter. Everything is explained in the Wiki pages and in the demoApp as well if you read the my comments there!
Keep in mind that, the Adapter is backed by an ArrayList, this list must be the most generic possible to support all the view types we want.

@davideas Thanks for your support and your great library and your very fast reply, but in fact I am not sure  why you should feel sorry for me not reading your wiki page. This issue wasn't created as a bug, obviously  I created it as a support, it was never been intended to offend you. You either have the right to offend people.  Thanks in advance.
Status now:
I have added and included your comments and now this is the current result, items do expand but also with duplicate items.
 timeTrackingAdapter
			.setAutoScrollOnExpand(true)
			.setAnimateToLimit(Integer.MAX_VALUE)//Size limit = MAX_VALUE will always animate the changes
			.setAnimationOnScrolling(true)
			.setAnimationOnReverseScrolling(true);

public class ParentItem extends AbstractModelItem< ParentViewHolder>
	implements IExpandable<ParentViewHolder, ChildItem>,
	IHeader<ParentViewHolder>

public class ParentViewHolder extends ExpandableViewHolder {
@Override
	protected void expandView(int position) {
		super.expandView(position);
		Timber.d(" ParentViewHolder pos: "
			+position+ " isExp "+mAdapter.isExpanded(position));
		if (mAdapter.isExpanded(position)) mAdapter.notifyItemChanged(position, true);
	}

	@Override
	protected void collapseView(int position) {
		super.collapseView(position);

		if (!mAdapter.isExpanded(position)) mAdapter.notifyItemChanged(position, true);
	}
}
public class ChildItem extends AbstractModelItem<ChildViewHolder>
		implements ISectionable<ChildViewHolder, IHeader>{
}

public class ChildViewHolder extends FlexibleViewHolder implements
	ISectionable<ParentViewHolder, ParentItem>, Serializable {
}

Thanks for your help and your great library.

@Sifrazooy, please show me how the adapter list is created, I think the problem lays there, and maybe you can try to activate the logs with the static call FlexibleAdapter.enableLogs(true) before you create the Adapter.
PS. No intention to offend anyone, more generally speaking, I just expect people to double check before opening issues.

ParentItem parentItem =
			new ParentItem("H" + index + 1, mTimestamp, isExpanded, onClick);
		ChildItem subItem = new ChildItem("C" + index);

				parentItem.addSubItem(subItem);

List<AbstractFlexibleItem> items = new ArrayList<>();
items.add(parentItem);

Logs ----
Timeline  I  Timeline: Activity_idle id: android.os.BinderProxy@1
                           0b087c7 time:35740584
                        I  Timeline: Activity_launch_request id:com.example tim
                           e:35743638
          RecyclerView  E  No adapter attached; skipping layout
       FlexibleAdapter  I  Mapped viewType<PHONE_NUMBER> from ParentItem
                        V  onViewBound    Holder=ParentViewHolder pos
                           ition=0 itemId=-1 layoutPosition=0
  ParentItem  D  Holder 0
       AnimatorAdapter  D  Started Animation on position 0
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=1 itemId=-1 layoutPosition=1
  ParentItem  D  Holder 1
       AnimatorAdapter  D  Started Animation on position 1
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=2 itemId=-1 layoutPosition=2
  ParentItem  D  Holder 2
       AnimatorAdapter  D  Started Animation on position 2
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=3 itemId=-1 layoutPosition=3
  ParentItem  D  Holder 3
       AnimatorAdapter  D  Started Animation on position 3
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=4 itemId=-1 layoutPosition=4
  ParentItem  D  Holder 4
       AnimatorAdapter  D  Started Animation on position 4
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=5 itemId=-1 layoutPosition=5
  ParentItem  D  Holder 5
       AnimatorAdapter  D  Started Animation on position 5
              Timeline  I  Timeline: Activity_idle id: android.os.BinderProxy@d
                           cc3b0a time:35745002

       FlexibleAdapter  I  Expanded 1 subItems on position=0
ParentViewHolder  D   ParentViewHolder pos: 0 isExp true
    FlexibleViewHolder  V  onClick on position 0 mode=0
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=7 itemId=-1 layoutPosition=7
  ParentItem  D  Holder 7
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=0 itemId=-1 layoutPosition=0
  ParentItem  D  Holder 0
       FlexibleAdapter  I  Mapped viewType<PHONE_NUMBER> from AddTimeStampItem
                        V  onViewBound    Holder=ChildViewHolder positio
                           n=1 itemId=-1 layoutPosition=1
       AnimatorAdapter  V  Clear notified for binding Animations

       FlexibleAdapter  V  Request to Collapse on position=0 expanded=true hasS
                           ubItemsSelected=false
                        V  Collapsed 1 subItems on position 0
    FlexibleViewHolder  V  onClick on position 0 mode=0
       FlexibleAdapter  V  onViewBound    Holder=ParentViewHolder pos
                           ition=0 itemId=-1 layoutPosition=0
  ParentItem  D  Holder 0
       FlexibleAdapter  V  onViewBound    Holder=ChildViewHolder positio
                           n=1 itemId=-1 layoutPosition=1

       AnimatorAdapter  V  Clear notified for binding Animations

               FlexibleAdapter  I  Expanded 1 subItems on position=0
ParentViewHolder  D   RegParentViewHolder pos: 0 isExp true
    FlexibleViewHolder  V  onClick on position 0 mode=0
       FlexibleAdapter  V  onViewBound    Holder=RegParentViewHolder pos
                           ition=6 itemId=-1 layoutPosition=6
  ParentItem  D  Holder 6
       FlexibleAdapter  V  onViewBound    Holder=RegParentViewHolder pos
                           ition=0 itemId=-1 layoutPosition=0
  ParentItem  D  Holder 0
       FlexibleAdapter  V  onViewBound    Holder=ChildViewHolder positio
                           n=1 itemId=-1 layoutPosition=1
       AnimatorAdapter  V  Clear notified for binding Animations
                   art  I  Background sticky concurrent mark sweep GC freed 847
                           19(3MB) AllocSpace objects, 0(0B) LOS objects, 8% fr
                           ee, 34MB/38MB, paused 10.175ms total 455.631ms
       FlexibleAdapter  V  Request to Collapse on position=0 expanded=true hasS
                           ubItemsSelected=false
                        V  Collapsed 1 subItems on position 0
    FlexibleViewHolder  V  onClick on position 0 mode=0
       FlexibleAdapter  V  onViewBound    Holder=RegParentViewHolder pos
                           ition=5 itemId=-1 layoutPosition=5
  ParentItem  D  Holder 5
       FlexibleAdapter  V  onViewBound    Holder=RegParentViewHolder pos
                           ition=0 itemId=-1 layoutPosition=0
  ParentItem  D  Holder 0
       FlexibleAdapter  V  onViewBound    Holder=ChildViewHolder positio
                           n=2 itemId=-1 layoutPosition=2
       AnimatorAdapter  V  Clear notified for binding Animations
                   art  I  Background partial concurrent mark sweep GC freed 26
                           093(1259KB) AllocSpace objects, 0(0B) LOS objects, 2
                           9% free, 38MB/54MB, paused 15.790ms total 990.881ms

Thanks, I did try every thing but being hopeless got me on the wrong track. Thanks in advance. really appreciate your help. :D

@Sifrazooy, so I think I've found it.
You now start with everything collapsed: only parents are visible. The logs say that you expanded 1 subItem of Parent 0 and another one later, here you see duplication? For me the cause is:

The overridden method equals returns false all the time, why? That has no sense at all, basically for Java, all items are different in the list, this is the cause for me.

So again, beside the documentation (because I'm pretty sure you missed the concept of equals method), you should know how List and Set works in java in general those 2 objects are strictly linked with equals and hashCode methods.
In official Java doc and mine as well, you will also notice that not implementing correctly the equals method will lead to strange behaviors very difficult to find the cause, exactly as this case demonstrates.
I added mandatory to implement because developers are responsible to identify their items uniquely as a good practice.
Then:

ChildViewHolder extends FlexibleViewHolder please remove implements ISectionable<ParentViewHolder, ParentItem>, Serializable those interfaces are not for the ViewHolder.
If you declare ParentItem as IHeader then the ChildItem sectionable should accept the header too: Once you create the child, you should provide the parent to its constructor to save its header(parent) inside (this will resolve future issues with sticky headers).
I don't know how you implemented the extended class AbstractModelItem, please share it as well, there might be others issues as well.

Are you are using beta8, correct?

Thanks for your help, really appreciate it. I don't know how I missed the equals() operator. Anyway it's now working great. Thanks again for your help much appreciated.  💃


Added crypto tracker

Title and Issue number

Title : Crypto Price Tracker
Issue No. : #467
Code Stack :  HTML,CSS, Javascript, React, CoinGecko API
Close #467

Video (mandatory)

https://github.com/apu52/METAVERSE/assets/68018372/0ac7bd2b-ee15-4989-bd1f-092669d19887
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have updated the projectData.json file for my contribution
[X] I have added the img of my project in the assets/img section

Additional context (Mandatory )
Are you contributing under any Open-source programme?

Codepeak, KWOC

@aindree-2005 The Project is not correctly deployed . Please check it.

@apu52 Really sorry about that. Fixed everything now


Standardize DG Requirements Section

After completing the features, standardize the following in the Requirements section of the Appendix

granularity of the extensions (error in command name + error in parsing fields + no/ duplicate entry in database)
language and style of writing the requirements
remove overlapping use cases and reference them directly

[ ] Standardise Acknowledgements in Home page and DG
[ ] Ensure that code links are removed


Add user authorization

I'm going to implement authentication and authorization for the app

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authorization

add user authentication

add user authentication

add authentication

add user authentication

add user authentication


Delete Mongo recipe parameters test

Description
Deleting Mongo recipe parameters test. This test has been disabled for a while and the scenario it covers is now being tested by https://github.com/radius-project/radius/blob/main/test/functional/shared/resources/recipe_bicep_test.go#L44
Type of change

This pull request is a minor refactor, code cleanup, test improvement, or other maintenance task and doesn't change the functionality of Radius (issue link optional).

Fixes: #issue_number
Auto-generated summary

🤖[deprecated] Generated by Copilot at d6560c3
Summary
🚫🐛🚀

Removed a flaky integration test for MongoDB recipe parameters from test/functional/datastoresrp/resources/mongodb_test.go. This was done to avoid failures caused by cosmosdb resource management issues.

Test_MongoDB_RecipeParameters
Flaky test skipped - issue with cosmosdb
Winter of testing

Walkthrough

Remove flaky test function Test_MongoDB_RecipeParameters from resource_test package (link)

/ok-to-test

Glad we're pruning some of the places that cloud resources are used in a test without needing them 👍

/ok-to-test

/ok-to-test

Thanks for doing this 👍


zooming hides the labels on the map past a certain point

updates the popups when zooming

@Bobfrat @DanielJMaher

@dlangston this is ready for you to add to the styling task

@Bobfrat @DanielJMaher dont merge yet one more thing to add

@birdage good to go?

@FBRTMaka yup!


Refactor EditSection to be more maintainable

It's not perfect, but hopefully a small step forward.

@felixfbecker @marekweb any idea how to resolve these errors in the build? Goes beyond my basic TS knowledge.
Error: src/components/EditSection.tsx(67,51): error TS7030: Not all code paths return a value.
Error: src/components/EditSection.tsx(71,93): error TS7053: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ 'company/team/index.md': string; 'product/feature_maturity.md': string; 'product/product_areas.md': string; 'product/feature_compatibility.md': string; }'.
  No index signature with a parameter of type 'string' was found on type '{ 'company/team/index.md': string; 'product/feature_maturity.md': string; 'product/product_areas.md': string; 'product/feature_compatibility.md': string; }'.
error Command failed with exit code 2.
info Visit yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 2.

Thanks for the feedback and suggestions @felixfbecker and @jyavorska. I learned some new stuff today 💡


Issue/118- Fix URI inconsistencies

This PR fixes some inconsistencies in the URIs as explained in #118. The following URIs are renamed:

User Service

/users/batch -> /userbatch

Settings Service

/settings/info/ -> /settings/
/users/<user-id>/settings/preferences/ -> /preferences?filter[user]={uid}

Traefik is already setup to forward to these URIs. The routes used in the Frontend need to be adjusted accordingly.

Merge when frontend changes are also ready to be merged.

Just applied necessary changes regarding new URIs to the frontend. Both can be merged, now.


Forms Crash Occasionally In Angular 2 Apps

I've been getting this error maybe 1 in 20 runs:

Basically when I start my Angular 2 application and try to type something in a form, it crashes.  The error received is as follows:
JS: Page loaded
JS: BOOTSTRAPPING...
JS: Setting DOM
JS: Angular 2 is running in the development mode. Call enableProdMode() to enable the production mode.
JS: ANGULAR BOOTSTRAP DONE.
I/DEBUG   (  146):     #02  pc 0024a377  /data/app-lib/org.nativescript.CouchbaseAngular-1/libNativeScript.so (Java_com_tns_Runtime_callJSMethodNative+231)
I/DEBUG   (  146):          bfc23dc4  947d9f31  /data/app-lib/org.nativescript.CouchbaseAngular-1/libNativeScript.so (tns::Runtime::CallJSMethodNative(_JNIEnv*, _jobject*, int, _jstring*, int, unsigned char, _jobjectArray*)+17)
I/DEBUG   (  146):          bfc23dd8  947d5378  /data/app-lib/org.nativescript.CouchbaseAngular-1/libNativeScript.so (Java_com_tns_Runtime_callJSMethodNative+232)

It is not particularly descriptive.
Any ideas?

It seems like a bug in the {N} runtime. Is it possible to send a repro project or steps to reproduce? If not possible, can you put __enableVerboseLogging() somewhere in your app (for example in the first line in app.js) and send us the full log when the app crashes?

Hey @slavchev,
See the attached project that I was using:
CouchbaseAngular.zip
See if anything seems out of the ordinary to you.
Best,

Hi @nraboy
I investigated the issue further and can confirm it's the same as https://github.com/NativeScript/android-runtime/issues/385. So far we identified the problem in ashmem but don't have a solution. We experienced (quite severely, especially on Genymotion) the same problem in our test environment and only on x86 emulators. As a workaround we switched to arm emulators.
Currently our team doesn't have enough resources and the mentioned workaround works fine for us. If you frequently experience the problem I would suggest to try another x86 emulator or switch to arm. Hopefully, in near future we will have more resources and solve the problem.
I am closing this issue. You can keep the track at https://github.com/NativeScript/android-runtime/issues/385.


Using "org.eclipse.collections" won't generate any code.

I have updated my project to use "org.eclipse.collections" (https://www.eclipse.org/collections/) and when i try to compile with TeaVM it won't generate any code and won't throw any exception nor display any log at all.
All i'm getting in app.js is
main = $rt_mainStarter(main);

//# sourceMappingURL=app.js.map

app.js.map
{"version":3,"file":"app.js","sourceRoot":"src","sources":[],"names":[],"mappings":""}

  public static void main(String[] argv) {
        FastList<Integer> container = new FastList<>();
        container.add(3);
        System.out.println(container.get(0));
    }

Can't reproduce the bug. Can you send me a minimum project that causes the issue?


Repetition in "Setting your commit email address" article

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/setting-your-commit-email-address
What part(s) of the article would you like to see updated?
Consider this data reusables.user-settings.no-verification-disposable-emails note.
The statement "If you'd like to keep your email address private, you can use a GitHub-provided noreply email address" is repeated directly after the Note.

Furthermore, within the Note, the "Setting your commit email address" link has the same title as the article itself, which is confusingly self-referential. Also, the link actually points to a heading that appears just after the Note, rather than the top of the article as one would expect from the link title.
Perhaps this reusable note should be replaced with a sentence that conveys the same information without repetition. Reduction in repetition increases clarity, especially for a novice reader.
Additional information
No response

@julerex Thanks for opening this issue! I'll get this triaged for review ✨

The article consists of two chapters (sans the intro/about):

Setting the author on GitHub(.com)
Setting the author in Git (client, locally)

So the link IMHO links the right chapter, only the title ([AUTOTITLE] to be exact) doesn't mention the correct heading — see #31829 — making the link/reference appear circular :(
Regarding the repetition, the reusable is currently used here: https://github.com/search?q=repo%3Agithub%2Fdocs no-verification-disposable-emails&type=code — I'll check all the pages for similar repetition, but if it's only in this instance, I'd say it's safe to omit the repeating part outside the reusable (only checking which formulation is newer, as they differ slightly).

Emeğinize sağlık

Emeğinize sağlık

@janbrasna @julerex

I'd say it's safe to omit the repeating part outside the reusable

Agreed ✨  I've added our help wanted label to this issue and anyone may submit a PR with this update 💛


Feature/24 implement base repository functionality

need to merge in a new solution when it is created properly


Backing up Docker Desktop Volume via Windows network share runs forever

Backing up a Docker Desktop Volume (Windows Share) results in the backup going on forever and not working as expected.
Backup Directory: \\wsl.localhost\docker-desktop-data\data\docker\volumes
Output:
[00:56:29] backing up...                  ████████████████████████████████████████ 458.17 GiB/62.55 GiB  127.48 MiB/s (ETA -)

Rclone had this same problem, but disabling preallocation of disk space fixed it. This will not fix rustic however, even when using the rclone backend with the environmental variable set.

@douglasparker Can you please give more information? What backend are you using? Can you give the full output of the backup command, maybe using higher --log-level?
What was the rclone issue and why do you thing this disabling of preallocation fixed it? Note that rustic doesn't do any kind of such preallocation...

@douglasparker Can you please give more information? What backend are you using? Can you give the full output of the backup command, maybe using higher --log-level?

I was using the rclone backend with S3 compatible storage.
I couldn't test with opendal because of https://github.com/rustic-rs/rustic/issues/1162
Unfortunately, I did not like some of the tradeoffs with Docker Desktop so I no longer have any of that enabled for my workstation so I cannot get better logging for you.

What was the rclone issue and why do you thing this disabling of preallocation fixed it? Note that rustic doesn't do any kind of such preallocation...

I believe the maintainer of rclone thinks that the WSL driver is implementing preallocations wrong. See his reply here: https://forum.rclone.org/t/rclone-copy-fails-to-wsl2-dos-copy-works/38351/4
I have no idea if these issues are related- I just know I had a similar with rclone. Copy and sync went on forever and similarly had the progress in GB being way higher than the total transfer size. Also, files were corrupted with rclone for the destination. Disabling preallocations in rclone fixed that issue for me.

As this cannot be reproduced I can only give some hints about how to get more information:

Use rustic --log-level=debug or --log-level=trace to get more information from rustic.
Set RCLONE_VERBOSE=2 or RCLONE_VERBOSE=3 to get more output from rclone. Note that rustic also outputs such rclone output.


chore(travis): update node to latest lts

Update travis build settings to use the latest LTS version of node

Can you have a look if this is alright @Turbo87 ? This might be relevant for the update of eslint-plugin-ember as well

@jessica-jordan we should probably keep this at Node 4 for now (see https://github.com/ember-cli/ember-cli/blob/master/blueprints/addon/files/.travis.yml#L4-L6)

I will close this as discussed with @Turbo87


Added missing import

Looks like an import was missing for download_url_to_file from from torch.hub, in the AI Ephiphany reconstruction section.
I've added the import at the top of the file, with other imports, to abide by the formatting already present, though, it might be a better idea to import it just before the new custom ResNet50 since it isn't used anywhere before?

Additionally turned off Matplotlib axis for cleaner output images - this one is more of a subjective change, so it might actually be against what you originally wrote.
Feel free to prune the change if you don't like it :)


different modulo behavior on windows vs linux since python3

I seem to have hit a different issue with modulo on windows versus linux.
if i cast the number to a float, or just put it inline before the modulo, it works as i expected.
num = 3316_000_000_000
print(num % 999)

num = float(3316_000_000_000)
print(int(num % 999))

print(3316_000_000_000 % 999)

from distutils.core import setup
from Cython.Build import cythonize

setup(
    ext_modules=cythonize(['test.pyx'])
)

pyinstaller@3d46c498e294:/app$ python setup.py build_ext --inplace
Compiling test.pyx because it changed.
[1/1] Cythonizing test.pyx
running build_ext
building 'test' extension
C:\mingw64\bin\gcc.exe -mdll -O -Wall -IC:\Python36\include -IC:\Python36\include -c test.c -o build\temp.win-amd64-3.6\Release\test.o
writing build\temp.win-amd64-3.6\Release\test.cp36-win_amd64.def
C:\mingw64\bin\gcc.exe -shared -s build\temp.win-amd64-3.6\Release\test.o build\temp.win-amd64-3.6\Release\test.cp36-win_amd64.def -LC:\Python36\libs -LC:\Python36\PCbuild\amd64 -lpython36 -o Z:\app\test.cp36-win_amd64.pyd
pyinstaller@3d46c498e294:/app$ python
Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import test
935
319
319

As you can see i'm building using mingw64, so this might be a factor, but the fact that it works either casting as float or inlining makes me think it's a cython bug.
gabriel@dev-desk-1:/tmp> python3.6 setup.py build_ext --inplace
running build_ext
building 'test' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -I/home/gabriel/.virtualenvs/kivy36/include/python3.6m -c test.c -o build/temp.linux-x86_64-3.6/test.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.6/test.o -o /tmp/test.cpython-36m-x86_64-linux-gnu.so
18:54:51 30/03/18 red argv[1] 94%kivy36 390
gabriel@dev-desk-1:/tmp> python3.6
Python 3.6.3 (default, Oct  6 2017, 08:44:35)
[GCC 5.4.0 20160609] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import test
319
319
319

Doing these operation in python directly always results in 319, on both platform.
the docker image used to build can be found on docker hub (https://hub.docker.com/r/tshirtman/kpmwine/)
docker run -ti -v $PWD:/app -v /tmp/pipcache:"/wine/drive_c/users/pyinstaller/Local Settings/application data/pip/cache/" tshirtman/kpmwine bash

I obviously cannot reproduce this without Windows, but I added your example to get it tested on appveyor. Are you using the latest Cython 0.28.1 release?
As for potentially relevant platform differences, long is 32 bits on Windows64 and 64 bits on Linux64, and I'm not sure what the size of a PyLong digit is on Windows.
In any case, the code that Cython generates is correctly typed and analysed. I don't see anything obviously wrong with it. The result is calculated in the generated helper function __Pyx_PyInt_RemainderObjC(), specifically by the code that handles PyLong values.

Appveyor seems quite happy with the test:
https://ci.appveyor.com/project/cython/cython/build/master-1898

Yes i was using the latest from pip, 0.28.1, i did integrate your test in my code to be sure there is no subtle difference, and it does generate the bug on my side, so i guess next step for me is to setup a windows build environment with visual studio and see if i can reproduce here.
Thanks for looking into it :).

I'm able to reproduce this with your docker image. In your setup, MinGW finds this config:
sizeof(digit) = 2
sizeof(long) = 4
sizeof(long long) = 8
PyLong_SHIFT = 15
PyLong_BASE = 32768

However, this is clearly not what CPython uses in your docker image:
$ wine python -c 'import sys; print([sys.getsizeof(i) for i in (0, 1, 2**15-1, 2**15, 2**30-1, 2**30, 2**30+1, 2**45-1, 2**45, 2**60-1, 2**60)])'
[24, 28, 28, 28, 28, 32, 32, 32, 32, 32, 36]

The integer object size increases by 4 bytes every 2**30 integers, which suggests a PyLong digit size of 30 bits, not 15.
I have no idea how to fix the setup here. If you need to use it, you may consider disabling direct PyLong usage in Cython by defining -D CYTHON_USE_PYLONG_INTERNALS=0. But that will slow things down a bit.
I'll close this ticket since it's not a bug in Cython.


device name fails to match

I have multiple MM devices, thruout my house... so I want to be able to control them separately..
i have changed the node_helper to add the device name in front of each of the menu_device creations..
so that for example I have
modulename.js
      "stop": this.translate("STOP"), "deviceName":this.translate(this.config.deviceName)
node_helper.js
       if(this.config.monitorToggle){
        	console.log("monitorToggle requested")
            device = {}
            device.name = _this.translations["deviceName"]+" "+_this.translations["monitor"]
//      'office monitor'
            device.port = _this.config.startPort

alexa device list shows (alexa.amazon.com)
office monitor   Wemo Plug	Forget
'office restart'
etc
the device discovery works and each of the devices is shown with the  two part name
i also have an existing device (an temp sensor for my thermostat) which is named 'Office'
when I say ' Alexa turn off office monitor', i get 'office doesn't support that'
so somehow the full name is not being searched.
the fauxmo  example shows multi-word device names 'Fake device 1"
I had also created a custom device called 'Office'
devices: {
	            devices: [{
			        name: 'Office',
			        port: 11100,
			        handler: 'console.log("office device invoked, action="+action)'
			    }
			    ]
}

and it received the action notification from fauxmo, when I said 'alexa turn off office' or alexa 'turn off office monitor'
i have deleted that device (alexa forget device)
am I doing something wrong?

i deleted my 'Office' thermostat device, and now 'alexa turn off office monitor' works..

Hi. I answered you in the other issue. Is the Office thermostat device a "real" device. Maybe it usee the same port. And if you would like to run more then one mirror in your home you have to set different start ports for each of them but not one at 11000 and the other on 11001. Set one to 11000 and another to 13000 and so on.

Is the Office thermostat device a "real" device.

yes, switching to port range 13000 doesn't help..  still get office doesn't support that
works ok for on, not ok for off 'office doesn't support that' for 'alexa turn off office monitor'

@JoChef2  thanks for the info on different port ranges on different systems on same network..
got to make 1st system work.. then on to others...

by changing the original physical device name, and the AlexaControl virtual device names, the collision is gone... see my pull request


Slint templates not showing the GUI on the display

When trying to run the Slint templates on the board, the GUI is not shown on the display.
With the following message on rustSlint:
Protocol error 0 on object zwp_linux_explicit_synchronization_v1@36:
Error: Other("Error running winit event loop: Exit Failure: 1")

And with the following message, with the same error, on cppSlint:
Protocol error 0 on object zwp_linux_explicit_synchronization_v1@36:
thread '<unnamed>' panicked at api/cpp/lib.rs:64:6:
called `Result::unwrap()` on an `Err` value: Other("Error running winit event loop: Exit Failure: 1")
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)

@tronical do you know what may be the issue?

On cppSlint, when adding the environment variable RUST_BACKTRACE=full, this is the message shown:
Protocol error 0 on object zwp_linux_explicit_synchronization_v1@36:
thread '<unnamed>' panicked at api/cpp/lib.rs:64:6:
called `Result::unwrap()` on an `Err` value: Other("Error running winit event loop: Exit Failure: 1")
stack backtrace:
   0:     0xffffa861bdac - std::backtrace_rs::backtrace::libunwind::trace::h4210404a228eb944
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/../../backtrace/src/backtrace/libunwind.rs:105:5
   1:     0xffffa861bdac - std::backtrace_rs::backtrace::trace_unsynchronized::hea2e482630a56378
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0xffffa861bdac - std::sys_common::backtrace::_print_fmt::h326180b7b26e4e21
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/sys_common/backtrace.rs:68:5
   3:     0xffffa861bdac - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::haee13570c31cb77b
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/sys_common/backtrace.rs:44:22
   4:     0xffffa86446f8 - core::fmt::rt::Argument::fmt::hee8176c00818b355
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/core/src/fmt/rt.rs:142:9
   5:     0xffffa86446f8 - core::fmt::write::he0b40f3f74e7e87c
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/core/src/fmt/mod.rs:1153:17
   6:     0xffffa861837c - std::io::Write::write_fmt::hc8024efb884f388c
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/io/mod.rs:1843:15
   7:     0xffffa861bbf8 - std::sys_common::backtrace::_print::he99739ec6cb2be23
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/sys_common/backtrace.rs:47:5
   8:     0xffffa861bbf8 - std::sys_common::backtrace::print::hf1431a2be8ae8207
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/sys_common/backtrace.rs:34:9
   9:     0xffffa861d33c - std::panicking::default_hook::{{closure}}::ha26cf0d89fc27676
  10:     0xffffa861cff0 - std::panicking::default_hook::hddcfc2aac016eb46
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:292:9
  11:     0xffffa861d748 - std::panicking::rust_panic_with_hook::hbd9f5866892982cc
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:779:13
  12:     0xffffa861d5f8 - std::panicking::begin_panic_handler::{{closure}}::hf930a65f0587fc68
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:657:13
  13:     0xffffa861c270 - std::sys_common::backtrace::__rust_end_short_backtrace::h8aeef1aadd5204df
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/sys_common/backtrace.rs:171:18
  14:     0xffffa861d390 - rust_begin_unwind
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/std/src/panicking.rs:645:5
  15:     0xffffa797ced0 - core::panicking::panic_fmt::h3c23aa0af13818a0
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/core/src/panicking.rs:72:14
  16:     0xffffa797d224 - core::result::unwrap_failed::h96aa0d56e71b0bb4
                               at /rustc/9b00956e56009bab2aa15d7bff10916599e3d6d6/library/core/src/result.rs:1654:5
  17:     0xffffa7980914 - slint_run_event_loop
  18:     0xaaaace696928 - _ZN5slint14run_event_loopENS_13EventLoopModeE
                               at /usr/include/slint/slint.h:1353:43
  19:     0xaaaace6a27dc - _ZN9AppWindow3runEv
                               at /home/torizon/app/build/arm64/appwindow.h:3332:26
  20:     0xaaaace693f3c - main
                               at /home/torizon/app/src/main.cpp:15:12
  21:     0xffffa7457780 - <unknown>
  22:     0xffffa7457858 - __libc_start_main
  23:     0xaaaace693cf0 - _start
  24:                0x0 - <unknown>
Aborted (core dumped)

Is this with a new version of Weston?
does reverting https://github.com/toradex/vscode-torizon-templates/commit/97c66e02c71da4142d99d537afab7e829201f9eb help?

I tried here, it does seem to solve the issue. Also, I tried here and changing from 3.3.0-bookworm-1.6.0 to  3.3.0-bookworm-1.5.1 does seem to solve the issue, so I think the problem is just with version 1.6.0

Thanks for checking! Yep, somehow there’s an incompatibility between Weston (which is quite old) and slint 1.6.0.
There are two paths forward:

We revert back to 1.5.1.
We change the 1.6.0 based templates to use linuxkms instead of Weston/wayland.

I can work on (2) but I need a bit of time. If you’re planning to make a release soon, then option (1) is the better short-term remedy.
How does your release schedule look like?

We are planning to do a release next week, so I think that for the short-term the option (1) is needed. But then, on the next release, we can do the fix described in option (2).

I can create it here. I will also add it in the same PR the fix for issue #199

Created here, please review @tronical

I've found a workaround for this in Slint now with https://github.com/slint-ui/slint/commit/72e35ea5f946ef89b76213de9c4f1722c8f1270e - that'll be in our next release, to which we can upgrade then :)

so, we are using the backend-linuxkms-noseat now for Rust Slint and seems to work. @tronical let me know if this is ok for you.

Yes, that’s okay for me. The fix for this issue was already in 1.7 - I forgot about this issue when that was merged. Meanwhile, the switch to the linuxkms backend avoids the problem altogether.


@me problems

In my list, when I am formatting the view with JSON.  The "@me" doesn't seem to be working.
We have something like:
...
{
"elmType": "div",
"attributes": {
"class": "sp-card-displayColumnContainer"
},
"children": [
{
"elmType": "p",
"attributes": {
"class": "ms-fontColor-neutralPrimary sp-card-content sp-card-highlightedContent"
},
"txtContent": "=if ([$BidderNo] == @me, 'You are the Highest bidder', [$BidderNo])"
}
]
}
...
This if statement is always false.
We have tried
"txtContent": "=@me"
and
"txtContent": "@me"
and even
"txtContent": @me
How do we get the @me to work?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f60068c3-4534-a400-350b-fdbcefd684b6
Version Independent ID: 228accdb-a7de-0671-34ad-60a37866c380
Content: Use column formatting to customize SharePoint
Content Source: docs/declarative-customization/column-formatting.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

Same question with @me is not retrieving the current user's email., Let's discuss there.

Dupe #6516


Format

Failing test, seems to be something wrong with parse-asn1?
/home/travis/build/crypto-browserify/browserify-sign/sign.js:23
  var len = priv.modulus.byteLength()
                         ^
TypeError: Cannot call method 'byteLength' of undefined

here we go with a version that passes standard and has DSA in it

everything passes, so merging

Thanks @calvinmetcalf,  not sure how that dsaSign got lost.

merge I'd guess, but that's why we use standard know

and published


Implemented GetUser in UserDAO

Implemented the GetUser function in UserDAO to fetch user data based on a provided userId.  Added the UserId to the User class.

Looks all good to me, only thought I had was to create a DAO object and inherit it for all our DAO since they all share DB connections needed and would make our code look cleaner, but not necessary.
Also in UserDAO, we need a createAccount Function as well, and I guess we still need to create UserManager.
The implementation thus far looks good and getters and setters look proper with except no setter for userName I think we should have setter for userName if the user wants to change their username and member functions that check if username already exists in userDAO and updates current username if it doesnt.


Color highlighting has a background color in prism.css

class of .token.entity has a background in prism.css
This cause reliability issues in theming:

Fixed in px-sass-doc and px-demo-snippet - change should be picked up by code-design and any other affected repos the next time they are rebuilt.


Ghost instance in pending state

When a request is rejected, the instance is kept in "pending" state.
Possible change:

add a new state to instance
delete the instance (but requests will be deleted too)

New state available: aborted


feat: Create function to calculate square of given number

Closes #29
Checklist:

[X] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[X] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[X] I've signed the DCO.
[X] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[X] My builds are green. Try syncing with master if they are not.

Codecov Report

Merging #26 into master will increase coverage by 16.66%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           master      #26       +/-   ##
===========================================
+ Coverage   50.00%   66.66%   +16.66%
===========================================
  Files           1        1
  Lines           2        3        +1
===========================================
+ Hits            1        2        +1
  Misses          1        1

Impacted Files
Coverage Δ

main.go
66.66% <100.00%> (+16.66%)
:arrow_up:

Continue to review full report at Codecov.

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

Hi @oss-contributor, this feature is not relevant to our project. Thank you for putting in all this effort.
Closing this PR.


Error/Bug when trying to publish an API with no resources

Test Case:
[N] An API
(a) in CREATED state
(b) doesn't Include all the mandated information in design, implement and manage stages
(c) by a user with publish permissions
should not be able to promote to PUBLISHED state.
Validations:
(a) The request should return 4XX.
(b) Final life-cycle state of the API is CREATED
Description:
After creating a REST API  and after deleting All the default resources users are still able to publish the API and in the store API is displayed and in the resource section it shows loading.
[1] Error Log- https://drive.google.com/open?id=1l3wNo-Ih9qFAiGD6t56_B1ar8YZZtMaT

UI error message is shown when you try to delete all resources. At least one resource needs to be there. this will prevent publishing without any resource


PhantomJS capabilities are not set through Selenide

Selenide fails to apply DesiredCapabilities on PhantomJS
When I set the capabilities through the Configuration.desiredCapabilities object, the PhantomJS driver does not get the capabilities as desired. Nonetheless, when I explicitly instantiate the PhantomJSDriver with the desired capability then it works.
Tell us about your environment

**Selenide Version:**4.11.4
**Selenium Version:**3.12
**OS Version:**Windows Server 2012 R2

Code To Reproduce Issue
Configuration.browser = "phantomjs";
Configuration.headless = true;
DesiredCapabilities v_caps = new DesiredCapabilities();
v_caps.setCapability("phantomjs.cli.args", new String[]{ "--ignore-ssl-errors=yes", "--port=1010"});
Configuration.browserCapabilities = v_caps;
getWebDriver();

PhantomJSDriver v_driver = new PhantomJSDriver(Configuration.browserCapabilities);

I needed to use a string array; ArrayList<String> v_args = new ArrayList<String>(); to add the desired capability v_caps.setCapability("phantomjs.cli.args", v_args);

This was a much better solution:
DesiredCapabilities dcap = new DesiredCapabilities();
File logfile = new File("ABSOLUTE_PATH_TO_YOUR_LOG_FILE");
String[] phantomArgs = [ "--webdriver-loglevel=DEBUG" ]
PhantomJSDriverService pjsds = new PhantomJSDriverService.Builder()
              .usingPhantomJSExecutable(f)
              .usingAnyFreePort()
              .withProxy(proxy)
              .usingCommandLineArguments(phantomArgs)
              .withLogFile(logfile)
              .build();
PhantomJSDriver pdriver = new PhantomJSDriver(pjsds, dcap);

Source: https://stackoverflow.com/questions/30805635/change-path-for-the-logfile-of-phantomjs-in-java

@asolntsev could you tell me the default capabilities for PhantomJS when using Selenide?

@espaciomore We don't pass any capabilities for default phantomjs drive.

@resolko I'm thinking browser viewport, platform, etc...

@espaciomore From browser stuff we just add browser version if it's not null.
Note: Miss one point we also add 2 arguments to phantomjs.cli.args:

--web-security=no
--ignore-ssl-errors=yes

My issue was the viewport so I changed the browser size:
v_driver.manage().window().setSize(new Dimension(1920, 1080));
v_driver.manage().window().setPosition(new Point(0, 0));

@espaciomore Selenide has configuration for this points:

Configuration.browserSize - for browser size, be default it has your browser default window size
Configuration.browserPosition - for browser  position, be default it has your browser default window position


fix RTP/RTCP Port in N5 Request on term side

Fix storing and retrieving SDP RTP/RTCP Ports from Orig User on term side.
I will be glad if you review it and comment if there is anything to adjust/fix

Thank you for your continuous contributions and efforts :)


HADOOP-17642. Remove appender EventCounter to avoid instantiation

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 51s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 30s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
22m 39s

trunk passed

+1 :green_heart:
compile
22m 25s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
18m 58s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
mvnsite
2m 18s

trunk passed

+1 :green_heart:
javadoc
1m 37s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
2m  8s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
shadedclient
101m 58s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 28s

the patch passed

+1 :green_heart:
compile
21m 37s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
21m 37s

the patch passed

+1 :green_heart:
compile
18m 53s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
18m 53s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
2m 14s

the patch passed

+1 :green_heart:
javadoc
1m 36s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
2m 10s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
shadedclient
23m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
17m 24s

hadoop-common in the patch passed.

+1 :green_heart:
unit
22m 24s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

211m 11s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2922/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2922

Optional Tests
dupname asflicense mvnsite unit codespell compile javac javadoc mvninstall shadedclient

uname
Linux 8fe3f14418a6 4.15.0-128-generic #131-Ubuntu SMP Wed Dec 9 06:57:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 60149c7da8e0ee425cc6736091841157520bb1af

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2922/1/testReport/

Max. process+thread count
2725 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2922/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


freebsd Unsupported platform

Steps to reproduce
Tell us about your environment:

Puppeteer version:
<EMAIL_ADDRESS>or
<EMAIL_ADDRESS>

Platform / OS version:
$ freebsd-version
10.3-RELEASE-p16

URLs (if applicable):

What steps will reproduce the problem?
Please include code that reproduces the issue.

$ npm install puppeteer

What is the expected result?
installed puppeteer
What happens instead?

<EMAIL_ADDRESS>install /usr/home/majkelo/node_modules/puppeteer
node install.js
assert.js:43
throw new errors.AssertionError({
^
AssertionError [ERR_ASSERTION]: Unsupported platform:
at Console.assert (console.js:171:23)
at Object.revisionInfo (/usr/home/majkelo/node_modules/puppeteer/utils/ChromiumDownloader.js:139:13)
at Object. (/usr/home/majkelo/node_modules/puppeteer/install.js:31:33)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
at Function.Module.runMain (module.js:609:10)
at startup (bootstrap_node.js:158:16)
npm WARN enoent ENOENT: no such file or directory, open '/usr/home/majkelo/package.json'
npm WARN majkelo No description
npm WARN majkelo No repository field.
npm WARN majkelo No README data
npm WARN majkelo No license field.
npm ERR! FreeBSD 10.3-STABLE
npm ERR! argv "/usr/local/devil/node8/bin/node" "/usr/local/bin/npm" "install" "puppeteer"
npm ERR! node v8.4.0
npm ERR! npm  v4.0.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node install.js'.

What does the following terminal command return for you on freebsd?
$ node -e 'console.log(os.platform())'

 node -e 'console.log(os.platform())'
return
darwin

@dwk715 that would be returned on mac os x; freebsd should output different value.

I'm running FreeBSD, this is the output:
freebsd```

@aslushnikov I get the same error on FreeBSD 11.1 Release. What's needed to make FreeBSD a supported platform? I'm willing to do the pull request but would like a little direction/help. It should be possible, FreeBSD got headless chromium support about 6 months ago1.

The problem is that the freebsd chromium builds are not official.
I think the available ones are listed here: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html
More info: https://wiki.freebsd.org/Chromium

You can run npm install with PUPPETEER_SKIP_CHROMIUM_DOWNLOAD to avoid the download problem.
When using puppeteer, you can set the executablePath option to point puppeteer to the right direction:
const puppeteer = require('puppeteer')

puppeteer.launch({
  executablePath: '/usr/local/bin/chrome',
})

This should work, but actually doesn't. I guess it's because the latest www/chromium in ports is too old. Puppeteer 0.13 uses v64.0.3264.0 while the latest version on ports is v61.0.3163.100.

v1.20.0
puppeteer/lib/BrowserFetcher.js:
...
`class BrowserFetcher {
/**

@param {string} projectRoot
@param {!BrowserFetcher.Options=} options
*/
constructor(projectRoot, options = {}) {
this._downloadsFolder = options.path || path.join(projectRoot, '.local-chromium');
this._downloadHost = options.host || DEFAULT_DOWNLOAD_HOST;
this._platform = options.platform || '';
if (!this._platform) {
const platform = os.platform();
if (platform === 'darwin')
this._platform = 'mac';
else if (platform === 'linux')
this._platform = 'linux';
else if (platform === 'win32')
this._platform = os.arch() === 'x64' ? 'win64' : 'win32';
assert(this._platform, 'Unsupported platform: ' + os.platform());
}
assert(supportedPlatforms.includes(this._platform), 'Unsupported platform: ' + this._platform);
}
`
freebsd is not supported

Same issue: FreeBSD 11.2-RELEASE-p5 amd64

+1 requesting FreeBSD support. Will try to get it working with the suggested workaround - if that doesn't work, i'll try the firefox based phantomjs replacement

Last I checked, FreeBSD was POSIX-compliant and still is. This means very little work is required to add FreeBSD under "compatible platforms". We've gone as far to support OSX (derived from FreeBSD, imagine that!) so why not respectfully include the parent OS that will most likely power the application on the server side?
The requirements have been met at this point; it's time to stop treating FreeBSD as a third-world OS.
+1

+1 for FreeBSD support

+1 for FreeBSD support

Not sure if you understand this, but the people that write puppeteer are likely NOT the people that build and distribute chromium binaries. That said, unless there's official FreeBSD support from upstream chromium, there's no way puppeteer can support this.
In this topic there are ways to make it work on FreeBSD that are oficially supported from puppeteer. That's as good as it gets for now.

I guess you chould check the availability of chromium on FreeBSD, or just warn that puppeteer won't run until you'll manage chromium to run.

Chromium exists in standard ports collection.
/usr/ports/www/chromium/
[ /usr/ports/www/chromium ] # cat pkg-descr
Chromium is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.
The Chromium website contains design documents, architecture overviews,
testing information, and more to help you learn to build and work with
the Chromium source code.
WWW: https://www.chromium.org/Home
On Fri, Dec 25, 2020 at 12:54 PM Alexander Povolotsky <
<EMAIL_ADDRESS>wrote:

I guess you should check the availability of chromium on FreeBSD, or just
warn that puppeteer won't run until you'll manage chromium to run.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/puppeteer/puppeteer/issues/1049#issuecomment-751223554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5UZZCOJRXBYHYWDPELUL3SWRONNANCNFSM4D7LY7QQ
.

--

Yours sincerely,
Igor

Last time I've tried it I've got issues with headless running with
pyppeteer. Can't recall exact problem, I had no time so I've installed
linux in VM...
On 25.12.2020 13:05, ip75 wrote:

Chromium exists in standard ports collection.
/usr/ports/www/chromium/
[ /usr/ports/www/chromium ] # cat pkg-descr
Chromium is an open-source browser project that aims to build a safer,
faster, and more stable way for all users to experience the web.
The Chromium website contains design documents, architecture overviews,
testing information, and more to help you learn to build and work with
the Chromium source code.
WWW: https://www.chromium.org/Home
On Fri, Dec 25, 2020 at 12:54 PM Alexander Povolotsky <
<EMAIL_ADDRESS>wrote:

I guess you should check the availability of chromium on FreeBSD, or
just
warn that puppeteer won't run until you'll manage chromium to run.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub

https://github.com/puppeteer/puppeteer/issues/1049#issuecomment-751223554,

or unsubscribe

https://github.com/notifications/unsubscribe-auth/AA5UZZCOJRXBYHYWDPELUL3SWRONNANCNFSM4D7LY7QQ

.

--

Yours sincerely,
Igor
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/puppeteer/puppeteer/issues/1049#issuecomment-751225266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD4K57ORK2DJTU5PHNHLETSWRPXRANCNFSM4D7LY7QQ.

Bizarre to add an explicit check when the workaround was working for FreeBSD users.

Bizarre to add an explicit check when the workaround was working for FreeBSD users.

Seems you can explicitly set platform: 'linux' in the instantiation options to get around this silly check.
It's one thing to warn users that something isn't officially supported, it's something else to actively work against them in this way.

Bizarre to add an explicit check when the workaround was working for FreeBSD users.

Seems you can explicitly set platform: 'linux' in the instantiation options to get around this silly check.
It's one thing to warn users that something isn't officially supported, it's something else to actively work against them in this way.

Indeed this does work fine.

Install chromium on FreeBSD the normal way.
Install puppeteer using the env variable, e.g. setenv PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true && npm install
Change your object instantiation to override the platform:

  return await puppeteer.launch({
    platform: 'linux',
    executablePath: '/usr/local/bin/chrome',
    ...

This is a lot of nonsense to go through to use something that "just works" if it wasn't for puppeteer itself actively working against it.

Bizarre to add an explicit check when the workaround was working for FreeBSD users.

Seems you can explicitly set platform: 'linux' in the instantiation options to get around this silly check.
It's one thing to warn users that something isn't officially supported, it's something else to actively work against them in this way.

Indeed this does work fine.
1. Install chromium on FreeBSD the normal way.

2. Install puppeteer using the env variable, e.g. `setenv PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true && npm install`

3. Change your object instantiation to override the platform:

  return await puppeteer.launch({
    platform: 'linux',
    executablePath: '/usr/local/bin/chrome',
    ...

This is a lot of nonsense to go through to use something that "just works" if it wasn't for puppeteer itself actively working against it.

Basically tons of stuff to preconfigure just to have puppeteer work in CI - which makes it useless.
We've switched out from Puppeteer in the meantime. There's no need for it anymore.

+1 for FreeBSD support

Bizarre to add an explicit check when the workaround was working for FreeBSD users.

Seems you can explicitly set platform: 'linux' in the instantiation options to get around this silly check.
It's one thing to warn users that something isn't officially supported, it's something else to actively work against them in this way.

Indeed this does work fine.

Install chromium on FreeBSD the normal way.
Install puppeteer using the env variable, e.g. setenv PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true && npm install
Change your object instantiation to override the platform:

  return await puppeteer.launch({
    platform: 'linux',
    executablePath: '/usr/local/bin/chrome',
    ...

This is a lot of nonsense to go through to use something that "just works" if it wasn't for puppeteer itself actively working against it.

For people coming from google, the above no longer worked for me.. it seems the platform option gets ignored and reset to os.platform in various places.
Couldn't really be arsed trying to work around that so I just modified the if statement in BrowserFetcher to include freebsd. Exactly where you need to edit depends on the version.. if you npm start the stack trace will tell you where to look.
Works fine on BSD after this change.

# Install chromium
pkg install chromium

# Install percollate, but skip trying to download chromium
/usr/bin/env  PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1 npm -g i percollate

# Run percollate and point it to the chromium executable
/usr/bin/env PUPPETEER_EXECUTABLE_PATH=/usr/local/bin/chrome percollate pdf -o test.pdf 'https://github.com'


Create small puzzle piece, guiding arrow asset for landing page

Done, assets located here: https://www.figma.com/file/6dwFZiYdsPN3vgViNPark1/BetaHack-UI?node-id=166%3A72


Add proximus client to aerolab (vector)

I have considered it, but decided against it. The reason is simple - examples are HUGE, especially the prism one.

Good point.

Did you run the prism install script before trying to upload?

Yes, but it looks like something happened.
➜  deploy_clients git:(vector-readme-updates) aerolab client attach -n vector -- /bin/bash /opt/prism-example.sh
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
git is already the newest version (1:2.34.1-1ubuntu1.10).
python3 is already the newest version (3.10.6-1~22.04).
python3-pip is already the newest version (22.0.2+dfsg-1ubuntu0.4).
0 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
fatal: destination path 'proximus-examples' already exists and is not an empty directory.
2024/04/02 09:19:01 -0600 exit status 128

Can you provide me with a snippet of the relevant prometheus yaml file example on how to configure it to the correct URL for monitoring?

Yes. We do it here: https://github.com/citrusleaf/proximus-sandbox/blob/main/new-trial.sh

Is it docker/GCP/AWS you are deploying in?

Testing on docker atm. It appears this is due to the prism script problem I am guessing.

@hev lets continue here
I will look into the new-trial.sh for prometheus configuration.
For the install script, yes, it looks like it failed on the first time you ran it. Now it fails as it already went most of the way in the install process. Can you nuke this (aerolab client destroy -f -n vector), and retry with the new instruction and a new 7.5.0 build I have just published? To upgrade just do aerolab upgrade --edge (may need sudo, depending on your system).

@hev Vector AMS configuration added, full running example provided in the docs as well. I am building and doing final testing now and in about an hour you should have a build to test this with. Please wait for that release, and you can run the full example after upgrading.


config: include "hour minute" timestamp on upload filenames

Filed https://github.com/sonatype-nexus-community/nancy/issues/217 for this CI failure.

Codecov Report

Merging #634 (8405410) into master (2dee5c7) will decrease coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #634      +/-   ##
==========================================
- Coverage   52.42%   52.30%   -0.13%
==========================================
  Files          95       95
  Lines        3296     3296
==========================================
- Hits         1728     1724       -4
- Misses       1210     1211       +1
- Partials      358      361       +3

Impacted Files
Coverage Δ

pkg/config/odfi.go
30.00% <ø> (ø)

pkg/upload/filename_template.go
82.60% <ø> (+4.34%)
:arrow_up:

pkg/upload/sftp.go
64.86% <0.00%> (-2.71%)
:arrow_down:

Continue to review full report at Codecov.

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


Hello :)

Hello :)
Started getting again error
I get the error https://prnt.sc/10u54ru
Brad told me, can be other places that need orginal fix..
Thx for help..
Additional info
Control Panel Nav 3.0.15
Craft Pro 3.6.10
Originally posted by @wmdhosting in https://github.com/verbb/cp-nav/issues/84#issuecomment-809583878

Sorry for the delay. Difficult to tell what this is referring to from the CP-based error. If you're still having this issue, can you look in your storage/logs/web.log or storage/logs/cp-nav.log files for this error?
Was this also an upgrade from Craft, or CP plugin version?

https://github.com/verbb/cp-nav/issues/84#issuecomment-809583878
Here you fixed  previously.
but seems need to do same on some other places..

Fixed in 3.0.17


Add set filter to exchange messages

Current coverage is 83.64%

Merging #67 into master will increase coverage by +0.45% as of 927382c

@@            master     #67   diff @@
======================================
  Files            6       6
  Stmts          845     850     +5
  Branches         0       0
  Methods          0       0
======================================
+ Hit            703     711     +8
  Partial          0       0
+ Missed         142     139     -3

Review entire Coverage Diff as of 927382c

Powered by Codecov. Updated on successful CI builds.


Many fixes for handling tasks in jobs and executors

The grand sum of fixes from #1225, also closes #1254 and #1255.
This is a big PR and I've left the commits separated for clarity. When merged, I can squash them (though it may make sense to leave them distinct because they address many different issues).
The comments for each commit will give the details, but at a high level this address a few things:

Handling queued/retried tasks in BackfillJob

queued tasks never ran
retried tasks were sometimes viewed as errors

Handling queued tasks in SchedulerJob

Scheduler tried to run ALL queued tasks, including those from other jobs, causing collisions and confusion. Now it only schedules queued tasks from its own executor, by examining the executor's events_buffer.

Handling deadlocked tasks in BackfillJob

If the backfill gets into a situation where none of the tasks can run, it exits with a helpful message. Previously it looped forever.

Fixed handling of depends_on_past in BackfillJob

previously, this was handled by automatically overriding start dates to effectively coerce them into ignoring their depends_on_past parameter. This was fragile and didn't always make it into nested executor instructions. Instead, this PR makes it possible to explicitly ignore ONLY depends_on_past dependencies when determining if a task can run. Users can tell a BackfillJob that they want to ignore_first_depends_on_past if they desire. The default is not to do this (but the helpful deadlock error message will tell users if that's the reason their tasks aren't running).
The command line parameter to ignore depends_on_past is -I or --ignore_depends_on_past (for airflow run) or --ignore_first_depends_on_past (for airflow backfill)

Fixed determination of DagRun states

previously, DagRuns were failed as soon as a task failed and marked successful if all tasks succeeded/skipped. That's no good, because tasks can fail and other tasks can respond with triggers or retries, but in the current system the dagrun would terminate immediately and those tasks wouldn't run.
Now:
dagruns FAIL when any of the root tasks FAIL
dagruns SUCCEED when all of the root tasks SUCCEED/SKIP
dagruns FAIL when all active dagruns are deadlocked (no tasks can run).

Fixed issue where triggers were not respected by BackfillJob

once a task failed, the backfill removed all of its downstream tasks from consideration no matter what their triggers were

Coverage decreased (-0.6%) to 66.451% when pulling 3d5ae40eeac8ebe2e422bc52fc0627862cd2c174 on jlowin:subdag_pool_issue_1225 into 3198756bceb9048829cfcd225e50336b6eee8f76 on airbnb:master.

Coverage decreased (-0.7%) to 66.334% when pulling 025cefb5998e4d73a476eb06c968632f342e6d3f on jlowin:subdag_pool_issue_1225 into 3198756bceb9048829cfcd225e50336b6eee8f76 on airbnb:master.

Coverage decreased (-0.7%) to 66.356% when pulling f7be657014628df1b2c479bbd40469176a8ecd66 on jlowin:subdag_pool_issue_1225 into 3198756bceb9048829cfcd225e50336b6eee8f76 on airbnb:master.

@jlowin this is a really great stuff! What I would really like (if you need help let me know), is to have some tests in place especially for the ignore_depends_on_past parameter as we have been bitten by this before, the schedulerjob fix and the deadlock ones. This would increase coverage in this area which is pretty important.

Coverage increased (+1.4%) to 68.483% when pulling c1eb83adbf9d4371dab7dd545c593cc5a853fb8b on jlowin:subdag_pool_issue_1225 into 526e564ecb0859e50b7b8da31a31c0b61aa3ec3c on airbnb:master.

Coverage increased (+0.1%) to 67.184% when pulling c1eb83adbf9d4371dab7dd545c593cc5a853fb8b on jlowin:subdag_pool_issue_1225 into 526e564ecb0859e50b7b8da31a31c0b61aa3ec3c on airbnb:master.

![img] (https://media.giphy.com/media/5MDk34NOY6ili/giphy.gif)


Update kamon-akka, kamon-bundle, ... to 2.1.7

Updates

io.kamon:kamon-akka
io.kamon:kamon-bundle
io.kamon:kamon-prometheus

from 2.1.6 to 2.1.7.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.kamon" } ]

labels: library-update, semver-patch

Codecov Report

Merging #674 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #674   +/-   ##
=======================================
  Coverage   81.40%   81.40%
=======================================
  Files         114      114
  Lines        3883     3883
  Branches       96       96
=======================================
  Hits         3161     3161
  Misses        722      722

Continue to review full report at Codecov.

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


Add highlighting for arguments in function and subroutine declarations

... and proper punctuation scopes for the parentheses.
Note:

There was a - include: comments in the "class-accessing" context, but I believe it had no effect because this context was only included in the "main" context, which also includes comments separately. So I removed it.
I'm not really familiar with the syntax Cee%Dee in MODULE SUBROUTINE MY_SUBROUTINE(A, B, Cee%Dee). The Cee part was scoped storage.type.class before, so I kept this scope here via the "class-accessing" context. Not sure whether the whole Cee%Dee expression should better be variable.parameter here?
I saw that you already had a "continuation-context" context, but as defined it wasn't sufficient to use here, so I defined another "line-continuation". They could probably get merged together later.

I'm not really familiar with the syntax Cee%Dee in MODULE SUBROUTINE MY_SUBROUTINE(A, B, Cee%Dee). The Cee part was scoped storage.type.class before, so I kept this scope here via the "class-accessing" context. Not sure whether the whole Cee%Dee expression should better be variable.parameter here?

This seems to be a mistake. Must have gotten in because it was confused with CALL MY_SUBROUTINE(A, B, Cee%Dee). You can remove it from the tests and only highlight the variables in function/subroutine declaration as variable.parameter.

I'm not really familiar with the syntax Cee%Dee in MODULE SUBROUTINE MY_SUBROUTINE(A, B, Cee%Dee). The Cee part was scoped storage.type.class before, so I kept this scope here via the "class-accessing" context. Not sure whether the whole Cee%Dee expression should better be variable.parameter here?

This seems to be a mistake. Must have gotten in because it was confused with CALL MY_SUBROUTINE(A, B, Cee%Dee). You can remove it from the tests and only highlight the variables in function/subroutine declaration as variable.parameter.

This seems to be a mistake. Must have gotten in because it was confused with CALL MY_SUBROUTINE(A, B, Cee%Dee).

Oh, this resolved some confusion 😄 . It's fixed now.

This seems to be a mistake. Must have gotten in because it was confused with CALL MY_SUBROUTINE(A, B, Cee%Dee).

Oh, this resolved some confusion 😄 . It's fixed now.

I'm not sure whether or how much if any of it can be re-used between functions and subroutines, because only functions need to highlight the result(x) part. Keep in mind that Fortran doesn't have any reserved words, so it's probably advantageous to highlight keywords only where they make sense, and not in all arbitrary places of the code.
Btw there is one lookahead I used for functions, that might look like nonsense, but seems to be required because of a bug in the syntax highlighting engine with set and meta_content_scope (https://www.sublimetext.com/docs/syntax.html#compatibility). This was fixed in syntax version 2, but of course we can't use it because there is no backward compatibility to Sublime Text 3.


Fix  tag duplicated

The bug came from bbcode parser which transforms \n with <br>.
So I just remove the br tag in bbcode parser before applying the mardown parser.
Fix #1480

Coverage increased (+0.02%) to 40.0% when pulling b1670f274ff4f54c099265311e3a227a448f6ba7 on fixbr into 2ec6eaab9d06f400e210c145a7b9d36ad53bd4ba on dev.

Changes Unknown when pulling f70547d74ec1fafe4c68c4469eca98c315b9379d on fixbr into ** on dev**.

Coverage increased (+0.02%) to 40.0% when pulling f70547d74ec1fafe4c68c4469eca98c315b9379d on fixbr into 421935f8be64eb614f479b7fad25f9c2e6d5cb44 on dev.


Support only having one auth method enabled

Currently you can't disable the local db auth if you are using an oauth provider (for example Microsoft Azure).
This adjust the validation to require at least one enabled authentication provider, and ends up being a little noise for a commit

LGTM. Merged your PR. Thanks for your contribution.


feat: looser import statement regex

Was really scratching my head on this one. The strict format on the regex for pulling out the import statements was causing some imports to be missed.
Offending code with whitespace (someone put that there):

[Error] There is an error in your styles:
File to import not found or unreadable: animations. on line (1294, 1)

I've confirmed this is now working with my local. I wasn't able to run the tests, so I just added to the simple case. It should generate the same as the snapshot.

Could you revert changes for simple case and add a new one for this?

My local is not happy. Do I just match the test case folder name with the snapshots name?

The folder name is for the test case. Snapshots are automatically generated and not edited.