Add support for tags

This is a working implementation and suits my needs; let me know if you'd like for tags to follow the Record model to keep the API more consistent

Looks good! (Ignore the failling test, that's my fault) I think that using a Map for the tags is more convenient for retrieval :+1: . One thing I would suggest is extracting the Map creation to a separate method to keep constructSeries simple. That would also make testing all branches of the switch statement less of a hassle, which you can also add if you want. Thanks!

Current coverage is 99.43%

Merging #2 into master will decrease coverage by -0.57% as of 4226eb5

@@            master      #2   diff @@
======================================
  Files           13      13
  Stmts          164     177    +13
  Branches        31      35     +4
  Methods          0       0
======================================
+ Hit            164     176    +12
  Partial          0       0
- Missed           0       1     +1

Review entire Coverage Diff as of 4226eb5

Powered by Codecov. Updated on successful CI builds.

Sort of followed the pattern used by Record as it eliminates the need for casting the result to get a successful test. An outer iterable isn't required as there is only one set of tags per series. Will add coverage for the malformed response and this should be good to go.

Perfect! Will cut a release right away. Thanks Cory

Thank you, this library saved me a ton of time. Look forward to contributing in the future.

Closes #1

@paulgoldbaum With this PR to enable group by, can still access the actual tag values? Are there any issues with exposing them? Working on something and would like to be able to associated the returned Series with the particular groupby tags. Thanks

@cmasekera tags are exposed for each series object like this: result.series.head.tags("TAG_NAME"). There's currently not a way to list what tags were returned. Is this something you would need?


Timeout on Store

I am trying to implement a code where if the packet receiver does not receive a packet within a period of time it must report it to the console.
I realized the simpy engine does not process this correctly, digging deep I realized that the engine removes the callbacks from the event but I cannot understand why.
Code below:

from simpy import *

def dbg_log(env, msg):
	tmp = '[%0.2f] %s' % (env.now, msg)
	print(tmp)

def packet_receiver(env, q):
	while True:
		dbg_log(env, 'RX: Queue len: ' + str(len(q.items)))
		event_a = env.timeout(10)
		event_b = q.get()
		condition = yield event_a | event_b
		if event_a in condition:
			dbg_log(env, 'RX: Timeout...')
		else:
			dbg_log(env, 'RX: received a packet...')
		yield env.timeout(20)

def packet_transmitter(env, q):
	yield env.timeout(500)
	while True:
		dbg_log(env, 'TX: Sending')
		q.put(10)
		yield env.timeout(50)

env = Environment()
packet_store = Store(env)
env.process(packet_receiver(env, packet_store))
env.process(packet_transmitter(env, packet_store))

dbg_log(env, "*** SIM START ***")
env.run(until=1000)
dbg_log(env, "*** SIM END ***")

Please help.

Snippet of the output:

[600.00] TX: Sending
[600.00] RX: Queue len: 1
[610.00] RX: Timeout...
[630.00] RX: Queue len: 0
[640.00] RX: Timeout...
[650.00] TX: Sending
[660.00] RX: Queue len: 0
[670.00] RX: Timeout...
[690.00] RX: Queue len: 0
[700.00] TX: Sending
[700.00] RX: Timeout...
[720.00] RX: Queue len: 0
[730.00] RX: Timeout...
[750.00] TX: Sending
[750.00] RX: Queue len: 1
[760.00] RX: Timeout...
[780.00] RX: Queue len: 0
[790.00] RX: Timeout...

Hi,
I'm not sure this is great from a user's perspective, but the following happens. Although your code "lost" interest in event_b after event_a fired, the simpy engine still delivers event_b. During your next loop, a new event_b request is sent to the simpy engine, your code having effectively lost the ability to retrieve the one that fired in the previous loop. I slightly modified your code to reuse event_bs across the loop if they are not consumed by your code:
from simpy import *

def dbg_log(env, msg):
	tmp = '[%0.2f] %s' % (env.now, msg)
	print(tmp)

def packet_receiver(env, q):
	event_b = None
	while True:
		dbg_log(env, 'RX: Queue len: ' + str(len(q.items)))
		event_a = env.timeout(10)
		if event_b is None:
			event_b = q.get()
		condition = yield event_a | event_b
		if event_a in condition:
			dbg_log(env, 'RX: Timeout...')
		else:
			dbg_log(env, 'RX: received a packet...')
			event_b = None
		yield env.timeout(20)

def packet_transmitter(env, q):
	yield env.timeout(500)
	while True:
		dbg_log(env, 'TX: Sending')
		q.put(10)
		dbg_log(env, 'TX: Sent')
		yield env.timeout(50)

env = Environment()
packet_store = Store(env)
env.process(packet_receiver(env, packet_store))
env.process(packet_transmitter(env, packet_store))

dbg_log(env, "*** SIM START ***")
env.run(until=1000)
dbg_log(env, "*** SIM END ***")

I understand that this behaviour is counter-intuitive, but I'm wondering how a more intuitive solution should look like. Should AnyOf conditional cancel interest in unfired events? Should there be a way to del event_b?

Interesting point! I think the event should be canceled too.
I think the main problem here is that when the timeout starts and the Store gets an element in the queue, it does not process the store event. It instead waits for the timeout to elapse.
The workaround I am using is:
t1 = env.now
while env.now < t1 + 1000:
	if len(queue.items) > 0:
		item = yield queue.get()
		break
	yield env.timeout(0.001) # small step

it works but it affects the simulation performance drastically.

I suggest you take my workaround. My workaround does not "lose" any events and, although looks ugly to read, it uses the simulation engine properly to wait for a timeout or packet arrival. Performance is therefore really good.


Updating NetworkWatcher.json for Connectivity Check API

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@supriyajha-ms , 2022-09-01 version was released, it needs to get breaking change review approval for the change in this PR. Alternatively, add these changes in new api version.
In addition, please fix modelValidation errors.

From: msftbot[bot] @.>
Sent: Sunday, April 2, 2023 9:33 PM
To: Azure/azure-rest-api-specs @.>
Cc: RITABAN BASU @.>; Comment @.>
Subject: Re: [Azure/azure-rest-api-specs] Updating NetworkWatcher.json for Connectivity Check API (PR #22987)
Hi, @supriyajha-mshttps://github.com/supriyajha-ms. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove no-recent-activity label.

Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-rest-api-specs/pull/22987#issuecomment-1493379793, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4TWWPRMJMENE2QFD4SD6YLW7GPLHANCNFSM6AAAAAAVUZUPEI.
You are receiving this because you commented.Message ID: @.***>

Feel free to re-open this PR if needed.


analytical dipole strenght

Hi,
is it possible to specify the strenght of analytical dipole source when using
import empymod as epm
 model = {'res': 1 / 3.2,  # Resistivity
                 'freqtime': 1,  #
                 'signal': None,  # Frequency domain
                 'solution': 'dhs',  # Diffusive half-space solution
                 'verb': 1}  # Verbosity
 field[:] = epm.analytical(ab=25, **model)
Or is it set internally constant to 1A?

Hi Jan, thanks for your interest in empymod!
No, it is not possible. The analytical solution calculates the solution for an infinitesimal small dipole of unit strength. It is not set internally to 1A, there is simply no strength-parameter for empymod.analytical.
For the analytical fullspace solution there is a way: You could use empymod.bipole, providing a fullspace model and setting xdirect=True; this way bipole uses internally the analytical fullspace solution. But in this case you could provide a strength-parameter (and even source and receiver length, orientation, etc).
However, for the analytical, diffusive halfspace solution that is not possible. But in the end you only have to multiply the output by your source strength, and that's it.
import empymod as epm
model = {
    'src': [0, 0, 0],     # Source
    'rec': [5000, 0, 0],  # Receiver
    'res': 1 / 3.2,       # Resistivity (Ohm.m)
    'freqtime': 1,        # Frequency (Hz)
    'signal': None,       # Frequency domain
    'solution': 'dhs',    # Diffusive half-space solution
    'verb': 1             # Verbosity
}

strength = 250  # strength in A

field[:] = strength*epm.analytical(ab=22, **model)

Similarly, you could multiply it by source and receiver lengths.
Please note that the diffusive halfspace solution is only implemented for electric sources and receivers, hence for ab=11, 12, 13, 21, 22, 23, 31, 32, 33, so you cannot calculate the diffusive halfspace solution for ab=25. The diffusive halfspace solution is after Slob, E., J. Hunziker, and W. A. Mulder, 2010, Green's tensors for the diffusive electric field in a VTI half-space: PIER, 107, 1--20: doi: 10.2528/PIER10052807, which only provides the solutions for electric source and receivers. If you need halfspace results for ab=25 then you have to use the numerical solutions dipole or bipole. Again, with bipole you could define the source strength.
Hope that helps!


rTorrent plugin error with scgi uri

https://github.com/Flexget/Flexget/commit/1f4ef0e1db1928acbe623877f7f7a37f2a05b8f5
this commit produces the following error with a rtorrent uri in the config like
    rtorrent:
      uri: scgi://localhost:5000

Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/flexget/task.py", line 438, in __run_plugin
    return method(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flexget/event.py", line 22, in __call__
    return self.func(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/plugin_rtorrent.py", line 405, in on_task_start
    if client.version < [0, 9, 2]:
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/plugin_rtorrent.py", line 262, in version
    return [int(v) for v in self._server.system.client_version().split('.')]
  File "/usr/lib/python2.7/xmlrpclib.py", line 1233, in __call__
    return self.__send(self.__name, args)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/plugin_rtorrent.py", line 147, in __request
    response = self.__transport.request(self.__host, self.__handler, request, verbose=self.__verbose)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/plugin_rtorrent.py", line 63, in request
    return self.single_request(host, handler, request_body, verbose)
  File "/usr/local/lib/python2.7/dist-packages/flexget/plugins/plugin_rtorrent.py", line 80, in single_request
    addr_info = socket.getaddrinfo(host, int(port), socket.AF_INET, socket.SOCK_STREAM)
TypeError: int() argument must be a string or a number, not 'NoneType'

This error occurs due to urlparse() being run on just the hostname on line 76 of def single_request
as there is no scheme, port etc. this fails

Hmm, I i'll fix this shortly.

That should fix it.. Good to see someone using the rtorrent plugin :+1:

Nice one!
Just checked out your fix and it wasn't far off how i patched it (though you did it as a oneliner!)
Once i'm a bit more familiar with the source i'll start providing fixes rather than just raising issues hopefully.
Do you know of any info on setting up the development branch and being able to run the tests?

take a look at http://flexget.com/wiki/GitHubInstall
if you join the irc channel we can help you out.


getAlert returns undefined after upgrading from 1.1.0 to 1.2.0

Bug report
We tried upgrading to 1.2.0 from 1.1.0, following the changes in AppDelegate.h and AppDelegate.m. After installing the update when receiving notification in the background, when we call notification.getAlert(), it returns undefined. Also getData() doesn't seem to work. After going back to 1.1.0 and commenting out below function it works as expected again:
// IOS 10+ Required for localNotification event
- (void)userNotificationCenter:(UNUserNotificationCenter *)center
  didReceiveNotificationResponse:(UNNotificationResponse *)response
         withCompletionHandler:(void (^)(void))completionHandler
{
  [RNCPushNotificationIOS didReceiveNotificationResponse:response];
  completionHandler();
}

Environment info

react-native info output:
System:
    OS: macOS 10.15.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 443.91 MB / 32.00 GB
    Shell: 3.0.0 - /usr/local/bin/fish
  Binaries:
    Node: 13.12.0 - /usr/local/bin/node
    Yarn: 1.22.4 - node_modules/.bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 23, 25, 26, 27, 28, 29
      Build Tools: 27.0.3, 28.0.3
      System Images: android-24 | Google Play Intel x86 Atom, android-25 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom, android-R | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>77832
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Python: 2.7.15 - /usr/local/bin/python
  npmPackages:
    @react-native-community/cli: ^3.0.4 => 3.2.1
    react: 16.12.0 => 16.12.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 1.2.0

related to https://github.com/react-native-community/push-notification-ios/issues/107


Updated investigation title on instrument detail page so that it is a link that can navigate a user to the respective investigation detail page.

🗒 Summary
This PR addresses the following:

Updated the investigation title stats item on the instrument detail page in the header so that it is now a link that can navigate a user to the respective investigation detail page
Added new "links" utility to centralize the location of functions to assist with generating links throughout the portal.
Updated investigation and instrument directory pages to use newly added link utility functions
Removed unneeded code and import statements due to addition of links utility functions.

⚙ Test Data and/or Report
Tested locally and ensured that npm run build does not generate any errors.
♻ Related Issues

Fixes #117

Added link util usage to home page search.


Added URL mapping for Release attachments like on github.com

Implement a Git Hub style URL mapping for the attachment files in Release.

Can you merge this please!

@gdeverlant would you be able to resolve conflicts as well as update per @lafriks's suggestion?

Forgive me for bothering, but I'm just trying to understand: What exactly does this PR do? I'm not able to understand clearly. We already have releases with attachments, don't we?

@rakshith-ravi it provides clean URLs for attachments (has filename in URL), instead of the URL being the UUID of the uploaded file.


[Batch Normal] Would you have plan to sync batch normalization?

For semantic segmentation, it is very import to syncbn. would you tell us how to do it?

Duplicate of #18222


N17: Release

Preview (https://github.com/rust-gamedev/rust-gamedev.github.io/commit/2fe5c722a1fa37750a91745c3db1e7c1697ee8ca): https://rust-gamedev-preview.netlify.app/posts/newsletter-017
Everyone is invited to review!
:timer_clock: Hope to merge this in an hour or so if there're no objections.
Part of #408 ("Newsletter 17")

Github won't let me point out the relevant section, but the Bevy section was changed to use semicolons instead of periods or commas to end bulleted lists, which feels a bit awkward nothing else in the newsletter does that:
- a WebGL2 render backend;
- cross platform main function: `#[bevy_main]`;
- live shader reloading;
- Schedule v2 with custom stages, run criteria, fixed timestep,
  and typed stage builders;
- States that allow you to enable/disable systems
  according to the state your app is in;
- scenes can now be spawned as children;
- dynamic linking that significantly cuts compile times.
- a new general-purpose Rust reflection API;
- 3D texture assets;
- HIDPI fixes;
- GLTF, timer, text layout, task system, logging & profiling improvements;
- ECS improvements: flexible system parameters, improved query filter API,
  and system inputs/outputs/chaining;
- Apple Silicon support!

Github won't let me point out the relevant section, but the Bevy section was changed to use semicolons instead of periods or commas to end bulleted lists, which feels a bit awkward nothing else in the newsletter does that:
- a WebGL2 render backend;
- cross platform main function: `#[bevy_main]`;
- live shader reloading;
- Schedule v2 with custom stages, run criteria, fixed timestep,
  and typed stage builders;
- States that allow you to enable/disable systems
  according to the state your app is in;
- scenes can now be spawned as children;
- dynamic linking that significantly cuts compile times.
- a new general-purpose Rust reflection API;
- 3D texture assets;
- HIDPI fixes;
- GLTF, timer, text layout, task system, logging & profiling improvements;
- ECS improvements: flexible system parameters, improved query filter API,
  and system inputs/outputs/chaining;
- Apple Silicon support!

:timer_clock: merging in 20 minutes

:timer_clock: merging in 20 minutes

A plugin integrating Bevy. ECS with doryen-rs Ascii roguelike library.

Was meant to be "Bevy's ECS" ?

A plugin integrating Bevy. ECS with doryen-rs Ascii roguelike library.

Was meant to be "Bevy's ECS" ?

Was meant to be "Bevy's ECS" ?

Yup. Looks like that got added in this style-fix commit:
https://github.com/rust-gamedev/rust-gamedev.github.io/pull/436/commits/5cc9150c8bdb464f0524724079175df2c13c9507

Was meant to be "Bevy's ECS" ?

Yup. Looks like that got added in this style-fix commit:
https://github.com/rust-gamedev/rust-gamedev.github.io/pull/436/commits/5cc9150c8bdb464f0524724079175df2c13c9507

Ok, so I'm merging this, but feel free to report other issues if you happen to see them - I'll fix them in separate commits.

Ok, so I'm merging this, but feel free to report other issues if you happen to see them - I'll fix them in separate commits.

:tada:

:tada:


[CCXDEV-14419] Removing CODEOWNERS as a follow up to related task

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.86%. Comparing base (66568cd) to head (d5ed98f).
Report is 12 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #277   +/-   ##
=======================================
  Coverage   85.86%   85.86%
=======================================
  Files          28       28
  Lines        1196     1196
=======================================
  Hits         1027     1027
  Misses        169      169

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[super] Sign in flow

[x] Sign in button on main page and in navbar
[x] Hand off to external auth provider
[x] Handle return and issue token
[x] Redirect to dashboard (or page they came from?)

[Fixed] doe to PR https://github.com/frictionlessdata/dpr-api/pull/54


ENH: Use tz-aware dtype for timestamp columns

I couldn't figure out how not to get a tz-aware dtype in 0.24.x
versions, and I wanted a tz-aware dtype anyway for TIMESTAMP, so this
makes it official.
Towards #261.

Looks like we'll have to bump the minimum version to 0.20.0, as pandas.api.types.DatetimeTZDtype was first exposed publicly in https://github.com/pandas-dev/pandas/pull/16099

Oof. Looks like I still get the occasional TypeError: data type not understood for all versions before 0.24.0.
@max-sixty Thoughts on bumping the minimum version all the way to 0.24? It's a big jump from what we've had before. Otherwise, I'll see if I can make our tests robust against having naive datetime in 0.23 and before.

I'm going to branch this PR with just the docs changes. I'd rather not bump all the way to 0.24.0 just yet.

Closing in favor of https://github.com/pydata/pandas-gbq/pull/269. As was pointed out to me in https://github.com/pandas-dev/pandas/issues/25843#issuecomment-476426843 it's more "idiomatic" to call localize rather than be specific about timezones in the dtype. I'd prefer to avoid additional casts / localization if at all possible, so just documenting the current behavior for now.


[HB-7033] Handle Memory Leak

Fixes a memory leak for fullscreen ads.
Updated CHANGELOG, README, Adapter version to <IP_ADDRESS>.1

Will be pushing another commit that moves the listener to an internal class.


Panic in golang compiler on macOS Sierra Third Public Beta (16A270f)

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go version go1.6.3 darwin/amd64

What operating system and processor architecture are you using (go env)?

Third public beta of macOS Sierra 10.12 (build 16A270f)
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/userid/codex/gopath_m2"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.6.3/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.6.3/libexec/pkg/tool/darwin_amd64"
GO15VENDOREXPERIMENT="1"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common"
CXX="clang++"
CGO_ENABLED="1"

What did you do?

I checked out and tried to install:
https://github.com/n1rvana/go-spammer
This is a trivial app.  This issue has appeared with all apps I've tried to compile since installing this beta of the OS.

What did you expect to see?

Would it be possible to refer to a method to produce a working set of go binaries with that patch?  Or the right commit?
The method mentioned in that thread seemed to involve two Macs, one to build 1.4, then another to use that 1.4 to build a later version.

Found solution is to use Go 1.7rc5 as workaround:
https://golang.org/doc/install?download=go1.7rc5.darwin-amd64.pkg

using 1.6.3 and suffering the same issue.... Is it necessary to upgrade the complier to 1.7 ? I wanna keep using 1.6

Why do you want to use 1.6, 1.7.1 is better in every single way.
On Fri, Sep 23, 2016 at 6:01 PM, John Zeng<EMAIL_ADDRESS>wrote:

using 1.6.3 and suffering the same issue.... Is it necessary to upgrade
the complier to 1.7 ? I wanna keep using 1.6
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/16585#issuecomment-249127972, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcAyrZL8Xp8GsIOyHdj4-Ie_4z510Oks5qs4dDgaJpZM4Jb3g_
.

@davecheney Actually it's ok for me to upgrade to 1.7 , but not my production env.... Any way, production is using linux, it's ok so far.

Was having the exact same issue and upgrading to 1.7 fixed for me.


Starving while AFK

Players report that they have starved and died while afk, which reportedly should not happen. If you are standing still you should not lose hunger and then starve.
Do we have any civ mechanics in place for adjusting hunger/saturation/starvation? I seem to recall hearing something about it on Civclassic, but I can't find anything in configs.
Needs more info/ testing/ confirmation

https://github.com/CivMC/CivDocker/blob/master/paper/config/spigot.yml#L131-L137

Those are set to the default Spigot values, so vanilla behavior would be expected (unless the default Spigot settings do not correspond entirely to vanilla minecraft behavior)

I did some digging and these seem like the only config related to hunger

Do we have any civ mechanics in place for adjusting hunger/saturation/starvation?

Finale

This is the only Finale options I see around hunger, is the code for one of these doing it? https://github.com/CivMC/CivDocker/blob/master/paper/config/plugins/Finale/config.yml#L53

Once we narrow down the cause, I can move this issue to the correct repo


Multiple pipeline instances

Allow creating multiple pipeline instances, e.g. several model_api with different configs.

Solved in #40


https://github.com/jaredwray/keyv/pull/433#issue-1343297829I think this should be engines.node if you want package managers to enforce this. This is also a breaking change for users running < v14. I would highly recommend a major version bump to accompany this change.

I think this should be engines.node if you want package managers to enforce this. This is also a breaking change for users running < v14. I would highly recommend a major version bump to accompany this change.
Originally posted by @trevor-scheer in https://github.com/jaredwray/keyv/issues/448#issuecomment-1221612007

@1plansex1 - this was already take care of with the latest version


Needed Code

Hi,
Can you please provide me the code ,
there is source code but i am not getting it.
can you procide me in detail i needed its urgent.
Do the need full.
Thanks

Hi,
The wiki of my repositories is always extremely detailed, you can find all information there.
Regards,
Roberto


XmlSwitch pipe has unexpected behaviour

Describe the bug
When using the class nl.nn.adapterframework.pipes.XmlSwitch  you can make a referance to a stylesheet by using the attribuut : serviceSelectionStylesheetFilename this goes as expected.
But when you use the attribuut : styleSheetName the adapter will start and run but when the flow reaches this pipe the xslt will be ignored as will the rest of the functionality of the pipe.
It will just try to use the input to resolve a path to the next pipe which will (in most cases) not be found.
Reporter
My name is sir Tarik
Category

Frank Framework

To Reproduce
Steps to reproduce the behavior:

create an adapter with a xmlswitch pipe in stead of using the attribuut serviceSelectionStylesheetFilename to reference your xslt file, use styleSheetName

Expected behavior
The adapter shouldn't be able to strat up and tell the end-user the attribuut styleSheetName is not expected in the .... pipe
Screenshots

You can actually use the XmlSwitch without a stylesheet and yes it will take the input of the pipe to make a decision.
This is useful when you want do multiple switches in your pipeline based on the outcome of the same stylesheet. In that way you do not have to re-execute the same stylesheet everytime you want to do a switch again.
So that the adapter starts without any problems is expected behaviour.
Although I do agree that attribute names do not match with XsltPipe. Maybe a solution could be to make attribute names across pipes the same, so adding styleSheetName as an alias for serviceSelectionStylesheetFilename for the XmlSwitch.
I hope this clarifies your issue a bit.

@alisihab deprecate serviceSelectionStylesheetFilename and make styleSheetName the attribute to use


Don't try to download windows exe/msi and mac universal pkg if it doesn't exists for python version requested

Only some minor versions of python have an actual windows .exe / .msi installer.
eg:

this does https://www.python.org/downloads/release/python-3810/
this doesn't https://www.python.org/downloads/release/python-3811/

Rather than silently ignore some network failures that would lead to the version being skipped, the json returned by https://www.python.org/api/v2/downloads/release/?is_published=true should be parsed to check if the package exists or not. This shall probably be done while generating the build matrix.


Marshalling with a namespace and an empty prefix

Currently, marshalling with a namespace and an empty prefix creates a default p0 prefix:
<p0:purchaseOrder xmlns:p0="http://www.example.com/PO" orderDate="1999-10-20">
  ...
</p0:purchaseOrder>

Working example: http://jsfiddle.net/LP3DC/493/
Would it be possible to instead have the XML be generated with no prefix? I.e. generate the following:
<purchaseOrder xmlns="http://www.example.com/PO" orderDate="1999-10-20">
  ...
</purchaseOrder>

The later output is smaller and, to a human, easier to digest.
Does Jsonix natively provide any way of generating the later output?
Side note: I believe a saner default for the prefix (rather than p0) would be the module's name (i.e. PO in the above example).
Thank you for the awesome work so far!

See https://github.com/highsource/jsonix/wiki/Configuring-Namespace-Prefixes.
I think you can configure '' as a prefix then you'll have no prefix.

I did try this previously but somehow I messed up the object orded: instead of {namespace: prefix}, I went with {prefix: namespace}; of course, nothing happened then.
Thank you for your quick reply!


Improve Button Interactivity: Add Hover and Active States

Currently, the buttons "Find Scholarships"  "Find Jobs"  on the landing page of PathSphere are static, and do not have any interactive visual feedback on user interaction. Adding hover and active states will enhance the overall user experience and make the buttons feel more responsive and engaging.

This issue will help improve the visual responsiveness and overall interactivity of the buttons, making them more engaging and user-friendly.
I would like to contribute to the project under gssoc-exd2024.

I believe that i can resolve this issue. as i have a good hold over css styling .
please assign me this issue under GSSoC24 Extd

@manninookala  I want to resolve this issue plz assign to me .

@Nikhilkumar111 i am blocking you from contributing in this repo i gave you enough warning you have commented on all the issues here

Hello @aditya-bhaumik I would love to contribute in this issue and resolve it surely, assign this it to me under GSSoC24 Extd.

@manninookala you can start working in this issue make sure to follow the contributing.md properly it will help you get the  pair extraordinaire  github badge

@manninookala its been two days and no pull request was made so we are closing this issue


Can't create different type vars with same name

num_players$ = ""
num_players! = 0;

results in ERROR: A(n) string named num_players already exists in file startrader.bas in line 9
Not sure, if this is a bug. You could do this in BASIC V2 though.

This is not allowed in XC=BASIC. I'll update the docs accordingly.


Add support for "unpublished" site config in Jekyll

All pages including unpublished pages (published: false is set in AsciiDoc Header) will be generated in either of the following cases:

unpublished: true is set in _config.yml
jekyll serve or jekyll build is executed with the option --unpublished

This feature is useful for previewing unpublished pages.
I added a test for it. If this test is needless (or redundant), I will revert it.

Does the draft feature not cover this?
Put the preview in the _drafts directory, and if you want to see it use
jekyll serve --draft
I find:
jekyll serve --draft --future helpful if I've put a future date on that item also.

You should already be able to accomplish this by setting page-published in the site-wide AsciiDoc attributes defined in _config.yml. See https://github.com/asciidoctor/jekyll-asciidoc#asciidoctor. The site-wide AsciiDoc attributes override the document attributes.

Thank you for your comments.
It is true that the same thing can be accomplished by using drafts feature or site-wide AsciiDoc attributes in _config.yml.
However, jekyll serve --unpublished still will not generate unpublished pages (the pages such that published: false is set in Asciidoc attributes). It seems strange that jekyll serve --unpublished behaves differently with and without this plugin(jekyll-asciidoc), I think.

Thanks for clarifying. That makes a lot of sense.
I think the setting should be made to override the page-published AsciiDoc attribute, which in turn will force the page to be published. So the integration / lookup should happen earlier, when the site-wide attributes are being resolved. That would ensure the AsciiDoc attribute reflects the effective value. So everything is fine here except where the option is looked up.

I agree. Then I fixed.

I opened https://github.com/asciidoctor/jekyll-asciidoc/issues/257 to relate this to an issue.
Your last implementation is not where Dan suggested, it's per-page rather than where the global config is being set up.
Your test looks good.
I'll implement this in the suggested place and use your test by copying it :-) unless I figure out how to cherry-pick it from your branch.

I managed to cherry-pick your test, hopefully you being the author will be obvious.


MySQL support

I plan to add MySQL support to give the package feature parity with Kysely.

Looking forward to it!

#8

I'm implementing MySQL support in #12. It should be noted that it uses this connection string format (which mysql2 appears to understand):
mysql://user:password@localhost/database

If Connector/NET-style connection strings are deemed desirable, it may be implemented in the future. But it may be a separate issue in that case.


Color and Comment misalignment

Hello everyone, and congratulations on this viewer, which is among the best I have seen for QT.
I am facing a series of problems that I cannot understand if they are due to incorrect use on my part, a bug, or simply the lack of the function.
Here is what happens to me:
I initialize the memory of the buffer that I want to add to the document and add it to the last bytes of the document:

QByteArray PackedData(in_Buffer, in_Bytes);
g_hexdocument->insert(g_hexdocument->length(), PackedData);

I add a comment and a color to the text:
g_hexview->setForeground(StartPosition, EndPosition, TextColor);  // Set Text Color
g_hexview->setComment(StartPosition, EndPosition, Comment);  // Add a comment at offset range [12, 42)

I add more and more packets.
Now I remove the very first packet from the document:
g_hexview->setComment(0, in_Bytes, "");  // Clear Comment
g_hexdocument->remove(0, in_Bytes);

So far, no problem, the editor removes everything correctly from the QHexDocument.
The problem is that if I remove bytes from position 0 (in my case I have a FIFO that displays a rotating buffer) the color remains offset if the packets are of different sizes.
In essence, while the data is processed correctly, colors and comments remain fixed and are not removed and remapped correctly for the remaining data.
The result is that comments and colors always refer to the positions of QHexView and are not anchored to QHexDocument.
Unfortunately, I believe this is the intended behavior, which creates significant problems in the case of dynamic editing with a rotating buffer.
The question is if I have correctly understood the operation, if I am using the objects correctly, or if it is simply a limitation of the code.
Using a FIFO in a data stream becomes too slow to keep the map of all packets and dynamically change comments and colors on the fly every time the oldest packet is removed.
Any help would be greatly appreciated.

No clue guys?

I'm on summer holidays, I can't check it right now!

Ok, I have checked the code, and yes: metadata information are a model, so they are retained between data changes it's the intended behavior.
What behavior do you want to achieve instead? All metadata related to a specific range must be deleted when something changes? Or something else?

Hi Dax89,
Thank you for your answer and sorry for the delay, but I also took a few days off. In the meantime, I’ve tried and reviewed the code myself and have come to the conclusion that if you remove bytes that have a comment or a color, the related metadata doesn't change, which results in everything being misaligned.
Let me give you an example:
  AA BB CC DD    00 01 02 03
|   comment1  | | no comment |

If you remove AA BB CC DD, you end up with comment 1 at position 0, where AA BB CC DD no longer exists, but 00 01 02 03 is there instead. So the appropriate comment for the original bytes is now "assigned" to the wrong data.
This is what happens on my end, and I believe it's what you're referring to in your response. As you can see, it would be correct for the metadata to follow the bytes in the buffer, and therefore, in this case, be deleted as well. Does that make sense? Let me know if what I’m seeing here aligns with the correct functioning of the library.
P.S. I've added a few changes to the code, for example, to increase the font size when you press the CTRL key and move the mouse wheel, similar to other editors.
Note: I've noticed that when using certain fonts, the separator lines become misaligned with the text and sometimes end up almost in the middle of the hexadecimal bytes.

Ok, it's clear.
I can add that feature, but it can be very slow because the widget needs to check where the insertion/deletion happens and move every metadata that follows by the same amount of line/columns in order to keep visualization consistent.
Metadata is stored internally as map of lists of ranges where the key is the line (so it's not flat).
There is (a better) alternative: you can create you own QHexDelegate, with this class you can manage bytes' highlighting everytime a repaint happens.
class MyHexDelegate: public QHexDelegate {
    Q_OBJECT

public:
    ...
    bool render(quint64 offset, quint8 b, QTextCharFormat& outcf, const QHexView* hexview) const {
      // You can handle highlighting here
    }
    ...
};

// Attach the delegate to QHexView instance
auto* mydelegate = new MyHexDelegate(g_hexview);
...
g_hexview->setDelegate(mydelegate);
...

I can extend QHexDelegate it order to support comments too, in this case you keep metadata information on your side and it will be served to QHexView when needed.


Update Sentry IP address

See blog post here https://blog.sentry.io/2020/10/27/notice-of-internet-address-change?utm_medium=email&_hsmi=98671120&_hsenc=p2ANqtz-__PUr3R7qGWbW7M4ctFnXsc9pKunqtPrYXPXwZlnsoIfMboaNfG28lZ2J54pqWmrnokffW-uuCi1QpfBv6gaPtc4KBbw&utm_content=98671120&utm_source=hs_email
Acceptance Criteria

[ ]  Sentry still works

There is no change needed to account for this change with Sentry. It's specifically about making adjustments to firewall rules to permit the traffic to Sentry, this does not apply to us.


Support for DynamoDB and S3

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

I was planning to use ent for a small personal hobby project where I intend to use it alongside dynamodb and s3.  I can foresee some requirement as of now to compare data in dynamodb and s3. The project has some graph based relation related requirements over and above standard relations because of which I thought ent would be a suitable ORM candidate to achieve this.
Motivation 🔦

Currently ent does not support dynamodb / S3 . I found a comment here and  wanted to check if this is under works and if there would be any announcement on it.

Hey @rams3sh
Thx for reaching out!
DynamoDB and S3 are definitely on our roadmap. We don't yet have an time estimates, but I completely understand your use case and agree that it's needed.
Feel free to subscribe to our newsletter for updates on coming releases!
https://www.getrevue.co/profile/ent

Hey @rotemtam
Thanks for the response. Also, would there be any guide or doc that I can refer if in case I would want to contribute for an adapter for ent.

How is the going?
Can I contribute to this?

Is this still considered part of the roadmap and, if so, is there a rough estimate on a target release? Thank you!


[C++][Compute] Support casting a smaller struct to a bigger one if extra fields are nullable

Describe the enhancement requested
Arrow can already cast to a schema with an extra column if that column is nullable but it can't do the same on structs.
More precisely I want the follow unittests to pass
TEST(Cast, StructToBiggerStruct) {
  std::vector<std::string> field_names = {"a", "b"};
  std::shared_ptr<Array> a, b;
  a = ArrayFromJSON(int8(), "[1, 2]");
  b = ArrayFromJSON(int8(), "[3, 4]");
  ASSERT_OK_AND_ASSIGN(auto src, StructArray::Make({a, b}, field_names));

  const auto dest =
      arrow::struct_({std::make_shared<Field>("a", int8()),
                      std::make_shared<Field>("b", int8()),
                      std::make_shared<Field>("c", int8(), /*nullable=*/false)});
  const auto options = CastOptions::Safe(dest);

  EXPECT_RAISES_WITH_MESSAGE_THAT(
      TypeError,
      ::testing::HasSubstr("struct fields don't match or are in the wrong order"),
      Cast(src, options));
}

TEST(Cast, StructToBiggerNullableStruct) {
  std::vector<std::string> field_names = {"a", "b"};
  std::shared_ptr<Array> a, b, c;
  a = ArrayFromJSON(int8(), "[1, 2]");
  b = ArrayFromJSON(int8(), "[3, 4]");
  ASSERT_OK_AND_ASSIGN(auto src, StructArray::Make({a, b}, field_names));

  const auto type_dest = arrow::struct_(
      {std::make_shared<Field>("a", int8()), std::make_shared<Field>("b", int8()),
       std::make_shared<Field>("c", int8(), /*nullable=*/true)});
  const auto options = CastOptions::Safe(type_dest);

  c = ArrayFromJSON(int8(), "[null, null]");
  ASSERT_OK_AND_ASSIGN(auto dest, StructArray::Make({a, b, c}, {"a", "b", "c"}));
  CheckCast(src, dest);
}

Does this sound like a reasonable thing to support? The motivation comes from https://github.com/delta-io/delta-rs/issues/1610 but I think the fix would require a change to arrow.
Component(s)
C++

This suddenly became a critical problem for me so I ended up implementing something that works, but I'm not really sure if its a good implementation. If the idea seems reasonable I can open a PR.

@lidavidm What do you think about this? It seems that this is related to https://github.com/apache/arrow/pull/12724 / https://github.com/apache/arrow/issues/31101.

Yeah, I think in general if it works on tables but not structs (or vice versa) we should make them both work.

Issue resolved by pull request 44587
https://github.com/apache/arrow/pull/44587


[FancyZones] Show numerical value of the zones while editing

Currently when editing the zones, the user can only eyeball the size and position of the zones. It may be helpful if the numerical value of the zones' size and position can be seen to allow users to create a more precise layout.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

@Clessiah
tracked in https://github.com/microsoft/PowerToys/issues/463


Enforce srtricter integer parsing on encode function

Currently, the encode function in hashids is using parseInt in order to validate that a stringified number is indeed a number before encoding. However, there is a caveat to parseInt, detailed in MDN's documentation:

If parseInt encounters a character that is not a numeral in the specified radix, it ignores it and all succeeding characters and returns the integer value parsed up to that point.

If an API consumer were to pass hashids.encode('B6'), this would result in a proper result of '' since the API specifies returning an empty string if an integer is not received.
However, if the consumer were to pass hashids.encode('6B'), the parseInt function would parse this as 6 and ignore the succeeding characters. This would allow the encode function to continue with the encode, even though the function was passed a bad value.
I've updated the tests to demonstrate the issue. To address the bug, I added a stricter filterInt function. This function verifies that the number being passed is indeed an integer before executing parseInt. I pulled filterInt from MDN's documentation on parseInt  and modified it to be a bit cleaner.
Thanks to @juliancoleman for pairing on me to find/implement a fix for this bug.

Coverage remained the same at 100.0% when pulling 00368599b20dd585a8b13ac8cd2cc55ce2920943 on jadengore:feature/encode-validation-integer-parsing into b8b0a6ef42fc5eb6a896be7abda91221504a89c7 on ivanakimov:master.

Awesome description & good catch. Thank you @jadengore.


added about page thus fixed issue #32

#32 is solved. added new about page and linked it with nav bar and all other pages. Please add the level as well, it was missing in the issue.

Please resolve the conflicts

Please put on the labels gssoc ext , level and hacktoberfest


How to handle StartLambdaFunctionFailed error, using promises?

I have been using AWS SWF to coordinate lambda tasks. I'm using SWF Error Handling + SWF Promises + Replay Behavior of AWS SWF Java SDK.
SWF Lambda Task + SWF Promise + SWF TryCatch are powerful features, because when Lambda function throws an exception "SWF TryCatch" gives me a way to handle the errors. It works very well!!
Here we have example:

1       new TryCatch() {
2
3       @Override
4       protected void doTry() throws Throwable {
5         Promise promiseLambda =  lambdaClient.scheduleLambdaFunction("transcodeSegment_mock", "");
6
7         finishedWorkflow(promiseLambda);
8       }
9
10       @Override
11       protected void doCatch(
12           Throwable e
13       ) throws Throwable {
14         System.out.println("doCatch *** Error handling routine");
15         System.out.println(e.getMessage());
16         .... error handle code
17       }
18     };

But, I saw a diferente behavior, when SWF has Event Type="StartLambdaFunctionFailed" or Event Type="ScheduleLambdaFunctionFailed", for both cases Catch statement (line 11) is not being called.
Is it normal? How can I handle those types of SWF Events, using only promises?
As you can see in my code, it does not parse Workflow History, I'm using just promises and Replay Behavior. Is possible to handle those errors, without my code parse workflow history?
When Event Type="StartLambdaFunctionFailed" or Event Type="ScheduleLambdaFunctionFailed" happens, workflow never finishes, and I have timeout error.
Thanks

The fix for this is introduced through commit: https://github.com/aws/aws-swf-flow-library/commit/98bfa83cb66da0e9ec08f4dd43ee2b7977f06368
Please look at code in AysncDecider for details: https://github.com/aws/aws-swf-flow-library/blame/master/src/main/java/com/amazonaws/services/simpleworkflow/flow/worker/AsyncDecider.java#L314-L319


[actually an old bug] Gathering can put items in chest below it(with ritual ingredients).

So,there are ritual of Animal Harvest(and no chest near with Gathering ritual):

And items,that ritual gathered:

So what the idea,it NEED to require chest in the same Y level with Pyre for structure(to put in it gathered things).And chest below cannot gather items,only take ritual ingredients.
P.S.As you see,I'm cheking this in alpha 12.
P.S.p.s..Do actually someone made bug report like this?

That was painful to track down. Should be fixed in the next alpha.

Typed that in the wrong issue.


The website admin is not able to disable price translation.

Is your feature request related to a problem? Please describe.
Not all stores want their prices to be translated into different locales, this option allows admin to choose if they want to keep the prices as digits or translate them into the chosen locale.
For English, the price will look like AED 100.00
But if the customer switches to Arabic, it looks like ١٠٠٫٠٠ AED
It is clearly undesirable because no eCommerce store in the middle east wants to show prices like this.
Describe the solution you'd like
Add an option in the channels screen to enable/disable Price translation so that admin can have control over it.
Something like this

Describe alternatives you've considered
Hard code en in packages/Webkul/Core/src/Core.php
at line#662
$formatter = new \NumberFormatter('en' \NumberFormatter::CURRENCY);
Additional context
No response

I have done the required coding for this feature and opened a pull request#7277
Kindly request you to merge it.


Bugfix/dont show red circle when transcribing

Well that was easier than expected 😆
Tagging Riley as he has a mac and this is easiest to see on mac
For some reason it won't let me untag taz so we have a linux tester too 😎
Resolves #92
Resolves #110
(oops I think I made duplicate issues)
Builds on #147 (that PR is now merged)

Just checking I'm understanding properly, is this basically saying if there's no transcription associated with the current project then there isn't anything to save so saving shouldn't be enabled?

Just checking I'm understanding properly, is this basically saying if there's no transcription associated with the current project then there isn't anything to save so saving shouldn't be enabled?

That is correct @kateahyde

See the linked issues this resolves for a description

Thanks for the clarification and for pointing to the issues, I'll be sure to check them properly next time :) @chloebrett


[Beta] Rewrite Quick Start

The existing Quick Start is more of a "site overview". There was a bunch of negative feedback on it and it clearly didn't work out. This is a clean rewrite. The goal is to cover the basics but without distracting the reader with links or too many caveats. It needs to cover enough to prepare you to read Thinking in React, but be short enough that you wouldn't bail on it right away.
I hope this one will work.
Page preview: Quick Start

Content
A big improvement overall in my opinion, much easier for someone new to read and understand. I think it's still missing something though: the "light bulb" moment that shows why React is so useful and how it all fits together. "Why" is everyone using this library, basically. This page sort of just lists all React's features and how to use them, but not why you should be doing this. Maybe this goes in a different section?
Others have given good feedback already for the rest. Though, I noticed in the "Displaying data" section, the Sandpack example after "You can put any dynamic expressions..."  Perhaps show briefly how conditionals change the rendered output?
Styling
This isn't related to the content, so it'd be a separate PR. But I wanted to give high level feedback of "experiencing" the preview that's linked since the experience all fits together.

Line highlighting is odd, it should span the entire code block. It looks like the .sp-stack forces the width to fit the content.
The code editor/Sandpack examples have no proper indication they can be scrolled for devices without a scrollbar by default. I also think the max-height set on it could be higher (or adaptable to the screen height) so you can see more code at once. It feels limiting to be in a tiny window, e.g. to see two components at once, making the examples a bit harder to comprehend.

First of all: great work on updating the quick start. It's easy to read and it's easy to understand the main concepts. I like the section about useState a lot, especially the "evolution" of the count from isolated state to shared state. It's one of the common "real-life" tasks so it's nice to see it covered in the documentation.
A few little notes that came to mind while reading the guide:

as @atomiks already mentioned, the snippet on Displaying data should be either simplified or we'd need to add some visual changes when large class is applied;
for the complete outsider who never touched React, the example of useState feels a bit too magical. So, we call useState, we want to have a state property called x, and it provides us with a function to update a state property with set- prefix. It would be nice to mention somewhere that if count was avocado, we'd have setAvocado instead 😅

It could be neat if the first playground that the user sees was visible without scrolling down. Basically using it as a teaser somehow. Or otherwise just having a picture of the button next to the very first bit of code that you show, just to give real beginner people an instant feel of this is what you can do easily.

I think it's still missing something though: the "light bulb" moment that shows why React is so useful and how it all fits together. "Why" is everyone using this library, basically. This page sort of just lists all React's features and how to use them, but not why you should be doing this. Maybe this goes in a different section?

Maybe I can add something short to the end. I'd like to have a page like this but I'm not sure it's this one.

Others have given good feedback already for the rest. Though, I noticed in the "Displaying data" section, the Sandpack example after "You can put any dynamic expressions..."  Perhaps show briefly how conditionals change the rendered output?

The code is there to make the classes.join(' ') call relevant (and also to answer one of the most common questions about how to do multiple CSS classes). But it's fair this isn't really clear if you don't already understand it. I'll try to move this.

Line highlighting is odd, it should span the entire code block. It looks like the .sp-stack forces the width to fit the content.

As you mentioned, this isn't really relevant to this specific page. I remember fixing this and causing some other issue. But we should probably revisit this at some point. I'd like to have a fix for this.

It feels limiting to be in a tiny window, e.g. to see two components at once, making the examples a bit harder to comprehend.

There's a "Show more" button on each sandbox that expands it. I realize it's not super noticeable but hopefully once the reader sees it's there, this is less of a problem.

So, we call useState, we want to have a state property called x, and it provides us with a function to update a state property with set- prefix. It would be nice to mention somewhere that if count was avocado, we'd have setAvocado instead

👍

It could be neat if the first playground that the user sees was visible without scrolling down. Basically using it as a teaser somehow

That's what the existing quick start does. I've heard feedback that the example isn't helping and makes people feel overloaded. At this point I'm not sure which feedback to take into account, but I wanted to try the inverse, and then maybe we'll find some middle ground.

I love the new QuickStart! I also agree with the feedback already given. I'd like to add a few nits from a potential beginner's perspective ✨


Proposal: Modular standard library and crates.io improvements

Rust has a small standard library because they don't want to add something bad to the standard library because if they do they won't fix or remove it because it would break compatibility. I've been thinking of a solution and this is what I've come up with:
Before I explain my modular standard library idea I need to explain my crates.io improvements:

There will be crate titles for crates with the default title being unverified. If a crate is verified it means there's nothing malicious about it. If a crate is official it means it's maintained by the official Rust team. If a crate is unverified it means the crate isn't gaurenteed to be safe.
Precompiled crates for efficiency.
Crate groups, let's say somebody wants to add a ton of packages as dependencies for their project but they don't want all of it cluttering their cargo.toml. You'd go onto crates.io and create a crate group with all the specified crates. Multiple versions of these groups can be made like with normal creates (so 1.0.0, 1.2.4, 2.0.5, etc).

Now with all that out of the way this is my proposal which would allow the Rust standard library to be big with the freedom to make breaking changes without breaking compatibility:
Make every little part of the standard library a crate and have the standard library be a crate group that's added by default. This way there can be different versions of every module that's part of the standard library so breaking changes can be made and corrected without breaking anything because developers could simply use an older version of that specific crate from the standard library.

they do they won't fix or remove it because it would break compatibility

It is not just that, adding more things make std maintainers life harder.
You have more works to do and take care of.
It's mostly boiled down to resources. If Rust org has more resources (including people),
they could do a few things mentioned.
In short, these ideas has been proposed in some posts/media, but never have
enough resources to do.

If we can't even ship pre-built quote and syn to keep proc-macro build times down, I don't know how we'll ever manage to ship pre-built anything else to keep build times down.

they do they won't fix or remove it because it would break compatibility

It is not just that, adding more things make std maintainers life harder.
You have more works to do and take care of.
It's mostly boiled down to resources. If Rust org has more resources (including people),
they could do a few things mentioned.
In short, these ideas has been proposed in some posts/media, but never have
enough resources to do.

Even if the team doesn't have the resources for a big standard library these changes should still be made because mistakes can still appear in a small standard library and this system is the best system to correct them.

If we can't even ship pre-built quote and syn to keep proc-macro build times down, I don't know how we'll ever manage to ship pre-built anything else to keep build times down.

Aw that sucks to hear, well scratch what I said about precompiled crates then.

these changes should still be made because mistakes can still appear in a small standard library and this system is the best system to correct them

I don't want to be discourage. But there are things easier said than done.
Who would maintain those crates? Who review them? What about qualities? Does it need to be built/passed CI?
Who implement initial features to classify crates/verify it and maintain it when it has issues?

these changes should still be made because mistakes can still appear in a small standard library and this system is the best system to correct them

I don't want to be discourage. But there are things easier said than done.
Who would maintain those crates? Who review them? What about qualities? Do they need to be built/passed CI?
Who implement initial features to classify crates/verify it and maintain it when it has issues?

The whole idea is to make the standard library modular, it's a different structure but the same people who maintain the standard library would maintain the standard library.
I'm not sure who would implement this new crate system but this is all open source so I assume the Rust community would contribute to this if it gains enough support.
Regarding verifying crates, a review team for that would need to be made which would also probably be ran by the community if it gains enough support.

The whole idea is to make the standard library modular, it's a different structure but the same people who maintain the standard library would maintain the standard library.

And that's the problem. They don't have bandwidth, but they want to keep std high quality.
They can only attend FCPs to decide what going to stable.
I know some members in std lib team don't want to be assigned for reviewing PRs.
Some are busy in working group, for example inline-asm, errror-handling, simd, etc...
Some at works.
Also, not all are expert in every domains, like GUI or crypto. We don't have people for that.

The whole idea is to make the standard library modular, it's a different structure but the same people who maintain the standard library would maintain the standard library.

And that's the problem. They don't have bandwidth, but they want to keep std high quality.
They can only attend FCPs to decide what going to stable.
I know some members in std lib team don't want to be assigned for reviewing PRs.
Some are busy in working group, for example inline-asm, errror-handling, simd, etc...
Some at works.
Also, not all are expert in every domains, like GUI or crypto. We don't have people for that.

If you have an actual critique about my proposal I'd love to hear it but all I've heard you say about it is that it won't work because nobody is probably going to work on it which seems like an irrelevant point to bring up because things like the support something has, the resources there are to implement it, and the people who are willing to contribute can change. I'm not saying this needs to be implemented right now, I'm just saying it should be implemented eventually. Is there anything you don't like about the idea itself or is weather it's feasible your only concern?

How are you supposed to define your minimum rust version policy? Like some parts require version XXX some other YYY?
No thanks.

How are you supposed to define your minimum rust version policy? Like some parts require version XXX some other YYY?
No thanks.

Well every crate from the standard library would depend on whatever it needs to work, so if a specific version of x needs version 2 of y and version 3 of z to run it would use that because these dependencies would be specified for that crate (Just like it is with any other crate).

This is a classic version / dependency problem. The original Java libraries years ago shipped with the JDK because there really was no other means at the time to have a bundle of verified, but dependent code - In 1994 Java was already becoming a popular language and the internet as we know it was just becoming public. Did you know the core Java UI libraries ship by default along with all the backend libraries (up until java 9)? What interest does a webserver have in desktop UI widgets?
This all resulted in version release cycles in the order of 5-6 years with dozens of features and hundreds of bug fixes. Basically, a monolith.
A few years ago Java finally released a modular system for all dependencies and they have been slicing off core libraries into separate modules ever since. In addition, the core maintainers finally realized that a 6+ year release cycle was making Java look like an irrelevant dinosaur. So, they open-sourced it and it's on a 6 month release cycle.
While platforms like .NET core and nodejs come stripped down, this has the upside of relieving maintainers from improving anything but core language features. The flip side is, of course, to some degree, it becomes the wild-wild-west when trying to get basic things done because you have to find a dependent library to do the job.
As for complaints of "but who would maintain it?!" and "official" packages: Making dependencies 100% modular but then shipping with a default bundle in no way impedes support ability - it in fact, enhances it. People are always going to take the defaults unless they have a compelling reason not to (laziness will win everytime).
As for the complaints about which version goes with what: That's called software development; you should always test when any dependency (OS, processor, etc.) changes. This is no different. I like the idea of bundling (internally at Amazon, they do exactly this and it's called a "Version Set").
I would suggest that research be done on how the dozens of other languages around the world have managed dependencies and what issues they have faced - this isn't even a remotely new problem.


Enum Symbols should have a method to know the original enum name

Description:
If an enum is defined with expression values, enum elements' type signature would be the expression. However, this should instead be the original enum name. Or, there should be a way to know the original enum name.
Steps to reproduce:
enum Language {EN="english", TA="tamil", SI="sinhala"}
// Type signature of variable would be `english` but should instead be `EN`.
// Or there should be a way to get the `EN` symbol name.
EN variable = "english"

Related Issues (optional):
#28037

I believe this is the same as #27190

Closing since this is a duplicate


Invariant Violation: requireNativeComponent: "RNDateTimePicker" was not found in the UIManager

When i run "react-native run-ios"! the component seems to work just fine!
But when i run "detox test", i got this error:
Invariant Violation: requireNativeComponent: "RNDateTimePicker" was not found in the UIManager
Is this plugin not usable with detox?

+1

hello, this is most likely problem with linking the module. I'm closing this because there is no runnable reproduction.
please create a new issue with repro and we'll be happy to review it!


version: post-release bump

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

Coverage remained the same at 100.0% when pulling b8b3a34e92ea576d70fdbc6ad1a322037d340106 on jirikuncar:version-bump into fca66ddc485f6a835beb2f447584fa6709b38522 on inveniosoftware:master.


Name elements that indicate taxon is a virus

It looks like names with these elements are not yet recognized as viruses, so capitalized words are stripped from the canonical form:
NPV, e.g., Papilio polyxenes NPV: http://eol.org/pages/41592578
RNA, e.g., Alternaria zinniae dsRNA element: http://eol.org/pages/11611917
virophage, e.g., Organic Lake virophage: http://eol.org/pages/20868817
satellites, e.g., Double-stranded RNA satellites: http://eol.org/pages/11603787
satellite, e.g., Whitefly VEM satellite: http://eol.org/pages/20858522
betasatellite, e.g., Tomato leaf curl China betasatellite: http://eol.org/pages/11603870
alphasatellite, e.g., Ageratum yellow vein Singapore alphasatellite: http://eol.org/pages/39738381
particle, e.g., Mouse Intracisternal A-particle: http://eol.org/pages/11609198
subgroup, e.g., Subgroup B: http://eol.org/pages/11623168 -- This is probably not limited to viruses, but it's very unlikely that any name that has this string in it will have author information associated with it.

Thanks Katja, I will look at these words through GN names to see if i get some unexpected consequences (unlikely) and everything that is safe will go to the next version of parser

RNA happens in surrogate names:
|Candida albicans RNA_12C-1                                          |
| Candida albicans RNA_12C-2                                          |
| Candida albicans RNA_12C-3                                          |
| Candida albicans RNA_CTR0-1                                         |
| Candida albicans RNA_CTR0-2                                         |
| Candida albicans RNA_CTR0-3                                         |
| Candida albicans RNA_GC75-1                                         |
| Candida albicans RNA_GC75-2                                         |
| Candida albicans RNA_GC75-3                                         |
| Candida albicans RNA_SC5314-1                                       |
| Candida albicans RNA_SC5314-2                                       |
| Candida albicans RNA_SC5314-3                                       |
| Candida tropicalis RNA_Ct1-1                                        |
| Candida tropicalis RNA_Ct1-2                                        |
| Candida tropicalis RNA_Ct2-1                                        |
| Candida tropicalis RNA_Ct2-2                                        |
| Candida tropicalis RNA_Ct3-1                                        |
| Candida tropicalis RNA_Ct3-2

I am not sure what to do with subgroup. Here are some examples:
xLevivirus subgroup I
plant rhabdoviruses subgroup B
Zelotes mayanus subgroup
Teuchophorus notabilis subgroup Meuffels & Grootaert 2004
Subgroup I Geminivirus
Sericania mimica subgroup Kobayashi & Fujioka 2008
Pipistrellus (Hypsugo) imbricatus subgroup

Everything except subgroups is covered in v3.1.10


Full JSON response for debugging?

I couldn't find any information in the documentation regarding debug options, specifically the ability to print out the full JSON response when making API calls. Is there a way to enable such debugging?

This seems good to have.

Now, at version 4.1.4, you can log responses from async methods with this.
update the package and try it.

That was fast! :+1:


Request options from the client when the server starts

Fixes https://github.com/dotnet/razor/issues/9224 by honouring the razor.format.enable setting

Whoops, missed your comment Andrew, sorry.
The only way to test would be by using mocks and verify that when the OnInitializedAsync method is called, it calls to make an LSP request, but that doesn't seem like much value to me. Obviously I manually tested in VS Code :)


Implement muon.crypto.encryptString/decryptString API

master key is same as built-in password manager/cookies
Using base64 to encode non ASCII characters
fix https://github.com/brave/browser-laptop/issues/10705
Auditors: @bridiver, @diracdeltas, @bbondy

@bsclifton mentioned this might cause manually session backup failed because you can only encrypt/decrypt value on the same machine.
What do you think @diracdeltas ?

saved password and cookies applied to the same rules ^^^
so you can just copy those file to different machine

for safety, i think that muon.crypto.encryptString/decryptString should throw an error or return nothing if OSCrypt EncryptString/DecryptString are not available. In most cases, if a string cannot be encrypted, it is better to save nothing than to save it in plaintext.

wouldn't it be better to just store them in the password manager? That has the added benefit of cross-device sync

we can do that on Mac and Window because password manager stores encrypted password in Login Data sql file but it stores the login entries in keyring

cc @riastradh for review of the underlying chromium crypto code


Porting BoringSSL-OQS Fork Into Envoy

Hi everyone, firstly apologies if this is the wrong place to open a discussion on this.
What I'm Trying To Do
I'm currently working on an open source implementation of a post-quantum enabled service mesh. This effort is in 3 parts:

Nginx-oqs (finished in march of this year)
Envoy (in progress)
Istio (contingent on completion of envoy)

Nginx was fairly straightforward to port the OpenSSL-OQS fork, but Envoy is giving me some trouble. Envoy is incompatible with OpenSSL (there is a team working on fixing this currently), so I had to use the BoringSSL-OQS fork
How I'm Doing it
To update BoringSSL for envoy, specifically the "main-with-bazel" branch must be used:

The last updated Boringssl-OQS main-with-bazel was from 2019, so I forked it and added the siphash.h file needed by Envoy.
A few other modifications I needed to make in the Envoy fork I'm modifying:

Disable jwt-auth
Disable QUIC to side-step Quiche compatibility issues

Envoy successfully builds with my modifications

Here are the commands I used to generate the self-signed CA cert and the server cert as per the instructions on the OpenSSL-OQS page. I have tried them with all combinations of standard/OQS/hybrid for both the CA cert and the server cert
/usr/local/openssl/apps/openssl req -x509 -new -newkey rsa:2048 -keyout root_CA.key -out root_CA.crt -nodes -subj "/CN=oqstest CA" -days 365 -config /usr/local/openssl/apps/openssl.cnf

/usr/local/openssl/apps/openssl req -new -newkey rsa3072_dilithium2 -keyout serverkey.key -out servercsr.csr -nodes -subj "/CN=oqstest server" -config /usr/local/openssl/apps/openssl.cnf

/usr/local/openssl/apps/openssl x509 -req -in servercsr.csr -out servercert.crt -CA root_CA.crt -CAkey root_CA.key -CAcreateserial -days 365

How It's Working: Standard RSA
I can confirm my build works by passing RSA certs and keys generated using the OQS-OpenSSL fork. The HTTPS server successfully performs the TLS handshake, and I am able to reach HTTP upstream.

How It's Not Working 1: "Cannot Load Certificate Chain"
If I pass the (hybrid or OQS) server cert to Envoy, I get this error:

I have tracked it down to this portion of the Envoy source code:

Here is a diagram of the functions and their locations in the Envoy and BoringSSL source code:

How It's Not Working 2: "Unsupported Algorithm"
If I pass the (RSA) root CA cert to Envoy with the (hybrid or OQS) key, I am faced with this error instead

Questions
If anyone is curious and wants to reproduce this, the instructions are on this repo I have set up.
At this point, I feel like there may be something catastrophically important I'm missing about either BoringSSL-OQS, Envoy, or just software development in general.
I would love any and all feedback/advice/thoughts/criticism about why this may be happening, and what I can do to fix this.

Without looking more closely, my first guess is that because you're using a BoringSSL from 2019, it doesn't support one of the default ciphersuites that envoy tries to configure.
Unless you can get this branch of BoringSSL rebased onto a recent release, I think this is probably a dead-end.

@ggreenway yes, that was a big concern of mine when I saw that the only master-with-bazel branch was from 2019.
However, envoy builds completely fine with it, passes the tests (some functionalities are disabled, like jwt-auth, quic, etc), and is able to initialize a TLS server using standard RSA encryption. The certificate and keys for the standard RSA are generated using the Boringssl fork from 2019.
If the outdated BSSL was the issue, wouldn't the standard RSA fail as well?

Without digging in further, I don't know exactly what the issue is. But you've already identified several incompatibilies (jwt, quic, etc). I believe there have been CVEs fixed in BoringSSL since 2019, so I think any path forward using BoringSSL will need a more recent version. I don't think it is worth any time trying to make current Envoy work with old BoringSSL.

@ggreenway That's fair, i appreciate your input on this.
I reached out to the bssl-oqs to discuss an updated master-with-bazel, but I think the easiest solution would be envoy that works with openssl.
Interestingly, the incompatibilities I found were the same ones identified by the envoyproxy team that was working on full openssl integration


Project rename

The project is now known as "Zomis' Games" and any place "Server2" occurs should be changed to "Zomis' Games" or just "Games" or "Server", depending on the context.
Definition of Done: "Server2" does not appear anywhere.

isnt this done?

@GustaMagik The rename on GitHub is done, but there are still many places that refer to "server2". Just looking at the README.md for example.


cmd/compile: ICE: not lowered: v58, ITab PTR64 PTR64

At tip, this package fails to compile with an ICE in SSA:
package p
func f() ([]interface{}, *int) {
    return nil, nil
}
var _ = append(f())

/cc @randall77

go1.2 reports multiple-value f() in single-value context, and doesn't ICE.
go1.4 compiles it successfully (!)
go1.[56] ICEs with cgen_wb of type interface {}
go1.[789] to current ICE with not lowered: ITab PTR64 PTR64
I think go1.2 is correct.  I think if we reported that error correctly, we'd never pass the bad code to the backend, and then we wouldn't ICE.

go1.4 generated code is "correct", in that it does convert the *int to an interface{} and appends it to a []interface{}.

Hmmm, looks like append of the result of a multi-return function does generally work.
Maybe go1.4 is correct?

Oh, yes, the code should compile correctly, like it did with go1.4.
go/types and gccgo accept the code. (Sorry, I should have mentioned that in the original report.)

Looking at cmd/compile's -W output, I think maybe this is an issue in walk instead. Currently we're rewriting append(f()) into something like:
t0, t1 := f()
append([]interface{}(t0), t1)

I think what we actually mean to do is rewrite it to:
t0, t1 := f()
append(t0, interface{}(t1))

Still happening with go version devel +9761a162f0 Thu Mar 29 16:37:26 2018 +0000 linux/amd64

This has been broken for a while, so punting to 1.12, but marking as a release-blocker for that release.

Looks like there is a missing CONVIFACE here.
Before order:
.   AS l(7) tc(1)
.   .   NAME-_ a(true) l(7) x(0) tc(1) SLICE-[]interface {}
.   .   APPEND l(7) tc(1) SLICE-[]interface {}
.   .   APPEND-list
.   .   .   CALLFUNC l(7) tc(1) STRUCT-([]interface {}, *int)
.   .   .   .   NAME-p.f a(true) l(3) x(0) class(PFUNC) tc(1) used FUNC-func() ([]interface {}, *int)

After order:
.   AS2FUNC l(7) tc(1)
.   AS2FUNC-list
.   .   NAME-p..autotmp_2 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used SLICE-[]interface {}

.   .   NAME-p..autotmp_3 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used PTR-*int
.   AS2FUNC-rlist
.   .   CALLFUNC l(7) tc(1) STRUCT-([]interface {}, *int)
.   .   .   NAME-p.f a(true) l(3) x(0) class(PFUNC) tc(1) used FUNC-func() ([]interface {}, *int)

.   AS2 l(7) tc(1)
.   AS2-list
.   .   NAME-p..autotmp_0 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used SLICE-[]interface {}

.   .   NAME-p..autotmp_1 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used PTR-*int
.   AS2-rlist
.   .   NAME-p..autotmp_2 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used SLICE-[]interface {}

.   .   NAME-p..autotmp_3 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used PTR-*int
.   AS l(7) tc(1)
.   .   NAME-_ a(true) l(7) x(0) tc(1) SLICE-[]interface {}
.   .   APPEND l(7) tc(1) SLICE-[]interface {}
.   .   APPEND-list
.   .   .   NAME-p..autotmp_0 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used SLICE-[]interface {}
.   .   .   NAME-p..autotmp_1 a(true) l(7) x(0) class(PAUTO) esc(N) tc(1) assigned used PTR-*int

Nowhere is there a CONVIFACE to convert the second append arugment from *int to interface{}.
Normally the typecheck pass, even before order, inserts CONVIFACE and the like ops to convert function arguments to the right types. We just don't do that here.
I think copyRet in order.go needs to use temporaries corresponding to the outer function's required argument types instead of the inner function's result types. Then the typecheck call it does should insert the conversions required.


docs: remove cncf label on homepage

Thanks for contributing! Please ensure your pull request adheres to the following guidelines:

[x] All commits contain a well written commit message and are signed-off (see Submitting a pull request).
[x] All code is covered by unit and/or end-to-end tests where feasible.
[x] All generated files are updated if needed (see Making changes).
[x] Provide a title or release-note blurb suitable for the release notes (see guidelines).
[x] Update documentation and write an upgrade note if needed (see guidelines).
[x] Are you a user of Tetragon? Please add yourself to the Users doc in the Cilium repository.

Removes the  CNCF label on the homepage for reasons we've discussed.

I think we should keep this, we just also need to mention that Tetragon is a subproject under Cilium like the website said before the update

for reasons we've discussed

would love to have more context on that discussion 😄

The reasons being that right now it looks like Tetragon is a stand alone CNCF project while it is actually under Cilium which is the overarching CNCF project

Yes. A slight redesign from PP would fix this

@mtardy PP will handle the update to this. I'll close this if that's fine with you.


Fix the buffer::tests::test_vec_reallocate test

The test is ignored since it has been flaky in CI see this comment for details.

Duplicate of #4318


Render quote characters outside of the text pills

Pull Request Description

Close #9161

UI is tentative - but I think white instead of faded makes sense here, otherwise the quotes will be too hard to see

Important Notes
None
Screenshots

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Closing in favor of @Frizi's solution which will be a more proper solution