bass: init at 1.0

Description of changes
Add Bass plugin for fish shell.
Bass is created to make it possible to use bash utilities in fish shell without any modification. It works by capturing what environment variables are modified by the utility of interest, and replay the changes in fish.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I would suggest using the latest commit or ask the maintainer to tag a new release, as the only release is from 2018, and about half of total commits are added since then.

I would suggest using the latest commit or ask the maintainer to tag a new release, as the only release is from 2018, and about half of total commits are added since then.

Good catch!  I just grabbed the latest commit.  I changed the version in the derivation to 1.x.  Since the package doesn't have a actual version number, is there a convention for this that I should be using?

The convention for such version number is unstable-YYYY-MM-DD where YYYY-MM-DD is the commit date.

The convention for such version number is unstable-YYYY-MM-DD where YYYY-MM-DD is the commit date.

Okay, all fixed up.

Result of nixpkgs-review pr 164360 run on x86_64-linux 1

1 package built:

fishPlugins.bass


Use temporary directory for memory-mapped files

Summary

This stems from #565. Currently, we write temporary files to the NiMARE data directory (~/.nimare), but using an actual temporary directory (defaulting to $TMPDIR) would leverage faster storage that is common on HPCs.
My only question is whether it would be better to adopt a straightforward $TMPDIR check or look into how nilearn handles things, with joblib and caching (see here).
@jdkent are you familiar with how nilearn handles this?

I won't take this on in 0.0.10, which I will probably release later today, but I do want to make sure we do something about it by 0.0.11 (barring the possible need for a rapid hotfix release).

If we go with $TMPDIR, then I think the only place we'd need to change is in use_memmap:
https://github.com/neurostuff/NiMARE/blob/bdcec801d0755d6e9f1d0559909b2ae7955cc18c/nimare/utils.py#L469-L472


Itay feature: Show SCS results include group by and Filter and Vulnerability Tab (AST-63908)

By submitting a PR to this repository, you agree to the terms within the [Checkmarx Code of Conduct]
Description

Support SCS Secret Detection in the VSCode Plugin with grouping and filtering functionality, as well as a Vulnerability Tab.

References

https://checkmarx.atlassian.net/browse/AST-63908

Testing

Load SCS Results and Group by Different Types: Validate that SCS results are loaded and correctly grouped by various supported types.

Load SCS Results and Filter by Different Types: Ensure that SCS results are loaded and properly filtered according to different criteria.

Expand SCS Vulnerability (Vulnerability Tab with Sub-tabs): Confirm that expanding an SCS vulnerability opens the Vulnerability Tab, displaying its detailed sub-tabs.
UI Tests. (in progress)

Checklist

[ ] I have added documentation for new/changed functionality in this PR (if applicable).
[ ] All active GitHub checks for tests, formatting, and security are passing
[ ] The correct base branch is being used

Great job!!!


Link to files help wiki

Provided wiki help for files.  The help is a link to the wiki pages about files.

:+1:


Different acceleration settings for different devices

Description
I'd like to tell Hyprland to force no acceleration on my mouse, but use default acceleration on my trackpad. My mouse name is glorious-model-o and my trackpad name is apple-mtp-multi-touch.
The wiki says it's not supported, so I thought I'd make an issue.

This is possible, but requires some device specific settings.
https://wiki.hyprland.org/Configuring/Variables/#per-device-input-config
Here's my issue on making this easier: #4181

where does it say it's not supported?
force_no_accel? It's an old thing that should honestly be removed altogether.

Just set a flat profile

but yeah #4181 seems to talk about the same thing

where does it say it's not supported?

I'll set a flat profile, thanks!


test: sharding tests refactor

Extend sharding utils unit tests in packages/utils/src/common/sharding.spec.ts
Add static and auto sharding interop tests in packages/tests/tests/sharding/
Add contentTopic flag to nwaku start (used for autosharding)
Fix sendMessageAutosharding typo
Adjust existing autosharding tests to use clusterID != 1 because starting with nwaku 0.26.0, clusterID 1 is reserved for TWN and it uses RLN-RELAY by default while we don't have RLN support yet in this framework (and thus nwaku will not start and fail the tests). However nwaku will allow autosharding for clusterID != 1 only starting with 0.27.0 (see https://github.com/waku-org/nwaku/pull/2505). So I've skipped autosharding tests until js-waku uses 0.27.0

Issues found:

https://github.com/waku-org/js-waku/issues/1900
https://github.com/waku-org/js-waku/issues/1902

So I've skipped autosharding tests until js-waku uses 0.27.0

can we open an issue to track this? (put it in the blocked column on the board)

clusterID 1 is reserved for TWN and it uses RLN-RELAY by default while we don't have RLN support yet in this framework (and thus nwaku will not start and fail the tests)

this is being tracked in https://github.com/waku-org/js-waku/issues/1914

can we open an issue to track this? (put it in the blocked column on the board)

Added Thanks


Error 500 after daylight savings clock change

I'm getting an 'Error 500' when trying to visit the dashboard after a clock change for daylight savings time. Looking up the error gives me this description:

Exception raised when attempting to create an ambiguous wallclock time.
At the end of a DST transition period, a particular wallclock time will occur twice (once before the clocks are set back, once after). Both possibilities may be correct, unless further information is supplied.
See DstTzInfo.normalize() for more info

https://www.kite.com/python/docs/pytz.AmbiguousTimeError
Might look into this myself later, but wanted to report this issue asap.
Error log:
ERROR Internal Server Error: /dashboard/
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/usr/local/lib/python3.9/site-packages/django/core/handlers/base.py", line 204, in _get_response
    response = response.render()
  File "/usr/local/lib/python3.9/site-packages/django/template/response.py", line 105, in render
    self.content = self.rendered_content
  File "/usr/local/lib/python3.9/site-packages/django/template/response.py", line 83, in rendered_content
    return template.render(context, self._request)
  File "/usr/local/lib/python3.9/site-packages/django/template/backends/django.py", line 61, in render
    return self.template.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 170, in render
    return self._render(context)
  File "/usr/local/lib/python3.9/site-packages/django/test/utils.py", line 100, in instrumented_test_render
    return self.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/loader_tags.py", line 150, in render
    return compiled_parent._render(context)
  File "/usr/local/lib/python3.9/site-packages/django/test/utils.py", line 100, in instrumented_test_render
    return self.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/loader_tags.py", line 62, in render
    result = block.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/loader_tags.py", line 62, in render
    result = block.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/defaulttags.py", line 211, in render
    nodelist.append(node.render_annotated(context))
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/loader_tags.py", line 195, in render
    return template.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 172, in render
    return self._render(context)
  File "/usr/local/lib/python3.9/site-packages/django/test/utils.py", line 100, in instrumented_test_render
    return self.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/defaulttags.py", line 516, in render
    return self.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/loader_tags.py", line 195, in render
    return template.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 172, in render
    return self._render(context)
  File "/usr/local/lib/python3.9/site-packages/django/test/utils.py", line 100, in instrumented_test_render
    return self.nodelist.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render
    bit = node.render_annotated(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated
    return self.render(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/defaulttags.py", line 514, in render
    values = {key: val.resolve(context) for key, val in self.extra_context.items()}
  File "/usr/local/lib/python3.9/site-packages/django/template/defaulttags.py", line 514, in <dictcomp>
    values = {key: val.resolve(context) for key, val in self.extra_context.items()}
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 671, in resolve
    obj = self.var.resolve(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 796, in resolve
    value = self._resolve_lookup(context)
  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 858, in _resolve_lookup
    current = current()
  File "/usr/src/shynet/core/models.py", line 106, in get_daily_stats
    return self.get_core_stats(
  File "/usr/src/shynet/core/models.py", line 116, in get_core_stats
    main_data = self.get_relative_stats(start_time, end_time)
  File "/usr/src/shynet/core/models.py", line 203, in get_relative_stats    chart_data, chart_tooltip_format, chart_granularity = self._get_chart_data(
  File "/usr/src/shynet/core/models.py", line 258, in _get_chart_data
    chart_data = {
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 280, in __iter__
    self._fetch_all()
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 1324, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
  File "/usr/local/lib/python3.9/site-packages/django/db/models/query.py", line 109, in __iter__
    for row in compiler.results_iter(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size):
  File "/usr/local/lib/python3.9/site-packages/django/db/models/sql/compiler.py", line 1122, in apply_converters
    value = converter(value, expression, connection)
  File "/usr/local/lib/python3.9/site-packages/django/db/models/functions/datetime.py", line 246, in convert_value
    value = timezone.make_aware(value, self.tzinfo, is_dst=self.is_dst)
  File "/usr/local/lib/python3.9/site-packages/django/utils/timezone.py", line 239, in make_aware
    return timezone.localize(value, is_dst=is_dst)
  File "/usr/local/lib/python3.9/site-packages/pytz/tzinfo.py", line 363, in localize
    raise AmbiguousTimeError(dt)
pytz.exceptions.AmbiguousTimeError: 2021-10-31 02:00:00

Hmm good catch. Thanks for looking into it.

This StackOverflow answer seems relevant: https://stackoverflow.com/a/21465529
I tried fixing the issue but I couldn't find where exactly I would put the suggested fix, since I'm not really the best with Django and stuff. If someone else could look at this that would be awesome.

Since DST change is coming up in most countries (september/october) it might be a good time to look into this again ...

Good point. Per https://stackoverflow.com/questions/21465528/resolving-ambiguoustimeerror-from-djangos-make-aware, it seems like this is fixed in Django 4. So perhaps the easiest solution is to just get Shynet on Django 4! (Which is something I'd like to do anyway.)

I just ran into this exact issue. After looking around in the Stack Overflow comments, a quick fix seems to be to set TIME_ZONE=UTC. Had this at TIME_ZONE=Europe/Berlin before.

same here, fixed with TIME_ZONE=UTC instead of TIME_ZONE=Europe/Paris

Ugh, sorry you all had to fix this. Really I think we should just be using UTC everywhere — perhaps that's the best solution...


Main layout to set unclickable.

I'd like the background (main) layout to not be clickable when the panel is expanded. I have a recyclerview on the panel layout, whenever I click on recyclerview item, the item in the background that is in main layout, that is taking the click event.

I'd like the background (main) layout to not be clickable when the panel is expanded. I have a recyclerview on the panel layout, whenever I click on recyclerview item, the item in the background that is in main layout, that is taking the click event.

Do you have any progress on this?

i have the same question too

same question ?

same question ?


Failed requests should fail gracefully

If I use Sentry with my application it will report an error "Network request failed " if the call to google analytics fails (which of course it will sometimes).
This could be avoided by handling the error that occurs when fetch is called in the send method i.e add a catch to the fetch.
Line 138 in analytics.js could be updated like this:
return fetch(url, options).catch((e) => {console.log(e)});

Realised that this of course should be handled at a higher level by the code calling analytics.hit.


Pre-build wheels for latest version

Hi @holgern
Thanks for the great package.
Is there any chance you could upload the linux wheels to pypi for the lastest version, please? We are trying to get this setup on a barebones docker image, and would rather not install gcc.
Thanks!

Found a work around, thanks!


API to directly write file into weedfs from Http URL

the API to write file allows uploading from local filesystem. However in case where you want to upload a large file it may be inefficient to do write twice - once in local file system and then to weedfs. Is it possible to provide an API that can directly copy file to weedfs from http/https URL with appropriate buffering? Something like below:
curl -X POST -d "fileName=<file-name>&fileUrl=http://www.something.com/someimg.png" http://<IP_ADDRESS>:8080/3,01637037d6

This is more of a feature request for curl?


Added 'required' CSS class, applied to all required input fields.

Introduced new CSS class 'required' (showing a red asterisk after the label of a required field) and applied it to all required fields in all forms in the application.
Fixes HTBox/crisischeckin#26

Also fixes HTBox/crisischeckin#252 (inconsistent layout send message form).


Draft PRs

First off, this tool is awesome. Thank you to all that created it!
Secondly, I'm curious if it supports the ability to create draft PRs? If not, that's a feature I might (eventually) add.
Thanks!

The CLI does not support creating draft PRs, although you can do it if using the library interface from a Go program. It should be straightforward to add a new CLI flag for this if you'd like to try implementing it. Otherwise, I can probably add it sometime in the next few days.

@bluekeyes Thanks!


Resilience and outage time and date

Hi! I have a question about using the ReOpt API. I was wondering if it is possible to add resilience as a goal in the optimization like the Step 1 on the ReOpt web app? I saw in the output json file that there is LoadProfile|resilience_check_flag, but I don't know how to set it in the input.
Another question is that, what is the different between outage_start_hour and outage_start_time_step? If I'm using 15 min interval load data, should the time step be multiplied by 4?
I'd really appreciate your help. Thanks!

Resilience scenarios in the web app are the same as adding an outage to the model.  When an outage is included in the model the critical load must be met during the outage. (The web app also runs the same scenario without the outage for the "Financial" comparison on the results page.)
The outage_start_hour is an old input that has been kept for backwards compatibility. You can use the outage_start_time_step value for 15 minute interval load data.
Our wiki has a link to all of the API inputs:

the wiki: https://github.com/NREL/REopt-API-Analysis/wiki/Job-Inputs
API inputs: https://github.com/NREL/REopt_Lite_API/blob/master/reo/nested_inputs.py
shortcut to outage_start_time_step input: https://github.com/NREL/REopt_API/blob/fbc70f3b0cdeec9ee220266d6b3b0c5d64f257a6/reo/nested_inputs.py#L588

resilience_check_flag is not an input; It is true if the critical load can be met during the outage with the existing generation technologies:
https://github.com/NREL/REopt_API/blob/bb85165ecfad7ff478e80b7746a8a755f658167d/reo/src/load_profile.py#L769
In the next major API version the resilience_check_flag output will be renamed to bau_critical_load_met:
https://github.com/NREL/REopt_API/blob/fb89f2c17fba2aec8d0d5d1eaa901415dfd129b0/job/models.py#L799
(bau = business-as-usual)

Thank you Nick for getting back to me on this. This really clarifies things a lot. A follow-up question on the resilience criterion. I added an outage for 4 hours (16 time steps) , with the chosen technologies of solar, battery storage, and with or without generator. In both specifications, the resilience_check_flag returned to be false. Is there a way that I can force the outage to be met? I run the same assumptions with the Web Tool and the optimized capacities are very different. I think the resilience issue might be playing a role here. I'd really appreciate it if you could help me with this. Thanks!

The resilience_check_flag only applies to the business-as-usual scenario. For every "Scenario" that you POST to the job endpoint two scenarios are run:

The business-as-usual (BAU) scenario, which determines the cost of meeting the (electric and thermal) loads with the grid and any existing technologies; and
The optimal scenario, which determines the cost-optimal size and dispatch of considered technologies.

In your case, the false resilience_check_flag indicates that the critical load is not entirely met in the BAU scenario (if you have no existing technologies then zero percent of the critical load is met in the BAU scenario).  If you want to include an existing Generator for example then you must provide the generator capacity in the existing_kw input field.
One reason for the differences in your webtool and API scenarios could be that the webtool only runs hourly models (even if 15 minute data is provided). We do this in the webtool because 15 minute scenarios typically take longer to solve than hourly scenarios.

Thank you Nick, this makes perfect sense now. I will go with the API solved optimal capacities then. Thank you!

@Janeyyt you're welcome! And FYI we have a Discussions tab for general usage questions of the API and Webtool.  (I will copy this discussion into the Resilience section there).


Error message and other content updates.

Updated content in all error messages to increase clarity on using accept-language.
Also editted Readme to improve clarity of how to use accept-language

Thanks updated in 3.0.20


Makefile: Compile mlkem/* in a single step

@potsrevennil This should not be merged (yet), but I'm curious about your thoughts on this crude hack. How would you have gone about this? How would you extend it to cover also FIPS202?


Switch release CI to build on Linux

Also disabled Mac builds and .deb generation.

Mac build - they are unsigned and will not be able to run when downloaded
.deb - it doesn't add much value in addition to the binaries

config.yml.txt
export-0x57f1887a8bf19b14fc0df6fd9b2acc9af147ea85_withnotes.xlsx
Freeware License.txt


Re-enable bootkube-terraform cluster tests

Simplify script to not launch subshells
Verify tests don't leave behind processes running terraform apply

Closes #508

Hm, still introduces flakes.

This has now succeeded on 8 suite runs in a row (i.e. booting 32 different clusters). Hopefully its reliable enough to be included in regular testing again.


WGSL: Add support for all intrinsics

TODO: This task was estimated to take 2 weeks, and so should be split into several sub-tasks.
For this purpose it would be useful to have e.g. a list of all the Slang intrinsics, or some other thing to split based on.

atomics
texture functions
TODO: @csyonghe Is there an exhaustive list of Slang intrinsics?

You can search for "metal" in hlsl.meta.slang and core.meta.slang and make sure there is a "wgsl" case.

Thanks Yong, I'll make a list and split it tomorrow.
FYI @bmillsNV, this is the task we could put an extra resource on to help hit WGSL milestone 1 on time.

@csyonghe I see about 20k lines that contain "metal" in hlsl.meta.slang.
The vast majority apply to 0.5 functions, so let's say 10k lines that need to be visited and considered for wgsl.
I'm not about to paste 10k entries here just so we can have something to point at when splitting this task.
@jkwak-work  If you feel like you want to split this one, I guess you can split it into chunks

1/10 for the first 1k instances
2/10 for the next 1k instances
...

We added all metal intrinsics over the course of 2 weeks.

The spec document lists all built-in functions for WGSL.
We should apply them in hlsl.meta.slang from this list.

easy ones
numeric (63 functions)
data packing (9 functions), unpacking (7 functions)

little tricky ones
constructor (19 functions)
texture (15 functions)
derivative (9 functions), bitcast, all, any, select, arrayLength

potentially trickly ones
atomic (3 functions)
synchronization (4 functions)

@jkwak-work Shouldn't we mainly be looking at the list of intrinsics that Slang needs to support? I think we just need to visit all of the places in hlsl.meta.slang and plug in the corresponding WGSL intrinsics (if any) where we can. In places we can't I suppose it gets a little trickier.

I assume that there will be many functions that WGSL don't have.
For those functions, we will need to rely on the generic version of the implementation.
As an example, hlsl has a function called "sincos" and WGSL don't have anything directly same one.
We will need to use the "default" implementation as you can see below.
void sincos(matrix<T,N,M> x, out matrix<T,N,M,L1> s, out matrix<T,N,M,L2> c)
{
    __target_switch
    {
    case hlsl: __intrinsic_asm "sincos";
    default:
        s = sin(x);
        c = cos(x);
    }
}

I think it will be easier if we go down a list by what WGSL has rather than what Slang needs.
Once that step is done, we can run down all Slang functions and make sure that the default version works for WGSL.

I have a PR that covers "numeric" part of WGSL functions.
https://github.com/shader-slang/slang/pull/5078


Some errors

Hi qiwihui,
Seems like you doing some work at enhancing the original script.
I'm getting a couple of issues though.
Don't have any previous experience, with the telegram bot, so not sure, how to set it up properly, though I try everything possible..
In every case, I get the following error, running it with Python 3.8.5
`root@racknerd-64b3f5:~/plutus# python3 plutus.py
reading database: xxx  DONE
Traceback (most recent call last):
File "plutus.py", line 161, in
send_telegram_message("Start searching bitcoin @ " + str(datetime.datetime.now()) + ', database size: ' + str(sum(len(i) for i in database)))
File "/root/plutus/message.py", line 10, in send_telegram_message
bot = Bot(token=token)
File "/usr/local/lib/python3.8/dist-packages/telegram/bot.py", line 147, in init
self.token = self._validate_token(token)
File "/usr/local/lib/python3.8/dist-packages/telegram/bot.py", line 229, in _validate_token
if any(x.isspace() for x in token):
TypeError: 'NoneType' object is not iterable
If I comment the telegram posting related lines and run the script, It goes through "reading database: ...  DONE`" part and the just sits there, doing nothing.

If you want to use telegram bot to send message, you need to set environment variable TELEGRAM_CHAT_ID for telegram channel ID, and TELEGRAM_SENDER_TOKEN for bot token.
In your situation, this is searching the database. I commented the print line to reduce no sense information. You can turn it on by uncomment the line # print(str(address)).
	if address in database[0] or \
	   address in database[1] or \
	   address in database[2] or \
	   address in database[3]:
		with open('plutus.txt', 'a') as file:
			msg = ('hex private key: ' + str(private_key) + '\n' +
				   'WIF private key: ' + str(private_key_to_WIF(private_key)) + '\n' +
			      	   'public key: ' + str(public_key) + '\n' +
			           'address: ' + str(address) + '\n\n')
			send_telegram_message(msg)
			file.write(msg)
	else:
		pass
		# print(str(address))

Thanks,
TELEGRAM_SENDER_TOKEN inserted as the Fatherbot supplied.
For the TELEGRAM_CHAT_ID, I tried my own Telegram ID, a private group ID and a private channel ID, (of course, adding the telegram bot to them), yet, the error is there ... Also tried installing python 3.7.4, the error is the same.

Please try to print token when call send_telegram_message in message.py to debug this error. It seems it cannot get token.


event: Remove obsolete runtime guard for 'envoy.reloadable_features.activate_timers_next_event_loop'

Commit Message:
event: Remove obsolete runtime guard for 'envoy.reloadable_features.activate_timers_next_event_loop'
Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: added
Platform Specific Features: n/a
Fixes #16003

This flake should be fixed on main.


Upgrade maven version to 3.9.5 version on gitlab actions ci

This pull request is aiming to upgrade the maven version to the latest version on Github Actions ci for Kogito Runtimes   building workflow

No longer necessary: already updated to 3.9.6.
Thank you anyway @bmscomp


Please publish a new version on npm

The last npm publish was 7 months ago, AFAICT, the code has changed a lot since then.
Can you publish a new release please ?

yes! done now - sorry for the delay :) let me know if you need anything else!


Changes to logic for determining download channel

For #2755
@brettcannon 	@d3r3kk
The new logic is outlined in the issue.
Please review, @d3r3kk you two have reviewed this in the past.
@brettcannon you have been (need to be) across the requirements.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR)
[x] Title summarizes what is changing
[x] Has a news entry file (remember to thank yourself!)
[x] Unit tests & system/integration tests are added/updated
[n/a] Any new/changed dependencies in package.json are pinned (e.g. "1.2.3", not "^1.2.3" for the specified version)
[n/a] package-lock.json has been regenerated by running npm install (if dependencies have changed)

@d3r3kk Please re-review.


GH-22

Add a null check when trying to remove properties from the Swagger Schema List of required properties. (As the required properties will be null, rather than an empty list, if there are no required properties.)

I've just realised that this should probably go into the release branch, with a patch version bump. I'll fix it up later.

Hi,  thanks a lot for the fix. Imo a merge to develop is fine, i can then cherrypick it to a release version.

True, I was gonna do that myself, but happy for you to do it. :)

Can you merge this one if you're happy with it? I've got another change to add support for Javax/Jakarta validation annotations, but if I push it to my develop branch, it'll get included with this PR.


enhance(walkthrough-garden): accept different meadow version

Sometimes, a garden dataset might rely on a meadow dataset with a different version, e.g.
data://garden/namespace/2022-11-25/short_name:
    - data://meadow/namespace/2022-11-30/short_name

Therefore, I have added an extra field if we want to specify the Meadow version separately.

@pabloarosado I think this is common. At least in my case.

given that it introduces an additional field to be filled every time in the garden step

A default value is set in the walkthrough form, the same as the default one for the Garden dataset. So in cases where they are the same, you don't need to set it.

which in the most common case is unnecessary (because meadow and garden versions are the same)
I find this often, and it would be nice if I didn't have to manually edit the DAG and files after running walkthrough. Also, it prompts me with the message "Meadow dataset not found..." which is inaccurate cause there is a Meadow dataset, just not with that version.

A typical scenario for me:
When I port several datasets to Grapher, I go channel by channel. First, I add all datasets to Snapshot, Meadow, Garden, etc. We can go into the details of why this makes sense in another discussion if you want. The point is, once I start working on Garden, there might have passed some days since I worked on Meadow, so I will set a different version (I use the current date as the version).
Also, it follows the logic of the walkthrough meadow step, where Meadow and Snapshot versions have different fields.


Removal of duplicate classes impacts AlpineJS x-mask directive

What version of prettier-plugin-tailwindcss are you using?
v0.6.1
What version of Tailwind CSS are you using?
v3.4.3
What version of Node.js are you using?
v21.7.3
What package manager are you using?
npm
What operating system are you using?
macOS
Describe your issue
Using Alpine.js and its x-mask directive with a repetitive pattern:
<input
    type="text"
    x-mask="99 99 99 99 99"
/>

Will result into:
<input
    type="text"
    x-mask="99"
/>

I guess removal of duplicate classes should only impact class or className attributes
Workaround
Set the new tailwindPreserveDuplicates option to disable removal of duplicate classes to true (https://github.com/tailwindlabs/prettier-plugin-tailwindcss/pull/276)
{
  "tailwindPreserveDuplicates": true
}

I've confirmed that this doesn't happen in a barebones project with alpine, prettier, and our plugin.
Most likely you have something like this in your Prettier config:
"tailwindAttributes": [
  "x-mask"
]

You'll want to remove that and it'll start working. 👍

@thecrypticace thanks, I should have check the entire config...
{
    "plugins": [
        "prettier-plugin-blade",
        "prettier-plugin-tailwindcss"
    ]
}

There is a conflict with this other plugin prettier-plugin-blade
https://github.com/stillat/blade-parser-typescript

Ah yeah that sounds like a bug in prettier-plugin-blade then


feat(@angular/cli): support Yarn workspaces for vendor chunk

Resolves https://github.com/angular/angular-cli/issues/9611.
When the Angular CLI project is inside of a Yarn workspace, the vendor chunk can't be generated as the node_module directory is at the workspace root, not the workspace where .angular-cli.json resides. This PR resolves that by determining if there's a Yarn workspace root. If there is, use that directory's node_modules, otherwise, fall back to the original behavior of using the node_modules within the .angular-cli.json project's directory.
I haven't written a test for this, yet. Not sure how to approach it with the fact that it requires a specific file structure to run the test with. Any guidance on this would be greatly appreciated!

Maybe we can make this generic to support lerna as well?

Thank you for the contribution.  However, both use cases will be fully supported in CLI v6 with no additional changes required.  v6.0 is currently in the beta phase.  There are no current plans to add this as a feature to 1.7 at this time.

@clydin If this PR is working in 1.7, and 1.7 is broken for anyone wanting to use workspaces at the moment, is it too difficult to release a patch to 1.7 to unblock people?
Upgrading to v6 is going to be a potentially big change for existing project, and forcing a major framework version upgrade just to get a bugfix in the cli tool seems heavy-handed.


Resolved some more compiler warnings.

I added a final change to this PR, please review.

Please review.


Feature Request: Multiple Note Databases

Hi,
I'd like to request a future feature - the ability to switch between notes folders quickly.
I would like to be able to set up multiple notes "databases" (folders).  Each should have it's own preference sets for Simplenote account, storage, file extensions, and encryption.  I would like to be able to switch the NValt view between folders quickly, with a keystroke and/or a drop-down menu next to the search bar.
This would facilitate note sharing.  For instance, one database might be shared with dropbox across multiple users, another might be my encrypted private notes folder, and another might be synced with a github wiki.
Many thanks for a great program!

I'd love something like this too. What you describe might be too complicated from the perspective of code development and user interface design.
What's more likely is that you could keep subfolders within the main notes folder (rather than distributed all over your file system. If you'd want some folders elsewhere then you could make an alias). Simplenote will be a real challenge; and separate Simplenote accounts for each folder is very unlikely. I don't use Simplenote so I don't know this, but back (a couple years ago) when I did it didn't have subfolders. If Simplenote doesn't support separate folders, then its likely this feature (if and when its created) will only sync notes in your main folder, notes in subfolders won't sync. Even if Simplenote does support subfolders, I can't promise much. I don't know the Simplenote code in Notational Velocity or nvALT at all, I don't know Simplenote, or its API at all. And we already have some Simplenote bugs that are a challenge to work with. (Personally, I wish Simplenote only used Dropbox and drop its own cloud service and then nvALT could drop support for it).
I think it is possible, even necessary, for users to set up different note database preferences (basically, the preferences you set in Preferences>> Notes tab) for each subfolder.
The user interface I have in mind (and I'm not committing to, or making any promises here), would be based out of the current location bar. That if you had an empty location bar and typed "/", a drop-down meny of subfolders would show up and help you complete a search for subfolders. Once you had "/folder name/" typed into the location field and hit space that folder name would become a pseudo-permanent token (as in when Mail.app completes an email address in the to: field and you get a blue bubble containing the address). As long as that token was there you'd be "in" that folder, and only see notes from that folder. Delete the token and return to the main folder. Rinse. Repeat.
Again. No promises. No commitments. I'm going to close this issue because I'm not ready for any feedback on this. But I do want sub folders in nvALT. And will try. Eventually.


[ERROR] No loader is configured for ".less"

Command
build
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
@angular-devkit/build-angular:browser
Description
The team tried the new builder @angular-devkit/build-angular:browser-esbuild but face one particular issue with .less files. When we build using the previous version that error don't occur.
Minimal Reproduction
What we did was:

Replace @angular-devkit/build-angular:browser by @angular-devkit/build-angular:browser-esbuild
Ran the following ng build project-name --configuration production

While running, this error appeared:

But, replacing back the builder to the older one, everything is working fine.

Another thing that we notice was that the esbuild doesn't log the result of the build on the console.

Duplicate of https://github.com/angular/angular-cli/issues/24329


HiveTypeParser does not support Hive syntax "Decimal(precision, scale)"

The PR https://github.com/facebookincubator/velox/pull/2653/files added support for Decimal Types in HiveTypeParser.
Hive supports the DECIMAL(precision, scale) syntax. However, the support added was for the Velox Decimal types with syntax SHORT_DECIMAL(precision, scale) and LONG_DECIMAL(precision, scale).
We must add support for the Hive syntax.

CC: @aditi-pandit @Yuhta @karteekmurthys

@majetideepak I am taking a look at this. Just to confirm, we still need support for SHORT_DECIMAL and LONG_DECIMAL.
Need to add support generic DECIMAL as well.

Why do we need to support SHORT_ and LONG_? I think only DECIMAL(p,s) support is needed.

@karteekmurthys thanks for picking this up. We only need to support DECIMAL(p,s) syntax since Hive only supports that.


Develop Log View UI

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
External services such as compilation, static constraint checking, and mission data store publish will return data that needs to be displayed.
Describe the feature request
Develop a generic method to display logs that are returned from executing external services such as compilation.

Questions:

how to view multiple logs from something like compilation that has many steps? View text files, and download others?
Some services may be streaming - can this support simulation status reporting, for example?


Add min_delta argument to ModelCheckpoint callback.

🚀 Feature
Unlike the ModelCheckpoint callback EarlyStopping has the min_delta argument, which controls the criteria for training stopping, I.e how much the monitored value must be improved to continue further training. Such behavior provides you with minimal regularization to your model and saves some time because you wouldn't continue training if your model improves a little bit, e.g +0.0001, which sign of overfitting to the validation dataset.
However, when using ModelCheckpoint with or without EarlyStopping I can't control this behavior and maybe my best checkpoint will be rewritten with the overfitted model.
This problem will be really strange in research.
Motivation
The motivation of this proposal is to reduce the chance of overfitting the validation dataset. I didn't meet similar issues like this one before.
Pitch
I suppose to add a new argument to the ModelCheckpoint/for controlling the saving checkpoint relatively on how much the monitored value was improved.
Alternatives
Unfortunately, I don't see any alternatives.
Outline
Also, I would to join one team to write the code of ModelCheckpoint for the min_delta argument, of course, if the issue will be agreed upon.

sounds reasonable!
would you like to add this feature?

Thank you for your feedback. I will probably write code in 1-2 days.


(Question) The project is abandoned?

4 years with no single update :(

Yes, it is abandoned. I switched to commandline git a while back :)


WIP: feat(auth): re-organize authentication function and support ICP4D authentication

Fixes arf/planning-sdk-squad#???
Why:
We need to provide a tactical solution for supporting the ICP4D authentication mechanism
What:
This commit includes a re-packaging of the authentication function within the java core
to allow it to be extended with additional authentication implementations.
Left to do:

Implement the ICP4D token manager (modeled after IamTokenManager)
Add new tests for ICP4D

@mkistler @dpopp07 @lpatino10 This is an in-progress PR that contains my changes (so far) for re-organizanizing the authentication function within the Java core to support ICP4D.   I wanted to get this first bit of work pushed out so you guys could take a look and let me know if you have any feedack so far.
I still have the following left to do:

Refactor the IamTokenManager class to put most of it in a base class so it can be shared with the ICP4D token manager implementation (ICP4DAuthenticator class).
Add tests for all the new function
Add tests (or modify existing tests) to verify that outgoing requests do in fact have a valid Authorization header attached to them.  I don't think our existing tests do that just yet.

cc: @germanattanasio

Note: there will be some minor tweaks required in the SDK generator to support this new style... specifically the service ctor that is generated to take in the IamOptions argument will need to be changed to take in an AuthenticatorConfig instead.  This should be a compatible change wrt the generated code (famous last words).   My goal with the java core changes is to not require changes to existing apps that are already using IAM or Basic Auth.

We're trying to add this feature this week for Java while Phil's out, so I'll go ahead and take over finishing this PR.

My thought now to build on this is to make setAuthenticator() public and add a new service constructor with the following format in the generator (using Assistant as an example):
public Assistant(String versionDate, AuthenticatorConfig authConfig) {
  // constructor logic
}

We could get away with just that constructor now since the other configuration options like username/password and IAM all implement AuthenticatorConfig. We could then just deprecate the old constructors that deal with authentication until the next major release.

My thought now to build on this is to make setAuthenticator() public and add a new service constructor with the following format in the generator (using Assistant as an example):
public Assistant(String versionDate, AuthenticatorConfig authConfig) {
  // constructor logic
}

We could get away with just that constructor now since the other configuration options like username/password and IAM all implement AuthenticatorConfig. We could then just deprecate the old constructors that deal with authentication until the next major release.

The plan is to change the constructor that we already generate (that takes an IamOptions instance as input) and modify it to so the input param is an AuthenticatorConfig instance, which would mean existing apps can continue to pass in an IamOptions object.

Sounds good @padamstx I'll leave it for you to finish then 👍  It all looks good to me so far.
Just regarding setAuthenticator() being called from the generated constructors, do you think we also want some equivalent way to set the auth other than the constructor? Since we currently allow that with U/P and IAM.

Sounds good @padamstx I'll leave it for you to finish then +1 It all looks good to me so far.
Just regarding setAuthenticator() being called from the generated constructors, do you think we also want some equivalent way to set the auth other than the constructor? Since we currently allow that with U/P and IAM.

Perhaps... let's see where we end up when things are mostly finished and we can decide whether additional methods need to be exposed to apps.   We could expose something like BaseService.setAuthenticatorConfig(AuthenticatorConfig) that would allow the app to replace whatever might be in place for authentication within the BaseService instance with a new config, etc.

Can we call it Authentication rather than AuthenticationConfig?

I'm a fan of AuthenticationStrategy actually 👀

I'm a fan of AuthenticationStrategy actually eyes

If y'all like AuthenticationStrategy that much better than AuthenticatorConfig, go for it :)
I guess it does sound a little fancier I guess (although the "Config" part is descriptive of precisely what is stored in the object).
lol

Just finished all the tests, so I think this is ready for a serious look. I didn't end up renaming those config classes but we can if there's a strong opinion around it.

@padamstx just did the live test and all the ICP4D auth logic works as expected 🙌


Feat: Clear filters button

What feature?
We can provide a button to clear all the applied filters
Add screenshots
No screenshots
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

hey, @kailashchoudhary11 we will add a new filter button soon & will add the clear button there.
also, assigned someone https://github.com/priyankarpal/ProjectsHut/issues/1047


Update README.md

Small grammatical fixes
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to documentation are included in the PR

LGTM


Orientation Native Module is not available

react-native -v: 0.45.1
node -v: 6.10.0
npm -v: 5.3.0

Target Platform: Android/Ios
Development Operating System: Windows 10
Build tools: 23

https://user-images.githubusercontent.com/10004370/29878252-61b59af0-8d78-11e7-92ba-da584d8e8000.png
You can see there that Orientation is not present. This breaks: https://github.com/yamill/react-native-orientation/issues/218

Doesn't look like an RN bug. please continue to use issue tracker on rn-orientation. Let me know if this needs to be reopened.


Add custom GraphQL context option

This PR is the same as stated in #74 and addresses the review comments.

Would you mind adding a co-authored-by in the commit so that we keep attribution of @brettlaforge work in https://github.com/mcollina/fastify-gql/pull/74?


as_u128 added to U256

as_u128 method added to u256.sw in order to enable downcasting from U256 to U128.

Tests added @mohammadfawaz. Let me know if this covers it properly:
assert(unwrapped == ~U128::from(11, 11));

I guess you could also do
assert(unwrapped.upper == 11);
assert(unwrapped.lower == 11);

Of course this would fail if those field names were changed.
Thanks again!

Your added tests seem to be failing. Try to run the test against a local fuel-core node and see what's going on.

@alphak3y turning this into a draft until CI passes 😄

@alphak3y this was getting pretty stale so I made a few fixes. I hope you don't mind! Should be ready. I'll approve once CI passes.

Anything is okay for me 🤝
We got around the casting by just doing it directly.
I can add more casting ability for users once we are done with the bulk of the AMM libraries.


Refactor default theme for better maintainability, bring CSS variables and stylelint

Hello! Finally got a project where I had to use this and could not go with the current structure because of maintainability. Related to #60 decided to go and do the work. This PR will maintain the current default theme completely refactored carefully. I have tested this with the demo and it seems to work fine.
This PR will:

Get rid of unnecessary and overly complicated nesting
Tries to prevent too much specificity, although some parts are forced to be ignored in sake of functionality, may be further simplified though if time
Get rid of unnecessary overrides
Replace unspecified and unclear darken() colors with real variables
Prefer specificity in favor of !important rule to maintain continuity
Remove unnecessary & and > that are not needed at all
Fix duplicate selector issues if any
Disable overcomplicated calculations in font sizes, prefer CSS variables instead

After this making a new custom theme will be easy. You just need to replace the colors in variables with your own and style other things according to preferences.

I'll check this as soon as I have a chance for it :)

Any plans of merging this in master? It would be pretty useful to have CSS vars for easier customization of the drawer.


Handling tweets which have multiple labels

The dataset has 81163 tweets. There are total 9 labels : Anger, Fear, Love, Joy, Sadness, Surprise, Thankfulness, Disgust and Guilt. There are few tweets where the tweet is categorized into multiple labels. So in such a case what will be the true label for the tweet?
Below is the screenshot.

In the above screenshot there are few tweets having multiple labels. So I wanted to know which label should I consider a true label.

Hi, thanks for being interested in this dataset. Yes, there are a few data samples that are multi-labeled. If you are only working on single label emotion classification, feel free to ignore them.

CBET is mainly for single labeled, and if you ignore those multi-labeled samples, you every emotion has 9000 instances (if I remember correctly). Most people simply ignore those exceptions and tread it as single labeled only. If you are interested in multi-label emotion classification tasks, there are other options such as GoEmotions, and SemEval-18 task1.

Thank you very much. I appreciate your prompt response.


Chat bot

i found a bunch of interesting libraries here
https://www.npmjs.com/search?q=keywords:chatbot

[16:25, 11/12/2019] Xtina ⭐: here's a good start for the camp asia app - https://www.campasia.asia/about-us/faqs.html
[16:25, 11/12/2019] Xtina ⭐: we can use these as sample questions with sample answers


How do you change the order of the pages on the main navigation?

Hi! It seems as if the pages in the main navigation are in alphabetical order. Example:
Home | About | Contact | Portfolio
Is there any way to change the order to something specified? Thanks!

You can change the order by renaming the base files without changing the rest of their contents.
What I do is prepend a number to each page. In your case if you wanted Portfolio to be second in the list rename the pages:

1Portfolio.md
2About.md
3Contact.md

Changing the order of Home requires editing header.html, more work is required.

I'm relieved that it was something simple. Thank you!

:+1: 😃


fix: Check for wasm-opt during configure & run on post_build

Description
This PR makes the wasm-opt dependency more explicit. It is now referenced as a dependency since the wasm build fails without it. I've also added a find_program call to ensure it is installed during the configure phase for a wasm build; otherwise you'd get to the very end and it would crash.
I've changed the executable target to be barretenberg.wasm and then used the TARGET variant of add_custom_command so the wasm-opt command isn't run if barretenberg.wasm is already built. The previous way of doing this created a target that was always stale.
This should enable adding the wasm binary as an installation target, which is not possible with custom targets.
Checklist:

[x] I have reviewed my diff in github, line by line.
[x] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[x] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[x] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[x] There are no circuit changes, OR a cryptographer has been assigned for review.
[x] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[x] The branch has been rebased against the head of its merge target.
[x] I'm happy for the PR to be merged at the reviewer's next convenience.
[x] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[x] If existing code has been modified, such documentation has been added or updated.

Left a comment. Otherwise looks good to me. This is good cleanup.


Parse XML sitemaps via SAX for option to parse partial/broken documents

Updated #80 - merged with master branch, fixed a few issues, applied formatting, fix headers etc...
Will compare the perfs on some large sitemap files. I'd expect if not a gain in speed, then at least one in memory usage (since we don't hold the whole DOM representation in RAM).
Have closed #80, let's resume the work here.
@matt-deboer sorry it took so long to have another look at your work

I ran a benchmark on this branch vs existing DOM parsing. As expected is uses a lot less memory (90MB vs 180MB on my test docs)
[https://www.novinky.cz/sitemap/sitemap_articles_5.xml]
[http://www.foxnews.com/sitemap.xml?idx=26]
[http://push.abs-cbn.com/sitemap/2015/]

The SAX parsers do not work for cases like #29. Will add a test class to the master branch and apply it to this branch as well + fix some of the issues highlighted by @kkrugler.

Have identified a possible issue with the locations not being properly handled. Will add a test case to the master branch first.
@kkrugler I have addressed some of the issues you mentioned, will look again at the startElement() logic.

Was an issue with locations split over several calls to characters() - as illustrated by d200346
Still need to apply the same logic to XMLIndex, Atom and RSS Handlers and modify tests to cover for these cases.
The latest commit also improves the efficiency of the parsing as URLs were created twice from strings unnecessarily.

I've adapted this PR to master and for testing and evaluation doubled the parser classes (added SiteMapParserSAX), see this fork. After testing both classes on 35 problematic sitemaps and feeds: I've found no regressions, truncated docs are successfully parsed as expected, XML syntax errors do not affect the whole document, but only the tail after the error.
There are two option how to proceed:

replace the existing DOM-based parser
keep both parsers and let the user decide which one to use (cf. --use-sax-parser in SiteMapTester)

Hi @sebastian-nagel - so what would be a reason for keeping the DOM-based parser around? From @jnioche's comments above, SAX should be faster, use less memory, and should be more resilient to errors (would this also take care of #148?).

For the long-term, I principally agree: maintaining two parsers means additional work, and there are few arguments in favor of the DOM-based parser:

less code, 700 vs. 1000 lines, excluding license headers, ev. easier to read
optionally expose the DOM or parts of it? For the more complex, derived formats (images #36, videos #35, news) this could be a quick and extensible solution to make the additional information accessible without the need to define huge classes to hold all the information.

should be more resilient to errors

Right now, the only difference is that the SAX parser is able to extract URLs from the top of the XML document. It does not recover from an error. Would be nice if the parser could continue after trivial errors such as in #148. I don't know whether this is doable based on the existing code. I found one example (1, 2) in Python based on beautifulsoup.

SAX should be faster, use less memory

In addition, it could provide an iterator over SiteMapURLs. Often URLs are filtered or sampled, and there is no need to keep the complete list of 50,000 URLs (or more for sitemap indexes) in memory.
For the next time, I want to test the SAX-based parser and compare it to the DOM-based one. I'll prepare a larger test set (few 1000 sitemaps), right now I can share a list of 16 million URLs pointing to sitemaps.

+1 to having both for the time being.  @sebastian-nagel could you please open a new PR?

Done: #150. I've used the SAX parser to process 500,000 sitemaps, but have to mine the logs for potential regressions.

I've used the SAX parser to process 500,000 sitemaps

did you monitor the processing time and memory used compared to the DOM based one?

No, it was a mapreduce job, and also only an overlapping set of URLs. For performance measures, it's probably also better to use a sample on disk not URLs. A first comparison of the log files also shows that the Tika version (also changed) has some impact whether formats are properly recognized. I'll sample a subset of URLs (excluding sitemap indexes) and pre-fetch it for measuring performance, and to have a controlled environment with no differences except the parser.

Replaced by #150


Missing key-mappings for userstore configuration properties

Currently, we have only added key-mappings for the below properties.
"user_store.connection_url": "user_store.properties.ConnectionURL",
"user_store.connection_name": "user_store.properties.ConnectionName",
"user_store.connection_password": "user_store.properties.ConnectionPassword"

Other properties only can be configured using the actual property value.
Eg:
[user_store]
UsernameJavaRegEx = "^[\\S]{5,30}$"

But we have updated the documentation to add the above property as shown below.
[user_store]
username_java_regex="^[\\S]{5,30}$"

If we configure the additional changes as shown above it will not get reflected in the user-mgt.xml file.
Reference To: https://github.com/wso2/carbon-kernel/issues/2250
Suggested Labels:

Priority/High
Type/Config
5.9.0-Alpha

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Trigger Build - PE

next time write like this Trigger 2 - 12 may 1:28pm

next time write like this Trigger 2 - 12 may 1:28pm

Sure


Add LocalizedError conformance to AnyError on Linux with a workaround

Supersedes #216.

Can we run test with swift-DEVELOPMENT-SNAPSHOT-2017-05-19-a on Linux?
Or wait for next swift-4.0-DEVELOPMENT-SNAPSHOT?

I added DEVELOPMENT-SNAPSHOT-2017-05-21-a to the build matrix.

We need to use swift test -Xswiftc -swift-version -Xswiftc 4 for confirming #if swift(>=4.0) path.

Or adding swiftLanguageVersions to Package.swift.
Without them, SwiftPM builds with -swift-version 3.

Done

Thanks! 🚢


Fetch people tagged in a picture (but not tagged inside the captions)

Is it possible to fetch people tagged inside a instagram picture who might not be tagged inside the captions? since we can view this from the web i think it is possible but i had to ask anyways.
if yes i think it would be beneficial to add the feature since it would add to the completeness of data fetched while instaloading. a lot of instagrammers tag people inside the pictures but not the captions.

Indeed, this information is easy to get. Commit e471bd5 in branch v3.1-dev adds properties caption_mentions and tagged_users to the instaloader.Post class, making it available for --only-if fiters. However, it is not yet possible to tell Instaloader to export this information.

Commit e0ed4cf adds the --metadata-json flag which instructs Instaloader to dump the metadata of each Post into a JSON file.


docs: remove code sprint announcement from README

title says it all...

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


set callback path dynamically

AFAIK, it's currently impossible to easily set callback dynamically per call.
I propose passing callback_path transparently from request phase to callback phase. Below is a monkey patch.
Thoughts?
module OmniAuth
  module Strategies
    class OAuth2
      alias_method :original_request_phase, :request_phase
      def request_phase
        session['omniauth.callback_path'] = request.params['callback_path']
        original_request_phase
      end

      alias_method :original_callback_phase, :callback_phase
      def callback_phase
        session.delete 'omniauth.callback_path'
        original_callback_phase
      end

      def callback_path
        @callback_path ||= session['omniauth.callback_path'] || super
      end
    end
  end
end

Allowing the redirect_uri to be set from user input probably opens up account theft attacks, for example via URL fragments in 302 redirects.


Problem signing up

After signing up, I return to the login page. With out any hint if it was successful or that I would receive an email.
When I try to sign in with the credentials I signed up with I get an 'invalid credentials' comment.
I didnt receive any email.
Email should have been sent to<EMAIL_ADDRESS>Maybe this is the problem?

Demo site is up and running now.
Sign up-
https://chainfury.nbox.ai/ui/signup
Originally posted by @chanh-1 in > https://github.com/NimbleBoxAI/ChainFury/issues/72#issuecomment-1518538328

If you are being redirected to the login page after signing up, it indicates that your account has been successfully created. Please attempt to log in again using your username (not email) and password.


NPM-published version 0.51.0 uses 'jsonschema' not 'ajv'

Description
I need some of the features in the 'ajv' jsonschema validator (localization). The package.json you have published to NPM is using 'jsonschema' even though the package version is the same (0.51.0)
Version
0.51.0 (github)  <>  0.51.0 (npm)

Version 0.51.0 doesn't use the ajv library.

The package.json of the current version (0.51.0)  lists these dependencies:
"dependencies": {
"ajv": "^5.2.3",
"lodash.topath": "^4.5.2",
"prop-types": "^15.5.8",
"setimmediate": "^1.0.5"
},
While the version you have published to NPM (which is also 0.51.0) looks like this:
"dependencies": {
"jsonschema": "^1.2.0",
"lodash.topath": "^4.5.2",
"prop-types": "^15.5.8",
"setimmediate": "^1.0.5"
}

ajv didn't make version 0.51. It made it into 0.52.

Great, thanks 👍


CLI does not interpret some characters correctly

> wsk action create '.' a --docker -v
...
https://<IP_ADDRESS>/api/v1/namespaces/_/actions/?overwrite=false
...
error: Unable to create action: HTTP method not allowed, supported methods: GET, OPTIONS (code ...)

note the url has a missing ..
worse if you use /:
> wsk action create '/' a --docker -v
https://<IP_ADDRESS>/api/v1/namespaces
error: Unable to create action: HTTP method not allowed, supported methods: GET, OPTIONS (code ...)

In both cases the expected error should be, respectively:
error: Unable to create action: name '.' contains illegal characters (code ...)
error: Unable to create action: name '/' contains illegal characters (code ...)
I did not try other characters like ? and '&` which should be checked.

This seems to also affect whisk.invoke|trigger in the node js runtime.

@rabbah, even when the URL is correct, the backend is not returning the error that you mentioned. For example, when creating an action with just / as the name, the following URL should be generated. Note that the URL is missing an action name after /actions/.
https://{deployment_address}/api/v1/namespaces/{namespace}/actions/?overwrite=false

Here is the error returned from the server:
error: Unable to create action: HTTP method not allowed, supported methods: GET, OPTIONS (code 310776)

As you can see the illegal character error was not return. Perhaps some changes to the backend need to be made to generate the desired error. Obviously we can detect this situation with the CLI, and generate the proper error message. However, this does not help in the case where user is not using the CLI to create actions, etc.

I don't follow - the URL that is sent to the controller is wrong (ignores the dot for example). The error that's returned for https://{deployment_address}/api/v1/namespaces/{namespace}/actions/ is expected. You can only GET on that URI (it lists the actions in a package).

For the dot example, Go's built-in URL encoding is removing the dot. This happens if you put the correct URL into your browser as well. I can probably find a workaround for that.
I suppose the CLI will need to throw an error if the action name is just a forward slash before it even makes the HTTPS request.

the names of entities aren't uri encoded?

Entity names are being URI encoded. It appears that the /.? sequence is equivalent to /? when requests are made via HTTP(S). This seems to be true even when I try it out in a browser.
I can throw errors when the two mentioned cases occur (dot and slash), but the error will not contain a sequence number. Ie, you would just get error: Unable to create action: name '.' contains illegal characters without the (code ...) part.

@rabbah, why is it that I can create action names with "illegal characters" when said character is not at the front of the entity name? For instance, I can create an action with a name of action@name. However, I cannot create an action with a name of @name.

This is the regex for allowed names https://github.com/openwhisk/openwhisk/blob/master/common/scala/src/main/scala/whisk/core/entity/EntityPath.scala#L157.


Improve Intel 8086 compatibility

Hello, I am not a speaker of the English language, so I did not put any explanation in the initial request, as I have worked quite a lot with retrocomputing, especially with 8086, I will try to include in the 8086 support little by little the excellent compiler that you did, I am even seeing about 32bit and 64bit calculation in 16bit and 8087 emulation to be able to add to the compiler, so I do not send dozens of requests with small changes, would it be better to wait for me to implement bigger changes before sending a new request? Do you think it best to implement a flag to tell if the output should be at 8086 to interfere less with the code that is currently generated for 80186 or higher? Or in the scenarios where code is generated for 80186 can I replace it to make it more compatible with 8086?

Smaller C wasn't really designed to properly support 16-bit and 64-bit CPUs.
I'm not going to change that design in Smaller C as it exists today (if I do, it'll be a separate and quite different project, likely with a different name).
I'm not going to accept patches like this.
If you can contribute a macro file like sys/80186.h but for the 8086 with all the macros for the instructions that don't exist on the 8086, I may accept it.


accumulate: deprecate

see https://github.com/exercism/x-common/issues/553#issuecomment-279275406

@ryanplusplus If this is getting merged let me know if you also want to remove the accumulate directory from exercises, and I can include that in this commit.

Yeah, can you remove the actual exercise?

done :white_check_mark:

Thanks!


Unable to set goal pose and get trajectory

@MihirDharmadhikari Thanks for the excellent contributions.
Currently we are trying to deploy this package with real robot (SPOT) and currently able to get it work as it shown in the image.
We are using custom lidar odom package.

What does those highlighted bounding box indicates ?

What does this red box indicates ?

Would you please let us know ! how to set goal pose and get trajectory for the specific goal pose.
Appreciate any response.

Hi @ajay1606 ,
The highlighted box (the polygon) is called a no-go-zone or geofence. The planner will not span the graph in this area. If you want to disable or change it you can do it in the config file here:

This parameter will enable or disable the use of this functionality.
You can set a custom geofence here.

Regarding the red box. This is the no-gain-zone. No voxels in this volume will be counted for the volumetric gain calculation. You can disable it from here. If you simply comment out that parameter it will be disabled.
Since this is an exploration planner, the UI does not directly provide the functionality to set a goal point and get a path to it. There are two ways you can do it:

If you have triggered the exploration (by clicking on start planner in the UI) and the robot has explored some part of the map, then you can set a waypoint for it to plan to along the global graph as described here. The planner will plan a path to the closest vertex in the global graph.
The planner has a function implemented to find a path to a goal point. This is the function: (link). You can write a service that takes the goal position and calls this function. The volume in which the planner samples to calculate this path is set here.

Let me know if this helps.
Best,
Mihir

@MihirDharmadhikari Excellent, really very helpful to understand more better. But currently i have tried as it instructed in the document here.
But path trajectory not showing up in the rviz, as it shows while running simulation mode.
In case of simualtion: (Launch planner -> Initialization in RVIZ GUI -> Start Planner in RVIZ GUI
https://github.com/ntnu-arl/gbplanner_ros/assets/29722843/5d005c56-acfc-43a3-b2b3-b3bf5d4a6a3d
In case of rosbag: (Launch planner -> Initialization in RVIZ GUI -> Start Planner in RVIZ GUI
https://github.com/ntnu-arl/gbplanner_ros/assets/29722843/dbab04ce-376a-40d3-96d4-598ce4c85bbc
Why I am unable to see explored trajectory in real data case ! would you please help.
Greatly appreciate any response.

Hi @ajay1606 ,
From what I see in the video, I think the planner it trying to plan from the initial location where the robot was. Since you are replaying a rosbag and the robot won't follow the path that the planner has planned, the planner won't trigger the next planning iteration automatically. To test the exploration path I would suggest you do the following:

At the instance when you want to trigger the planner, click on stop planner.
Click start planner. The planner will plan the path from the current robot location.
If the planner still does not plan and show a path, check in rviz where the green box is. That is the location from which the planner is attempting to plan the path.
Additionally, you can change the verbosity of the planner here. Set it to Verbosity::INFO and recompile before you test. This will print a lot more information in the terminal about what is happening with the planner. If the planner does not plan, send me the terminal log as well.

Hope this helps.
Best,
Mihir

@MihirDharmadhikari Thank you so much for the very valuable inputs, I was eagerly looking for your response.
I will try as you suggested.
Which topic publishes the actual planner trajectory output ? To Subscribe robots control algorithm ! Checked with robot/command/trajectory, in simulation mode. But the topic not publishing any data.
Am I looking at wrong topic ?

Hi @ajay1606 ,
The planner operates in two modes kTopic and kAction. If you are using the kAction mode, it will act as an action server you can find more details about what are the action names etc. it in the wiki. But if you just want a publisher that publishes the trajectory (this is the easy way, the kAction is there in case the path follower is setup to work with ROS actions) use the kTopic mode. You can set this here, set the parameter to kTopic.  Then the trajectory will be published on the robot/command/trajectory topic. The message type is trajectory_msgs/MultiDOFJointTrajectory. Additionally, it will publish a nav_msgs/Path message type on the topic pci_output_path.
Best,
Mihir

@MihirDharmadhikari
After following instruction as you suggested, I am able see some log messages as below;

@MihirDharmadhikari Thank so much for your feedback, as you mentioned its working normally now. I have made following changes in the file here.
run_mode: kSim to run_mode: kReal
trigger_mode: kManual to trigger_mode: kAuto
output_type: kAction to output_type: kTopic

After above modification robot able to explore path as expected. Thank you so much for your assistance.
By the way, able to save using /gbplanner_node/save_map, But how can i load saved map ? And how to avoid real time mapping ? Would you please give some hints !
Thanks in advance.

Hi @ajay1606 ,
Glad to hear that it worked!
To load the map, voxblox also has another service gbplanner_node/load_map. You can provide the file path to it and it will load the map. Once you load the map, voxblox will start integrating the subsequent point clouds against this map.
Best,
Mihir

@MihirDharmadhikari
I have saved map in the location using map.vxblx extension.
After running command, terminal shows no error. But there are no map published in topic, nor in rviz.
How can i verify, map loading in gbplanned_node ?
rosservice call /gbplanner_node/load_map "file_path: '/home/spotbot/gbplanner2_ws/src/exploration/gbplanner_ros/gbplanner/map/map.vxblx'"

@MihirDharmadhikari Its working , thank you so much.

Hi @ajay1606,
Sorry for the late reply. When you set the goal manually, you put the planner in manual mode. To set it back to the auto mode you need to press the start planner button in the UI.
Best,
Mihir

@MihirDharmadhikari Thank you so much for being so kind and sharing always very valuable inputs.
By the way, my last question in this, is it fine to increase the set_goal distance limitation ? Does it has any impact on performance ? Because currently, it is limited to 15 m with in that we have to choose the set_goal.
While deploy in real robot, do we need sim packages also ? Just trying to optimize specific code related to exploration and planning. So is it fine to remove sim code ? Is there any other packages depends on that ?

@MihirDharmadhikari Thank you so much for your quick response.
Here is the variable set for maximum allowed distance : https://github.com/ntnu-arl/gbplanner_ros/blob/77afce521a3aa7a4b94bf6a43a3c88ec08b6d544/gbplanner/src/rrg.cpp#L3320

Regards,
Ajay

Hi @ajay1606 ,
You can increase that distance, but keep in mind that this method does not calculate a path directly to the goal point you have set but to the closest vertex in the global graph that the exploration planner uses for global repositioning. If you see the distance very high, the robot will plan to a vertex that is quite far away from the desired goal. If this is fine for your application, then you can increase it.
Best,
Mihir

@MihirDharmadhikari Thank you so much, its been a nice discussion and able to learn lot with you.
Thanks, and I will end this issue as my all questions has been well answered. Will open, new issue if we have any more questions.
Thanks for your kindness always !

Always happy to help! :smile:


Fix SQL introspection for Postgres 13

Per meeting discussion - mostly quoting @elprans: we shall advertise the EdgeDB server as a compatible Postgres cluster at a particular version through the binary protocol (and version-related SQL functions, etc.), regardless of the actual version of the backend Postgres in use. To unbreak CI and future releases, let's start from Postgres 13 and merge this PR.


psm: use double instead of float

Changes:

switch Voltages to doubles to avoid some casting during solution generation
use long-double when generating conductance matrix to avoid rounding error

Fixes:

numerical instability in CI (hopefully).

LGTM. Sort looks good


Update DNS export scripts to use dns_rcode_name UDF.

The dns_rcode_name() UDF was added in vizier release 0.12.8 (commit).

Should be safe to land January 11 according to our release policies


chore(deps): upgrade compiler dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-compiler-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1988

Questions ?
Please refer to the Backport tool documentation


Uncaught SyntaxError: Identifier '_0x4482' has already been declared

Hi,
we are getting Uncaught SyntaxError: Identifier '_0x4482' has already been declared error in console.
Expected Behavior
In console it should not show following error.
Uncaught SyntaxError: Identifier '_0x4482' has already been declared
Current Behavior
Getting error:
Uncaught SyntaxError: Identifier '_0x4482' has already been declared
Steps to Reproduce
Please try to obfuscate following sample function and obfuscated code use it in application.
function testCall(empList){
empList.forEach(function(object){
let smalest=findSmallPoints(object.points);
});
}
Your Environment

Obfuscator version used: 2.3.0
Node version used: v12.18.4

Cannot reproduce.
Show me your options and an example that WILL show this error.
For me the following code works fine:
function findSmallPoints(points) {
   console.log(points);
}

function testCall(empList){
  empList.forEach(function(object){
  	let smalest=findSmallPoints(object.points);
  });
}

testCall([{points: 'foo'}]);

// foo

@sanex3339 Thank you for reply.
Above mentioned obfuscated code working fine separately. But in our application we have many other obfuscated functions, with that if we include this obfuscated code we are getting error. Unfortunately I will not able to provide other obfuscated code.
Please note this issue we are facing with obfuscated code which is starting with const type. Our application other obfuscated  codes are starting with var. Is this possible can we get obfuscated output starting with var type?

Please show me your obfuscation options

https://obfuscator.io/
Default obfuscation options with above link. I tried with online also.

This identifier _0x4482 most likely is the string array identifier. It shouldn't be declared twice. So looks like you did something wrong. If possible send me your source code that you obfuscated via obfuscator.io. I can sign the NDA if you want.

Or send me the obfuscated code. Or try to find the problematic place by removing parts of the code.

Maybe you used same seed option for a two separate files that then were concatenated together. So with the same seed the names of the string array identifiers will be the same

This error happens every time after obfuscation or it appears randomly?
The name of the identifier in the error is always the same or it's the different?

Without all this info i cannot help

So, you mentioned that a single file works fine but a few files together are broken. So probably you used the same seed for each file.
Try to use a different seed for these files OR use the identifiersPrefix option to set the identifiers prefix for each file:
https://github.com/javascript-obfuscator/javascript-obfuscator#identifiersprefix

This is application issue, obfuscated code is working fine alone. Not able to find exact root cause. So temporarily unchecked string array in obfuscate option and obfuscated code does not contain constant type, this is resolved the issue temporarily. Thank you @sanex3339 for the support. 🙂

As i said before, try to use a different seed for each obfuscated file of use identifiersPrefix option

As i said before, try to use a different seed for each obfuscated file of use identifiersPrefix option

Yes we tried same, still facing same issue.

Show me the error with identifierPrefix option enabled.

need no example code nor reproduce steps, just think about this case:

a resuable js file is obfuscated with global const/let declarations
this file is run for more than once
then it absolutely(and inevitablely) will suffer an already been declared error

why don't we use var instead? the obfuscated code should not be modified so variables dont have to be 'readonly'


Infer types from object defaults

When you just pass model or collection object to attr spec, currently it's typeless. So, behavior is very confusing, it behaves like a bug.
We can infer type from the value, taking it from .constructor property (works in the same way for primitive types and models/collections).
It will shorten model definitions, and eliminate common mistakes. Also, it will make behavior consistent with primitive types.
To fix in v1.3.x

Done in 'develop'


libdislocator does not trigger a segfault on Darwin/MacOSX

First issue was using the environment variable DYLD_INSERT_LIBRARIES instead of LD_PRELOAD.
To be sure the lib was really loaded, I temporarily added a puts("init\n") in the init function. That worked. I got my expected output.
But none the less the test did not trigger the segfault. It should do so because the page following the allocation is protected.
$ DYLD_INSERT_LIBRARIES=../libdislocator.so ./test-compcov BUFFEROVERFLOW
This will only crash with libdislocator: TESTBUFFEROVERFLOW

on macOS it s always has been a bit complicated, you can try put, in addition, this environment variable, as DYLD_FORCE_FLAT_NAMESPACE=1 if you like.

Thanks, I tried it, but the cause is somewhere else.


Add to NPM for use in PhoneGap Build?

Any chance of making this available on NPM? I use PhoneGap Build and would love to be able to use this plugin.
Many thanks

I'll see what changes we need to make to add it to plugman and let you know!
(I assume that's what you mean?)

Hi Neil,
Apologies I guess I might mean plugman too?. Just going by a recommendation on the PhoneGap community forums ( http://community.phonegap.com/nitobi/topics/completely-hiding-soft-keys-in-android-build ) I did a quick check on Google and found this http://phonegap.com/blog/2015/05/26/npm-plugins-available/ so assumed that it would make sense to a plugin developer.
I guess I just want to be able to add it to my manifest.xml in the usual format for 3rd party plugins. e.g.
<gap:plugin name="org.apache.cordova.device-orientation" version="0.3.1" />
<gap:plugin name="net.yoik.cordova.plugins.screenorientation" version="1.3.1" />
Many thanks indeed

This plugin is now available via NPM


Rafsa

gog change the splash text to say "Rasfa" and a fun fact to say "Rafsa" and change the fun fact text to say "Rafsa" instead of "Fun Fact:"

hmm, no


Should be able to select text with given class

Actual behavior
Getting the error
Invalid arguments passed, only relativeSelectors are accepted

Steps to replicate

Using taiko run the following script

const { browser, openBrowser, goto, listItem, click, link } = require('taiko');
const assert = require("assert");

(async () => {
    try {
        await openBrowser();
        await goto("https://gauge.org/index.html");
        assert.ok(text("class","github_star").exists())
        await click(link(toRightOf(text("class","github_star"))),{waitForNavigation:true});
        await waitFor(5000);

        await closeBrowser();
    } catch (e) {
        console.error(e);
    } finally {
    }
})();

Version
0.0.9

Blocks #29

text() does not support fetching using attribute and values, text api can be used to fetch elements matching exact text.
await has to be added before checking exists so that the promise gets resolved, there it was asserting against a promise. assert.ok(await text("class","github_star").exists())
For clicking on github star something like this worked,
click(listItem("class","githubstar-box"))

Though this is not supported currently it would be a nice feature. Here is my use case I want to access the text with the given class.

This can be done using $
example - await click(link(toRightOf($(".github_star"))));


Incorrect path for renaming ignore to .gitignore

Renaming of ignore file fails due to incorrect path
➜  ~ pnpm create @animotion
AppData/Local/pnpm/store/v3/tmp/dlx-6796 |   +5 +
AppData/Local/pnpm/store/v3/tmp/dlx-6796 | Progress: resolved 5, reused 5, downloaded 0, added 5, done

┌  Welcome to Animotion!
│
◇  Where should I create your project?
│  test
│
◇  Install dependencies? (requires pnpm)
│  No
│
└  Done. 🪄

💿 Start the development server:
pnpm run dev

💬 Discord
https://joyofcode.xyz/invite
[Error: ENOENT: no such file or directory, rename 'C:\Users\akt01\ignore' -> 'C:\Users\akt01\.gitignore'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'rename',
  path: 'C:\\Users\\akt01\\ignore',
  dest: 'C:\\Users\\akt01\\.gitignore'
}```

I have worked on it and tried to fix this issue, I am linking the PR below, please have look at it.

This doesn't fix the issue for me yet!  @mattcroat, Is it really fixed?

This doesn't fix the issue for me yet! @mattcroat, Is it really fixed?

It works for me.


Add auto-changelog & CHANGELOG.md to easily compare releases

Partially fixes #72 by adding a generated CHANGELOG.md file to the project, listing all commits for a particular release/patch.
It should be generated with yarn changelog or npm run changelog everytime there is a new release.
See auto-changelog documentation for more infos.
It does not replace the need for a list of real breaking changes that should be added to the README, but it is something to start with 💁
Feel free to edit auto-changelog configuration to fit your needs!

Merged! Thank you for taking care of this.


How to reproduce the results in Table 5 of the paper?

The table5 in the paper shows:

With following the steps in CoCLR on Code Search section, I have applied CoCLR on the task of code search and got the result:

1.How can I get the results for rows 2 and 3 in Table 5? Is it to follow the steps in Vanilla Model? The step2 of Vanilla Model descripts To train a search model without CoCLR. What does the model without CoCLR refer to? Is it CodeBert?
2.The paper descripts Hence, we simply choose RoBERTa-base and CodeBERT as the baseline methods. So the result of row 2 in the table 5 can be get by https://github.com/microsoft/CodeBERT/tree/master/CodeBERT/codesearch, right? Codebert is then evaluated on the data cosqa-retrieval-test-500.json with follow command, right?

3.The row 3 in table5 shows the data is CSN + CoSQA. Can CodeSearchNet Python corpus and CoSQA be used for training at the same time? They have different data formats.
The CodeSearchNet data format is:

CoSQA data format is:

Can CoSQA be directly used to train codebert?

For question 1: Yes! You can refer to this part of README to reproduce the results. And the model without CoCLR means training with original data to some extend.
For question 2: No. Our model is different from vanilla CodeBERT in architecture. On one hand, we add one more layer above CodeBERT for better semantic fusion. On the other hand, we use a siamese network architecture while CodeBERT uses a cross-encoder architecture. Therefore, you can not reproduce the results only with the evaluation command. Instead, you can process the CodeSearchNet python corpus into the same format as the code search training data. Then training the model to reproduce row 2 and row 1 in table 5.
For question 3: You can try to train with CodeSearchNet Python corpus and CoSQA at the same time. But it ill-performs than training with CodeSearchNet first then with CoSQA. We guess the former adds noise while the latter enables the model to learn discriminant ability. You can also try to train codebert with CoSQA directly. Also the results will be poorer.

For question 1: Yes! You can refer to this part of README to reproduce the results. And the model without CoCLR means training with original data to some extend.
For question 2: No. Our model is different from vanilla CodeBERT in architecture. On one hand, we add one more layer above CodeBERT for better semantic fusion. On the other hand, we use a siamese network architecture while CodeBERT uses a cross-encoder architecture. Therefore, you can not reproduce the results only with the evaluation command. Instead, you can process the CodeSearchNet python corpus into the same format as the code search training data. Then training the model to reproduce row 2 and row 1 in table 5.
For question 3: You can try to train with CodeSearchNet Python corpus and CoSQA at the same time. But it ill-performs than training with CodeSearchNet first then with CoSQA. We guess the former adds noise while the latter enables the model to learn discriminant ability. You can also try to train codebert with CoSQA directly. Also the results will be poorer.

Thanks for your reply!
For answer 1: I run the vanilla model on code search and get the result as follow:

I don't know which model in the table this result belongs to. Is this the result of row 3 Model CodeBERT, Data CSN+CoSQA in table 5?

I'm a little confused. Why is the name of the third line model CodeBert? Vanilla Model was probably your method. Did I understand something wrong? And Vanilla Model's results (Final test MRR 0.6502) were not much different from CoCLR on Code Search's (Final test MRR 0.6526). It turns out a little bit strange.
For answer 2: You said Then training the model to reproduce row 2 and row 1 in table 5. Do the models in row 1 and row 2 refer to vanilla RoBERTa and  vanilla CodeBERT?
you said you can process the CodeSearchNet python corpus into the same format as the code search training data. Does the code search training data refer to the training data of vanilla RoBERTa and  vanilla CodeBERT or CoSQA?

As for question 1, we checked the code and found there's a bug, which lead to the mis-use of the model. Now we fix it, you can use the new code to reproduce the results in line 3 with the same command as before.
As for question 2, yes! Row 1&2 refer to vanilla RoBERTa and CodeBERT trained only on CodeSearchNet. And the code search training data  in your question refer to the training data of vanilla RoBERTa and vanilla CodeBERT.

As for question 1, we checked the code and found there's a bug, which lead to the mis-use of the model. Now we fix it, you can use the new code to reproduce the results in line 3 with the same command as before.
As for question 2, yes! Row 1&2 refer to vanilla RoBERTa and CodeBERT trained only on CodeSearchNet. And the code search training data  in your question refer to the training data of vanilla RoBERTa and vanilla CodeBERT.

Thanks for your reply! I try the new code to reproduce the results in line 3. There is an error:

What should I do? I don't meet the error when I use the old code.
I have another question: Can the models in row 1 and 2 also be evaluated with the testset cosqa-retrieval-test-500.json in CoSQA? The data format in CoSQA is different from the test set data format in CodeSearchNet.
In cosqa-retrieval-test-500.json:

In CodeSearchNet:

Hi @skye95git ,
Did you try training with CodeSearchNet python corpus. If yes, could you share the scripts for converting the CodeSearchNet data into CoSQA data format.
I am also trying to replicate for the CodeBERT + CodeSearchNet result.

For question 1: Yes! You can refer to this part of README to reproduce the results. And the model without CoCLR means training with original data to some extend.
For question 2: No. Our model is different from vanilla CodeBERT in architecture. On one hand, we add one more layer above CodeBERT for better semantic fusion. On the other hand, we use a siamese network architecture while CodeBERT uses a cross-encoder architecture. Therefore, you can not reproduce the results only with the evaluation command. Instead, you can process the CodeSearchNet python corpus into the same format as the code search training data. Then training the model to reproduce row 2 and row 1 in table 5.
For question 3: You can try to train with CodeSearchNet Python corpus and CoSQA at the same time. But it ill-performs than training with CodeSearchNet first then with CoSQA. We guess the former adds noise while the latter enables the model to learn discriminant ability. You can also try to train codebert with CoSQA directly. Also the results will be poorer.

As for question 1, we checked the code and found there's a bug, which lead to the mis-use of the model. Now we fix it, you can use the new code to reproduce the results in line 3 with the same command as before.
As for question 2, yes! Row 1&2 refer to vanilla RoBERTa and CodeBERT trained only on CodeSearchNet. And the code search training data  in your question refer to the training data of vanilla RoBERTa and vanilla CodeBERT.

Thanks for your reply! I try the new code to reproduce the results in line 3. There is an error:
What should I do? I don't meet the error when I use the old code.
I have another question: Can the models in row 1 and 2 also be evaluated with the testset cosqa-retrieval-test-500.json in CoSQA? The data format in CoSQA is different from the test set data format in CodeSearchNet. In cosqa-retrieval-test-500.json:
In CodeSearchNet:

hello this issue author, I have the same question. I just want to know how to get  row 1 and row 2  results. Can the models in row 1 and 2 also be evaluated with the testset cosqa-retrieval-test-500.json in CoSQA?  Are RoBERTa and CodeBERT the same model archetecture?


How can i use it for dynamic page views ?

Hi, My home viewcotroller consume data from web server and build the pages dynamically (Async call). Based on the web service response only I am going to setup the pagingmenu. Is it possible ? ( It works if I call the api in some other controller and pass it to homeview controller but I need it in home page only). Thank you for your great library :).

Hi,
there is a method named. rebuild(viewControllers, options: options)
You can use it like the setup(viewControllers: viewControllers, options: options) method.
So if your pages are loaded from the web service you an call the rebuild()method.

Wow. That would be great. Really appricite you help. Thank you very much.

Related : #77  #248


feat: implement pprof serialization internally

Description
Implements pprof encoding in the backend. The actual export is still untouched. Would like some feedback on the current approach and structure.
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?

[ ] Tested manually
[x] Added automated tests

Checklist:

[x] Unit tests have been added/updated
[ ] Documentation has been updated
[ ] Change file has been generated (npm run change:new)
[ ] Delete this branch (after the PR is merged)

Codecov Report

Merging #507 (a5119a3) into main (75b2d1d) will decrease coverage by 33.20%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main     #507       +/-   ##
===========================================
- Coverage   87.32%   54.12%   -33.21%
===========================================
  Files          26       28        +2
  Lines         773     2378     +1605
  Branches      176      911      +735
===========================================
+ Hits          675     1287      +612
- Misses         98     1091      +993

Impacted Files
Coverage Δ

src/profiling/proto/profile.js
36.01% <ø> (ø)

src/profiling/types.ts
100.00% <ø> (ø)

src/profiling/utils.ts
100.00% <100.00%> (ø)

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 75b2d1d...a5119a3. Read the comment docs.


Broken links found in the TCP spec

Description:
There are the broken links below found on the TCP spec and we need to fix them.

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Fixed via https://github.com/ballerina-platform/module-ballerina-tcp/pull/719/files.


[Bug Report] Wanderer card missing

Fixed in https://github.com/seriaati/shenhe_bot/commit/985372694aae0a7a17275654c136ee7136158204


Generics lost when getting collection of relationships

Larastan Version: v3.0.2
Laravel Version: v11.36.1

Description
When I have a relationship defined where the model returned has generics on it, the generics are lost when trying to get the collection.
When I check the type of the HasMany it shows correctly, but when I afterwards get the type of the relationship collection, the generics are gone.
Laravel code where the issue was found

    /**
     * @return HasMany<Membership<TOrganization, TTeam, $this>, $this>
     */
    public function memberships(): HasMany
    {
        /** @var Membership<TOrganization, TTeam, $this> $membership*/
        $membership = new Membership;

        return $this->hasMany($membership::class, 'user_id')
            ->with('role.permissions', 'team', 'organization');
    }

assertType('Illuminate\Database\Eloquent\Relations\HasMany<Membership<Organization2, Team2, User2>, User2>', $user->memberships());
assertType('Illuminate\Database\Eloquent\Collection<int, Membership<Organization2, Team2, User2>>', $user->memberships);

where are the TOrganization and TTeam defined and what are they?
what does the Membership class look like?
what are the actual errors you are getting?