Migration to 9.1

Well. Everything worked fine until updating to 9.1.
How can I mix per user handler and inline queries in single class?
This is my old logic:
class UserTracker(telepot.helper.UserHandler)
...
    def on_message(self, msg):
        flavor = telepot.flavor(msg)
        print flavor
        if flavor == 'inline_query':
        elif flavor == 'chat':
        elif flavor == 'callback_query':
...
db_connection = psycopg2.connect(DB_NAME)
bot = telepot.DelegatorBot(TOKEN, [
    (per_from_id(), create_open(UserTracker, db_connection, timeout=20)),
])

I updated my code for new changes:
class UserTracker(telepot.helper.ChatHandler, telepot.helper.AnswererMixin):
    def __init__(self, *args, **kwargs):
        super(UserTracker, self).__init__(*args, **kwargs)

bot = telepot.DelegatorBot(TOKEN, [
    pave_event_space()(
        per_chat_id(), create_open, UserTracker, timeout=50
    ),
])

But inline doesn't work.
I have got flavor with '_idle' value and bot crashes
raise exception.EventNotFound(event)
EventNotFound: Event(timestamp=1473624346.643259, data={'_idle': {'seconds': 50, 'source': {'id': 110821612, 'space': 1}}})

Two questions:

Which inline do you mean, inline query or inline keyboard?

How often does EventNotFount happen?

Inline query.
telepot.flavor(msg) == 'inline_query'
EventNotFount happens after inline queries from groups. For example:
I send message to bot and it handle it. After this I send inline query from another chat to bot. I haven't got inline_query from telepot.flavor(msg). After this I send message from simple chat and telepot crashes with EventNotFount

Your intention calls for per_from_id() and UserHandler. In other words:
class UserTracker(telepot.helper.UserHandler, telepot.helper.AnswererMixin):
   blah blah blah

bot = telepot.DelegatorBot(TOKEN, [
    pave_event_space()(
        per_from_id(), create_open, UserTracker, timeout=50
    ),
])

For more details, please refer to my answer in #155
As for EventNotFound, I think it's related to #140. I suspect it's a bug in telepot, but have not time to check it out.

Should I use different implementation for handling inline and chat queries?
bot = telepot.aio.DelegatorBot(TOKEN, [
    pave_event_space()(
        per_inline_from_id(), create_open, telepot.helper.InlineUserHandlerSubclass, timeout=10),

    pave_event_space()(
        per_from_id(), create_open, telepot.helper.UserHandlerSubclass, timeout=10),
])

Well. I fix my code for inline queries. It works! But I don't understand roots of EventNotFound  problem. It is very often exception.

@nickoala can I change text of sent messages with InlineKeyboardButton? I can't find solution for this.

What do you mean by "change text of sent messages with InlineKeyboardButton"?

I try this in callback query:
query_id, from_id, query_data = telepot.glance(msg, flavor='callback_query')
message = msg['message']
msg_id = message['message_id']
bot.editMessageText((message['chat']['id'], msg_id), 'Test message')

But it causes error:
TelegramError: (u'Bad Request: Wrong inline message identifier specified', 400, {u'error_code': 400, u'ok': False, u'description': u'Bad Request: Wrong inline message identifier specified'})

I tried the same thing, and it worked for me. The message identifier (chat_id, message_id) is correct.
A quicker way to obtain the message identifier is this:
msg_idf = telepot.message_identifier(msg['message'])
bot.editMessageText(msg_idf, 'NEW MESSAGE HERE')

This should be equivalent to what you did, so I still have no idea why it didn't work for you. It worked for me both ways.


master_index: fix inconsistent length blob length in test

Two blobs with the same hash must always have the same content length.

What does this PR change? What problem does it solve?
Fixes https://github.com/restic/restic/issues/4448.

Was the change previously discussed in an issue or on the forum?

Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[x] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

LGTM.


RFE: Allow setting environment variables via operator

For quite a few cases the option to supply environment variables via operator would be really useful. Especially for corporate proxies, but also secrets.
I suggest something simple in the form of:
environment:
  - name: VAR
    value: VAL
  - name: VAR2
    configmapRef:
      name: public
      key: key
  - name: VAR3
    secretKeyRef:
      name: secret
      key: key

Which, while verbose, should translate well to the actual deployments. I could imagine this as global for all deployments or service specific.

@lhw You envision these for the operator container or the actual argocd components?

Hey. Thanks for your work on this project.
I meant these mostly for the ArgoCD components themselves. I skimmed the operator source code and couldn't find any way to add generic environment variables to the resulting deployments. I based my suggestion on the vault-operator here.

I could see this being useful even for making values available to the build environment while using config-management-plugins, especially if you happen to also be using your own custom build of the repo-server image.
@lhw In your example above, you mention being able to read these values from secrets/configmaps. I would assume that the user would be responsible for creating those outside of the scope of the operator, but is that how you're also imagining that this would work?

Separating the secrets from the deployment is a good practice in my opinion. The way we add secrets to the deployment namespaces in most of our cases is using bitnamis sealedsecrets or godaddys external-secrets. This way no secret is found anywhere in a non-encrypted form outside the cluster. And inside the cluster we can easily limit the access to these secrets as well.
Syntax-wise this should translate well to the deployment itself, being a basically 1:1 copy.

Being able to use a separate secret for dex client secrets or even external TLS would be great addition, or argocd root password from secret even


Fallbacks for context-vars in cccid?

Currently I have a directory containing a few .ccc files, like /.../grades/neutral.ccc /.../grades/beauty.ccc
I refer to these in the config as
- !<Look>
  name: beauty
  process_space: jplog
  transform: !<FileTransform> {src: "beauty.ccc", cccid: "${SEQ}/${SHOT}"}

This works fine, but errors if the cccid doesn't exist
Upon typing this I realise that storing the grades as .cc and having multiple paths on the search_path is a much better idea (as described on #201), since it allows for things such as a default sequence grade, and is possibly faster since it doesn't have to load a large XML file just to get one grade
..but I'm curious if there's any way to achieve something similar with cccid's?

Currently I cant think of a similar way to achieve it with ccc files.  But seeing as how .ccc files are what one usually gets from the client (.cc files are an OCIO convention / invention) maybe we should figure out a way to make them work?

Is this successfully addressed in the closed #346 ?

@dbr pinging this again

Not sure it was that specific pull request, but this problem seems to have been fixed in e48cce1653c45525652a3c69ab469d181e40467a (which is part of v1.0.9) \o/


Revert "Use working region/subscription for search deployments"

Reverts Azure/azure-sdk-for-java#25175
The above PR was a temporary workaround fix for an RP deletion metadata issue. Checking to see if it is resolved now.

/azp run java - search - tests

/azp run java - search - tests


MBT support SBOM Generation

new file:   internal/artifacts/sbom.go
modified:   cmd/cmd.go
modified:   cmd/init.go
modified:   configs/builder_type_cfg.yaml
modified:   internal/archive/fsops.go
modified:   internal/archive/mta_location.go
modified:   internal/artifacts/artifacts_msg.go
modified:   internal/artifacts/module_arch.go
modified:   internal/artifacts/project.go
modified:   internal/artifacts/project_test.go
modified:   internal/artifacts/sbom.go
modified:   internal/buildops/modules_deps.go
modified:   internal/commands/builder_type_cfg.go
modified:   internal/commands/commands.go
modified:   internal/commands/commands_msg.go
modified:   internal/commands/module_type_cfg.go
modified:   internal/conttype/content_type_cfg.go
modified:   internal/platform/platform_cfg.go
modified:   internal/tpl/base_args.go
modified:   internal/tpl/base_args.txt
modified:   internal/tpl/base_post.go
modified:   internal/tpl/base_post.txt
modified:   internal/tpl/base_pre_default.go
modified:   internal/tpl/base_pre_verbose.go
modified:   internal/tpl/make_default.go
modified:   internal/tpl/make_verbose.go
modified:   internal/tpl/manifest.go
modified:   internal/version/version_cfg.go
modified:   package-lock.json
modified:   package.json

Before submitting a pull request, please ensure the following:
Description
Please explain the changes you made.
Add a link to the design (if applicable).
Checklist

[ ] Code compiles correctly
[ ] Relevant tests were added (unit / contract / integration)
[ ] Relevant logs were added
[ ] Formatting and linting run locally successfully
[ ] All tests pass
[ ] UA review
[ ] Design is documented
[ ] Extended the README / documentation, if necessary
[ ] Open source is approved

Close this PR, a new PR for SBom generation is https://github.com/SAP/cloud-mta-build-tool/pull/1046


On 0.73.1 service google_assistant.request_sync stop working

Home Assistant release with the issue:
Home Assistant 0.73.1
Last working Home Assistant release (if known):
Home Assistant 0.72.1
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian GNU/Linux 9 \n \l 4.14.52-v7+
Component/platform:
google_assistant
Description of problem:
after update from 0.72.1 to 0.73.1 the service "google_assistant.request_sync" stop working
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
nothing changed
Traceback (if applicable):
Additional information:
error:
Jul 13 21:37:00 rasp-server hass[12796]: 2018-07-13 21:37:00 ERROR (MainThread) [homeassistant.components.google_assistant] request_sync request failed: 404 b'{\n  "error": {\n    "code": 404,\n    "message": "Requested entity was not found.",\n    "status": "NOT_FOUND"\n  }\n}\n'

Same here with 0.74.2:
2018-08-02 16:36:36 ERROR (MainThread) [homeassistant.components.google_assistant] request_sync request failed: 404 b'{\n  "error": {\n    "code": 404,\n    "message": "Requested entity was not found.",\n    "status": "NOT_FOUND"\n  }\n}\n'
previous version is working. No change in the config file.

This seems to work fine in 0.76.2.
I got a "Request contains an invalid argument" even though this worked fine before. I've removed the integration and added it back again, but first I had to start the simulation again on the google actions console, since my test-app was gone in the list.
Check this doc to be sure: https://www.home-assistant.io/components/google_assistant/#troubleshooting-the-request_sync-service

I'm getting this on 0.80.3. My existing setup already had identical project ids, but for good measure i recreated everything from scratch. Still getting Requested entity was not found. Something is amiss here.

Same here on 0.81.6

This issue is getting pretty stale, are you still having this problem in 84.latest?

Still getting it on 0.84.6

And to confirm, you have an api key set in the config and have the correct account configured on the google side?

Yes, everything is setup correctly, checked it a couple of times

Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks!

Still present, but with a different message in 0.90.1:

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/google_assistant/__init__.py", line 75, in request_sync_service_handler
    res.raise_for_status()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 942, in raise_for_status
    headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
    connection.context(msg))
  File "/usr/src/app/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/src/app/homeassistant/components/google_assistant/__init__.py", line 77, in request_sync_service_handler
    body = await res.read()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 969, in read
    self._body = await self.content.read()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/streams.py", line 335, in read
    raise self._exception
aiohttp.client_exceptions.ClientConnectionError: Connection closed

Same for me when i try a google_assistant.request_sync
2019-03-25 22:20:55 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection.139871210080016] Connection closed
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/google_assistant/__init__.py", line 75, in request_sync_service_handler
    res.raise_for_status()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 942, in raise_for_status
    headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
    connection.context(msg))
  File "/usr/src/app/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/src/app/homeassistant/components/google_assistant/__init__.py", line 77, in request_sync_service_handler
    body = await res.read()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 969, in read
    self._body = await self.content.read()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/streams.py", line 335, in read
    raise self._exception
aiohttp.client_exceptions.ClientConnectionError: Connection closed

Same problem here...
Could it be anything related to an old env-setup? I used the old guide back then, and updated to the latest method months back. I'm able to control everything as i'm use to, but sadly can't update the devices...
Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/google_assistant/__init__.py", line 75, in request_sync_service_handler
    res.raise_for_status()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 942, in raise_for_status
    headers=self.headers)
aiohttp.client_exceptions.ClientResponseError: 404, message='Not Found'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/app/homeassistant/components/websocket_api/commands.py", line 122, in handle_call_service
    connection.context(msg))
  File "/usr/src/app/homeassistant/core.py", line 1138, in async_call
    self._execute_service(handler, service_call))
  File "/usr/src/app/homeassistant/core.py", line 1160, in _execute_service
    await handler.func(service_call)
  File "/usr/src/app/homeassistant/components/google_assistant/__init__.py", line 77, in request_sync_service_handler
    body = await res.read()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/client_reqrep.py", line 969, in read
    self._body = await self.content.read()
  File "/usr/local/lib/python3.7/site-packages/aiohttp/streams.py", line 335, in read
    raise self._exception
aiohttp.client_exceptions.ClientConnectionError: Connection closed

I see this from time to time, and can fix this by starting the test again in the Google cloud Console. I assume google stops the test after a time. You might need to remove the integration from the Google home app and re-add it, but the last time, this wasn't needed.

I just tried to remove everything, and set it back up. However, i get the same error :(...


Please enhance the new coordination server to use tasks instead of child_process on iOS

Per thaliproject/Thali_CordovaPlugin#1228 we are going to run each test file in its own child_process on desktop and in Android in order not to overly stress JXcore. But child_process doesn't work on iOS so we can't run our tests there with that function. However JXcore does support a task API that should (famous last words) work on iOS. So we need to switch to that API when we are on iOS.

Not a workable idea given the problems we have seen with the task api.


请问楼主断点续传（上传），是怎么使用的喃？

@YXMao Did a PR for that.
https://github.com/DeveloperLx/LxFTPRequest/pull/17

I just merged it. Thank u @Double-Dude


SyntaxError: invalid syntax

I am getting this error, Python 3.8

What is the error message you are getting? It would be helpful to see the error message to understand what might be causing the issue. Additionally, providing more context such as the code you are running and any recent changes you made to your system would also be helpful in troubleshooting the issue.

It wasn't related to Replicate, was related to UUID lib I was using. Fixed now.


Move handleNodeTags from EncodingManager to AbstractFlagEncoder

Currently we do:
encoder.handleWayTags()
encodingManager.handleNodeTags() // sets access to false if encoder.isBarrier() == true)
encoder.applyWayTags()

In #2469 applyWayTags should go into handleWayTags so right now this would mean it would run before handleNodeTags. But first I think we should move handleNodeTags to the encoder (this PR), because the encoders should handle the access flags directly (not indirectly via isBarrier as we do now). I therefore moved the code that blocks barriers into a new handleNodeTags method in AbstractFlagEncoder and this method is called in encodingManager.handleWayTags now.
Later I'd like to go further and push this code down into the single flag encoders such that everything related to the access flags will be in one place per encoder (and we can make this just a TagParser for access) at some point.

Btw for #2469 we can probably also just change the order of handleNodeTags and applyWayTags, because (at least in our code) applyWayTags uses the accessEnc, but since the node tags are only used for barrier nodes it won't affect the elevation-related things we do in applyWayTags.

:+1:
Should we handle way and node tags in a single method (my preference too) or use e.g. a separate NodeTagParser with a separate method?
But as we use EncodedValues per edge (and have no intention anymore to introduce them for nodes) we should probably convert all tags into them using a single method only.

Should we handle way and node tags in a single method (my preference too) or use e.g. a separate NodeTagParser with a separate method?

I think the node tags along a way (like railway crossings) are just another type of information about a way that could be considered when writing the (edge) encoded values. So we would just pass this information to handleWayTags. Or, like we currently do for barrier, we create an artificial edge and then the node tags are again just a property of this edge again.
The only other case I can think of are node tags that shall be interpreted as turn costs (like traffic lights at junctions), but this will be treated differently and is for another issue.

But as we use EncodedValues per edge (and have no intention anymore to introduce them for nodes) we should probably convert all tags into them using a single method only.

Yes, I don't think something like encoded values for nodes is needed, and it would not be considered by the routing algorithms anyway. Like I said, the only thing we could do is using node tags to set turn costs.

Also at some point we should probably separate our internal/artificial way tags from the actual OSM tags, c.f. this discussion: https://github.com/graphhopper/graphhopper/pull/2457/files#r746357392


Markup fixes

Add code-block annotations for the YAML and fix the numbered lists.

Actually nevermind I got it


Booting Bare Metal

If I was wanting to boot this on a bare metal machine for testing security and performance (no network stack needed), how would you recommend going about it?

After building a machine image you will need to attach GRUB to it so that it can boot anywhere. I have a repo that used to do this: https://github.com/fwsGonzo/physboot But I haven't updated it in a while, so maybe all the scripts won't work, but the important thing is just to be able to call grub-mkrescue properly.
LOCAL_DISK=temp_disk
SERVICE=/path/to/service.elf

# create grub.iso
mkdir -p $LOCAL_DISK/boot/grub
cp $SERVICE $LOCAL_DISK/boot/service
cp grub.cfg $LOCAL_DISK/boot/grub
echo "=>"
grub-mkrescue -d /usr/lib/grub/i386-pc -o grub.iso $LOCAL_DISK
echo "grub.iso constructed"

Hope that helps! 👍

After building a machine image you will need to attach GRUB to it so that it can boot anywhere. I have a repo that used to do this: https://github.com/fwsGonzo/physboot But I haven't updated it in a while, so maybe all the scripts won't work, but the important thing is just to be able to call grub-mkrescue properly.
LOCAL_DISK=temp_disk
SERVICE=/path/to/service.elf

# create grub.iso
mkdir -p $LOCAL_DISK/boot/grub
cp $SERVICE $LOCAL_DISK/boot/service
cp grub.cfg $LOCAL_DISK/boot/grub
echo "=>"
grub-mkrescue -d /usr/lib/grub/i386-pc -o grub.iso $LOCAL_DISK
echo "grub.iso constructed"

Hope that helps! 👍

I am also having it write to my spare partition (sdb) but when I boot it in grub I get errors.
It's telling me:
"error: Not a regular file
error: you need to load the kernel first"
Could I be pointing to the wrong elf file? (The only elf I get from building the service is .elf.bin)
Any thoughts?
Also, I wanted to thank you for your help that you have given me! I am doing research for one of my classes on this Unikernel and I have had a blast with it!

You won't have to modify grub.cfg, just make sure you are actually creating a grub.iso file, which might require grub-pc-bin and yes, it's probably going to be the elf.bin, as long as the file command says its an ELF file.

You won't have to modify grub.cfg, just make sure you are actually creating a grub.iso file, which might require grub-pc-bin and yes, it's probably going to be the elf.bin, as long as the file command says its an ELF file.

The grub.iso is being created... I just get a black screen with "Grub" in the top left corner..Anything in specific I should look for on the .iso to make sure it is there?

oh right, you will want to add the VGA output driver, as there is no terminal anymore... unless you connect a serial port
add_stdout(myservice vga_output)

oh right, you will want to add the VGA output driver, as there is no terminal anymore... unless you connect a serial port
add_stdout(myservice vga_output)

Just to verify, which file am I going to put that into? I'm not familiar with that command.

Add it to the bottom of your CMakeLists.txt, its not a normal command, its a function we made for IncludeOS that adds a stdout plugin. It's not well-documented at all. Yet :)

Add it to the bottom of your CMakeLists.txt, its not a normal command, its a function we made for IncludeOS that adds a stdout plugin. It's not well-documented at all. Yet :)

Awesome! Will run it soon and let you know if that fixes my issue!
Again, thank you for all your help!

Worked like a charm, thank you!

LOCAL_DISK=temp_disk
SERVICE=/path/to/service.elf

# create grub.iso
mkdir -p $LOCAL_DISK/boot/grub
cp $SERVICE $LOCAL_DISK/boot/service
cp grub.cfg $LOCAL_DISK/boot/grub
echo "=>"
grub-mkrescue -d /usr/lib/grub/i386-pc -o grub.iso $LOCAL_DISK
echo "grub.iso constructed"

Thanks. I build hello_world image by modifying the last line https://github.com/includeos/hello_world/blob/5b95d9a79acde3e2396c25a173dbe1bb39f379d4/CMakeLists.txt#L10 to: os_add_stdout(hello vga_output default_stdout). When I tested the generated grub.iso from the script with qemu: qemu-system-x86_64 -boot d -cdrom grub.iso -m 512 -nographic, it fails to boot the OS/application and opens grub prompt.
same thing happened when tested by flashing the ISO to an SD card and tried booting from device via qmeu from Windows:
#!/usr/bin/env pwsh
C:\> Get-WmiObject Win32_DiskDrive | Where Caption -eq 'SDHC Card'

Partitions : 2
DeviceID   : \\.\PHYSICALDRIVE1
Model      : SDHC Card
Size       :<PHONE_NUMBER>0
Caption    : SDHC Card

$ &"\Program Files\qemu\qemu-system-x86_64.exe" -L "\Program Files\qemu" `
     -drive file=\\.\PhysicalDrive1,format=raw,media=disk -m 512 --no-reboot

followed by

I ultimately wanted to test it on a physical machine with legacy BIOS option. Is there anything missing?

I did create some bootable images for my own computer from this repo: https://github.com/fwsGonzo/physboot
Maybe it can still work for you.

Ops, I was missing grub.cfg. Used this one to make it work: https://github.com/includeos/IncludeOS/blob/99b60c782161f521edd797f789c35158109d9d44/test/kernel/integration/grub/grub.cfg#L1


Note Tab grid prop only applies to vertical menu

Codecov Report

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

@@           Coverage Diff           @@
##           master    #3957   +/-   ##
=======================================
  Coverage   99.84%   99.84%
=======================================
  Files         178      178
  Lines        3150     3150
=======================================
  Hits         3145     3145
  Misses          5        5

Impacted Files
Coverage Δ

src/modules/Tab/Tab.js
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 2dbab6b...fdcda3d. Read the comment docs.


Rancher Logging misconfigured project Endpoint causes cluster logging crash loop

This affects rancher 2.2.6.
If you set fluentd in the project logging configuration and give it an invalid endpoint (ex: foo:123) then the entire rancher-fluentd loggers (every instance on each node)  would go into a crash loop. They will complain upon starting that the endpoint doesn't exist and crash. This causes all logging to halt on the entire cluster.
Example log:
2019-08-06 17:56:38 +0000 [info]: adding forwarding server 'ooga.booga:80' host="ooga.booga.123" port=80 weight=100 plugin_id="object:3fa3b5b1d1ac"
/var/lib/gems/2.3.0/gems/fluentd-1.1.3/lib/fluent/plugin/out_forward.rb:706:in `getaddrinfo': getaddrinfo: Name or service not known (SocketError)
When you set an invalid SPLUNK HEC endpoint, it will complain that it cannot flush the buffer but it won't go into a crash loop.
Now this is expected behavior in a misconfigured project. However, this is affecting the entire cluster logging and killing logging for all the users and projects.
What kind of request is this (question/bug/enhancement/feature request):
Can we please segregate fluentd endpoint failures per project and not make it affect the entire cluster?
Steps to reproduce (least amount of steps as possible):

Go to Rancher Project logging page
Choose Fluentd
Give it an invalid endpoint Ex:  blah:123

Result:
Watch the System Rancher fluentd instances fail and enter a crash loop causing clusterwide logging failures.
Other details that may be helpful:
This does NOT happen with a misconfigured Splunk HEC (I haven't tested other endpoints).
Environment information

Rancher version 2.2.6
Installation option: HA

Cluster information

Cluster type: Hosted
Machine type VM with 281 gigs and 128 cpu cores. versio nv1.13.7
Kubernetes version

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.7", GitCommit:"4683545293d792934a7a7e12f2cc47d20b2dd01b", GitTreeState:"clean", BuildDate:"2019-06-06T01:46:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.7", GitCommit:"4683545293d792934a7a7e12f2cc47d20b2dd01b", GitTreeState:"clean", BuildDate:"2019-06-06T01:39:30Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version

Client:
Version:      1.10.3
API version:  1.24
Go version:   go1.5.3
Git commit:   20f81dd
Built:        Thu Mar 10 21:49:11 2016
OS/Arch:      linux/amd64

in rancher 2.2.6, each of our projects is configured to log to a custom fluentd pod, which performs some processing before forwarding the logs to another endpoint.  these custom fluentd pods live within the project and so can be controlled/modified by the project owners.  if one project owner deletes their custom fluentd deployment without removing the project logging configuration, it crashes the rancher fluentd pods and takes down logging for all projects in that cluster.

@aiwantaozi
Hi, I did some digging and it seems rancher's fluentd executes a copy and forward stanza. Here is what I am seeing on our end.
<match  cluster.** cluster-custom.** >    @type copy   <store>         @type forward         compress gzip         <server>           host cluster-logging.cluster-logging.svc.cluster.local           port 80           weight  100         </server>         <buffer>           @type file           path /fluentd/log/buffer/cluster.buffer           flush_mode interval           flush_interval 60s           flush_thread_count 8           queued_chunks_limit_size 200         </buffer>          slow_flush_log_threshold 40.0 </store>
Is it possible to try out https://docs.fluentd.org/output/copy#ignore_error-argument  ?
It may prevent project-level misconfigurations from affecting the entire cluster.
Thanks!

+1
We are also encountering this issue. When consumers uses project-level logging and misconfigure it, its blocks the whole fluentd daemonset from sending it to Elasticsearch. Anyway to work-around this issue?


[BUG] Vologram not appearing when used with a prefab on Android

Describe the bug
From Discord:

Hey guys, Im trying to enable the placement of a vologram within my scene based off of the AR Foundation tracked Image Manager. If the image is detected then the vologram should be placed etc... so basically image based detection. I seem to be having an issue though, Im not sure if saving a vologram object as a prefab to be placed is supported, but when the trigger is detected the vologram dosnt seem to appear? An object is definitely being placed within the scene as the vologram audio is playing etc, but its as if the mesh of the vologram just dosn't appear

To Reproduce
Steps to reproduce the behavior:

Create a prefab containing the VolPlayer component
Write a script that adds the prefab to the scene
Build the scene and run on an Android device
The vologram is placed but it is not visible

Expected behavior
Following the steps above, the vologram should be visible

After debug logging enabled these error messages appeared:

Volograms used were: joyce_2022 and TCD_Ulysses_sd

I've been working on this and found the key problem - the vol_libs library code underpinning this plugin's playback is using low-level file functions that are on some systems still 32-bits. That means they can break with files over 2GB.
I have been testing some replacement code using 64-bit versions of those functions. That appears to work on at least Windows and Linux, so I expect similar behaviour on macOS and iOS and Android.
I'll be adding that improvement to the https://github.com/Volograms/vol_libs project over the next days.
This may take a while as we need to thoroughly test this as it will impact several projects, including the Volu app.
There may be other libraries and tools affected but we will know shortly.

PR tested and merged -> Release coming shortly ~ tomorrow.


Can't run the Demo on Cesium V1.33.0 and V1.34.0

I tried to run the demo with a new version of Cesium, but it's not working.
The message on V1.33.0:
Uncaught Error: Core/GoogleEarthEnterpriseMetadata missing ThirdParty/pako_inflate
The message on V1.34.0:
Cesium missing ThirdParty/pako_inflate

seems an issue with cesium:
https://github.com/AnalyticalGraphicsInc/cesium/issues/5278

When i try to use the cesium V1.35.2, I get same problem: "Uncaught Error: Cesium missing ThirdParty/pako_inflate" .
The interest thing is the error info came from the vendor.js. So i guess the problem may be from webpack.
here is the debug info in my webstorm.

tested it with cesium 1.35.2 and worked!
my dependecies:

still having problems?

I suggest to close this issue. I found the demo  had problems. But when i directly use cesium-angular package in a new project. it has no problem.

resolved #70


Stable release channel?

Compiling 0.6.1 with stable rustc 1.62.1 results in:
error[E0554]: `#![feature]` may not be used on the stable release channel
   --> /home/rob/.cargo/registry/src/github.com-1ecc6299db9ec823/cc-traits-0.7.3/src/lib.rs:104:1
    |
104 | #![feature(generic_associated_types)]
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Is there a possibility to enable building with stable and avoid nigthtly, which is not endorsed for production?
P.S.
I tried to update the cc-traits to the newest 0.8.1, but the result is the same.

Hi, unfortunately generic associated types are required. They are currently in the process of being stabillized so we just have to wait a little longer.
However we currently also rely on trait aliases, another unstable feature that won't be stabilized any time soon. That is why I'm also working on the new version of json-ld that will get rid of all unstable features except for GATs. I'm doing my best to be done as soon as possible to finally have something usable with stable Rust.

Thank you very much for your effort and a swift reaction, @timothee-haudebourg! In the meanwhile, I will try to go with nightly.

@timothee-haudebourg What is the latest version that works on stable?

@timothee-haudebourg , GATS are stabilized now. It will be great if a json-ld parser, transformer is available for rust stable. Thanks for great work.

Hey, sorry for the delay I was on break.
Yes GATs are soon to be released on the stable channel (probably with Rust 1.65). But as I said above:

However we currently also rely on trait aliases, another unstable feature that won't be stabilized any time soon. That is why I'm also working on the new version of json-ld that will get rid of all unstable features except for GATs. I'm doing my best to be done as soon as possible to finally have something usable with stable Rust.

See #37 to see the progress on that. Only some work on the compaction algorithm remains before I can release it.

@timothee-haudebourg When do you think we could have a version release of json-ld that's stable? Is there anything we can do to help that along

If you want a version of json-ld that works with Rust stable, I published a beta version. It still lacks documentation and a few features and design testing before I can release a proper non beta version. If you want to help you can try to use it and give me feedback on the API, although with the current state of the doc, I don't expect it will be easy to do.
Please be patient until I can free some time to finish all that up.

Thanks a lot @timothee-haudebourg for your kind effort! That is a great progress, I will definitely give it a try.

I've just release version 0.9.1, which work with stable Rust 1.65. The transition from the old architecture may be rough, please don't hesitate to ask if you need help transitioning.


Is it possible to buy pre-assembled and flashed?

Please contact me via Telegram or Mastodon direct message.


Identity session monitoring

Issue and Steps to Reproduce
Event for validating that the auth session is still active.
If i open 2 tabs, and Identity cookies while listening to the events, then I refresh,  I see the "tryKeepExistingSessionAsync_end" with a message "tokens inside storage are valid"
Is there a way to actually validate that the identity server session is still active, or a function that returns current auth status
Current config
{  authority: process.env.REACT_APP_IDENTITY_SERVER_URL,
client_id: process.env.REACT_APP_IDENTITY_CLIENT_ID,
redirect_uri: ${window.location.origin}/authentication/callback,
scope: ${process.env.REACT_APP_IDENTITY_SERVER_SCOPES},
monitor_session: true,
silent_redirect_uri: ${window.location.origin}/callback,
silent_login_uri: ${window.location.origin}/authentication/silent
}
(Dont mind the uris, I am testing things around).
Additional Details
I have multiple applications that depend on the same identity session, and they have different client ids and scopes. I would like to be able to track when the identity session is no longer valid, or is gone, so i can reinitialize the auth flow, or take appropriate measures.

Hi @Alykod , that a good question.
I am using silent signin for doing this, but it work well on all browsers only if oidc server are on the same domain than your app.
For just a session cookie check, i have to search how to do that.

Hi have already implemented check session for single logout. It it possible to use that but it require oidc server and app on thz same domain to work well because of the new cookie restriction : https://connect2id.com/products/server/docs/api/check-session

Hi. Thank you for responding so quickly.
The identity server is in fact on the same domain. So I need to create a check session function similar to the one used for single logout ?

The simplest is to perform a silentlogin like you can do in the demo on multi page when your are login from first page : https://black-rock-0dc6b0d03.1.azurestaticapps.net/


Add new number style

Add an option 4 for g:lightline#bufferline#show_number to enable ordinal number to be shown before the buffer number.

Add a new option g:lightline#bufferline#ordinal_separator to define the separator between the buffer number and the ordinal number.

The new options can enable some interesting usages. For example, here is the settings I am using:
let g:lightline#bufferline#show_number = 4
let g:lightline#bufferline#number_separator = ') '
let g:lightline#bufferline#ordinal_separator = '('

Thanks! Looks like a useful addition.


Feature: Whitelisted smart contracts implementation

Please add bitstamp smart contract address in the default seed:
https://etherscan.io/address/0x1522900b6dafac587d499a862861c0869be6e428

Add documentation here

Please fix tests and write a documentation


Replace as casts in llvm.x86.addcarry.64 implementation

Recommended in https://github.com/rust-lang/miri/pull/2090#pullrequestreview-958491177.

Fancy. :D  Thanks a lot!
Can you move the new file into the (existing) helpers module, i.e., create a subdirectory with that name and put it there?

r=me with or without the inline
@bors delegate+

:v: @dtolnay can now approve this pull request

@bors r=RalfJung

:pushpin: Commit 8d42a7cfdf1eda2584c223354aaa76dd8dde7021 has been approved by RalfJung

:hourglass: Testing commit 8d42a7cfdf1eda2584c223354aaa76dd8dde7021 with merge 4bb36593e9b772b65816610c1a343ec8d9c0a82f...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 4bb36593e9b772b65816610c1a343ec8d9c0a82f to master...


Fix the travis build.

Primarily, fix the tangelo version to 0.7.0 until we are ready to update the tests.
Change how tangelo is called so that we can log error output.
Add vmstat to tell if travis is having a memory issue.  Added a quick test that errors out the travis build before doing much if the memory issue is happening.

Thanks @manthey LGTM

@manthey please do the merging honors to get us back on track with testing.


Tracing: add optionally configurable trace propagation input option to console commands

Currently, the "sentry-trace" HTTP header is used for trace propagation,
allowing traces from upstream services to continue traces to downstream services.
In order to trace between the service boundary of a web request to CLI application,
a new optionally configurable CLI option was added to provide the same trace
propagation mechanism, using the same format as the "sentry-trace" header

@ste93cry / @Jean85 : According to recent Git history, it looks like you both are the active maintainers for this repository.  I would like to contribute this feature to sentry-symfony so what would be needed to get this reviewed and merged?  Thanks in advance!

While I certainly find useful what you are trying to achieve, I don't really like the solution. Messing around with all the console commands by adding an input option seems a thing ready to cause errors and headaches in the future. I would prefer to understand if there are other solutions first, but as of now I'm not really inclined to say that I would merge this

Thanks for the reply @ste93cry !
I definitely understand the concern around potential future headaches and would feel awful if I caused it somewhere down the line. 😅
What are your thoughts on passing the trace propagation value through an environment variable (perhaps SENTRY_TRACE ?) This way, the console command's argv doesn't change as a result of enabling CLI trace propagation.


Add ruleSetId into Finding2

Add RuleSet.Id inside Finding2. In this same PR I also start using that in TestDetektion to simplify it. The next PR will use this new property to simplify even more all the Deteketion implementations.

Warnings

:warning:
It looks like this PR contains functional changes without a corresponding test.

  Generated by :no_entry_sign: dangerJS against fd93c8ad9cc9bcc7e1446c07c3c82d4150752b51


linux: relax filesystem requirements for container

change MUST to SHOULD so containers are not required to have all these filesystems mounted.
Related to discussions in https://github.com/opencontainers/runc/pull/1176
cc @cyphar @crosbymichael @philips @justincormack

I believe /proc MUST still be supplied, and /dev/pts in the case where you specify a console, and /sys if you specify sysctl config. Also /dev seems curiously missing...

On Mon, Jan 23, 2017 at 08:00:44AM -0800, Justin Cormack wrote:

Also /dev seems curiously missing...

It does not have to be a separate filesystem.  I'd floated devtmpfs in
the past [1,2], but folks can use other mechanisms to provide the
required devices 3.
If we're making these mounts optional for security reasons 4, we'd
be overturning an earlier decision on adding these (without a way to
opt-out 5).  For example, @philips has “considered making it
optional in appc but I don't think it hurts anything to have it” for
/dev/shm 6.
And if we do lift the requirement for these mounts, I'd rather just
drop the “Default Filesystems” section entirely.  Users who need these
mounts would have to explicitly set them up in their configuration (as
runtime-tools continues to do, see opencontainers/runtime-tools#24) if
they wanted to guarantee their presence.  Users who don't need them
can omit them from their configuration.  I don't see how keeping a
SHOULD-strength section (vs. dropping it completely) helps either of
those workflows.

I believe /proc MUST still be supplied, and /dev/pts in the case where you specify a console, and /sys if you specify sysctl config.

Makes sense. WDYT about:

/proc must be mounted
/sys must be mounted if sysfs config is set
/dev/pts must be available if terminal= true ( dont we want to take it out of process, i dont quite remember ?? )
leave out /dev/shm and the rest. I dont actually had any special requirements to not have /dev/shm, but i also feel like you use shm do you need /dev/shm. runc is a low level tool and should allow for weird use cases. In particular if you want to totally lock down ability to write to files by having no writeable mounts you want to remove /dev/shm makes sense

@wking /dev/shm is writeable (if it is not writeable it cannot be used for shm), and therefore can be used to fill a chunk of memory, possibly enough to cause your actual processes to crash if an attacker found a way to write to it. Without this you can have a totally read only container. So I think it is worthwhile to be able to remove it.

On Mon, Jan 23, 2017 at 09:38:46AM -0800, Daniel, Dao Quang Minh wrote:

/dev/pts must be available if terminal= true ( dont we want to
take it out of process, i dont quite remember ?? )

You may be thinking about #663.

leave out /dev/shm and the rest. I dont actually had any special
requirements to not have /dev/shm…

If we're rolling back the earlier “you won't need to opt out” position
in one case, I feel like we should roll it back for all of them.
Explicitly declaring these mounts is not particularly complicated
(opencontainers/runtime-spec#24) and we've already been wrong about
the need for opting-out once.

/sys must be mounted if sysfs config is set

sysctl writes value to /proc/sys, not /sys. so it is not needed to mount sysfs to /sys.

@Kxuan   sysctl is not sysfs, please don't get those confused.   sysfs should be mounted at /sys, if the container needs it.  Depends on what is running in it.

@gregkh yes, I know it. but they are discussing about "/sys if you specify sysctl config."

@Kxuan sysctls are set through the /proc/sys virtual filesystem -- not /sys. The two are very different (and @gregkh was one of the people who authored /sys's sysfs so he definitely knows what he's talking about :wink:).

LGTM
The spec does not specify what you MUST populate in your own spec.  If I'm writing a spec I can add whatever I want in it.  This section is meant as a hint to spec authors that these filesystems should be made available.
We need to stick to specing the schema for the fields in the spec and not spec what users put in it.

This section is meant as a hint to spec authors that these filesystems should be made available.

With the phrasing in 279c3c0 it looks like we're going from “the runtime MUST supply these even if the config doesn't call for them in mounts” to “the runtime SHOULD supply these even if the config doesn't call for them in mounts” (and I don't think we want that).  If the intention is actually to go to “config authors probably want to include mounts entries for these”, then I think we need to make that more explicit.  Something like:

On Linux, configuration authors are likely to want mounts to contain some of the following:
[entries from opencontainers/runtime-tools#24]

LGTM


Adding target for ADD

Hi @arun-gupta ,
Just a suggestion to add the target to the line of downloading the JDK9. Potentially consider making this line (with the download) the not-commented option to ensure the Dockerfile works first time a build is attempted.
Thanks,
Peter Dam

LGTM
The instructions require JDK to be pre-downloaded so this step would typically not be needed. But this is a good addition.
@ManoMarks please merge this

Sorry, I missed that from the instructions. Thanks for your reply and merge.


[ARD:mediathek] Bypass age restrictions

[x] I've verified and I assure that I'm running youtube-dl 2016.11.04
[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[x] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Description of your issue, suggested solution and other information
The ARD:Mediathek has this funny "feature" whereby certain videos are not
available during (CET/CEST) daytime, using server-side time checks. They do
this do protect children (with arguable value), but they are also imposing
inconvenience upon everyone in other timezones.
The restriction can easily be circumvented, e.g. using this
site, and it'd be trivial to add this to
youtube-dl.
The following instructions have been worked out by Birk Blechschmidt, who
shared this info with me specifically for the purpose of this feature request:

Given a URL like
http://www.ardmediathek.de/tv/Tatort/Echolot/Das-Erste/Video?bcastId=602916&documentId=38642286
extract the documentID

Call
http://mediathek.daserste.de/play/media/{$documentId}?devicetype=pc&features=flash
with {$documentID} replaced by the extracted ID. This will yield
a JSON structure.

From the contained _mediaArray array, extract the object that has
_plugin == 1. There will be a sibling _mediaStreamArray array which
lists all the available direct download/stream URLs (_stream) together
with a _quality label (integer, the higher the better…)

You can inspect the JSON dump like this:
GET 'http://mediathek.daserste.de/play/media/38642286?devicetype=pc&features=flash' | python -m json.tool

It'd be great to have this

Wow, it's as simple as that… I tried the patch and it seems to work.


Use a custom rule for API files generation

To prevent compiling the C++ code twice, we only want to build api_gen_binary_target for the target platform and not the execution platform.
To achieve this without causing confusion with source dependencies (e.g. putting api_gen_binary_target in srcs of the genrule), we use a custom rule to execute the command line for generating the API files.
Fixes https://github.com/tensorflow/tensorflow/issues/60167

@mihaimaruseac, can you review?

@meteorcloudy this is causing the internal build to fail: cl/520986273. Can you take a look?

Great to have this merged.
From https://github.com/tensorflow/tensorflow/issues/60167#issuecomment-1490907122, this is only a partial fix. How do you plan to finish removing the duplicate compilation?

Actually the change was automatically rollbacked due to some breakages, see https://github.com/tensorflow/tensorflow/issues/60298. Working on a rollforwad with fix.
I think the API gen rule is the major one, theoretically we can also fix other similar genrule in a similar way. But in long term,  I think there should be a way to tell Bazel that my host and exec are the exact same configuration, so Bazel can avoid building the target twice. /cc @gregestren @aiuto
On the other hand, I wonder if there is any way to avoid using those genrule at all? /cc @learning-to-play  @mihaimaruseac

In the mean time, can we roll back the commit that caused the regression?
I suppose what you propose will take times to get it.

@nouiz Unfortunately, that will prevent updating Bazel to 6.x for TensorFlow. I think with the fix the performance regression is much less significant, which should be fine?

The fix is now rolled forward at https://github.com/tensorflow/tensorflow/commit/da439b7d05584f93e745511d66f6d74a58b54b34

I think getting rid of API generation genrule and requiring the files to be checked in is a long-term solution, needs several changes, including adding CI to test that the API files are up to date.


new function getAnyPage to make Google genomics API call.

It might be good idea to have a generic API call function. Then a workflow  can be run in R (see example in getAnyPage help)
New  argument 'scope' is added into 'autheticate' function to anable arbitrary API calls. My changes in getSearchPage can be ignored. if the generic API function exists, getSearchPage should be just wrapper for the generic (getAnyPage) function

@vmorozov thanks for this
The example in getAnyPage help shows "readgroupsets/search" which works right now via getSearchPage.
Which other APIs in particular would you like to be able to call from the R client?  (sounds like perhaps  import reads and variants?)

Without knowing much about this, I would recommend a high-level interface that lets people write stuff like:
subset(callsets(genomics), sample=="A")

Instead of calling something like genomics.callsets.search.

@lawremi, thank you for your suggestion. It makes perfect sense. A deep integration with generic methods for Bioconductor objects (or even without Bioconductor, like providing an implementation of the subset method in your example above) is in the works but will take some more time as it is not very high priority and needs to be designed properly. The end result should be that people should be able to swap out a BAM file for the genomics API with only configuration changes and no actual code changes.
In the meanwhile, we can complete the rest of the API for this package in the existing layered approach as this can be done very quickly.

(Derail)
Are youse guise planning to do a workshop on the google genomics R client at BioC2015?  Because that would be an awesome way to get tons of feedback (and users!) fast.
--t

On Apr 22, 2015, at 12:05 PM, Siddhartha Bagaria<EMAIL_ADDRESS>wrote:
@lawremi, thank you for your suggestion. It makes perfect sense. A deep integration with generic methods for Bioconductor objects (or even without Bioconductor, like providing an implementation of the subset method in your example above) is in the works but will take some more time as it is not very high priority and needs to be designed properly. The end result should be that people should be able to swap out a BAM file for the genomics API with only configuration changes and no actual code changes.
In the meanwhile, we can complete the rest of the API for this package in the existing layered approach as this can be done very quickly.
—
Reply to this email directly or view it on GitHub.

@ttriche Yes, Sid and I will be there :-) http://www.bioconductor.org/help/course-materials/2015/BioC2015/

With regard to generics and the API, is there a reason that we (Bioc and Google) couldn't collaborate on this, with the goal being a new google genomics package?  We (Bioc) have structured a couple of other projects to have monthly conference calls for discussion and then work electronically via version control (including API design, etc.). I'm not sure how this would work from a licensing point-of-view, but having Bioc developers directly involved would potentially facilitate the development process a bit.    Just a thought....

@seandavi  +1 for collaborating in general and particularly on BioC generics!  I will follow up with you directly via email for meeting logistics.

My suggestion was to have something generic now. Tighter integration with/into BioC sounds great! Regarding what methods to wrap into R function, the Python API methods https://developers.google.com/resources/api-libraries/documentation/genomics/v1beta2/python/latest/index.html
look as reasanable starting point for the R API (:.


Model of Swagger and effective return do not match when using spring-data-rest

Repo demonstrating the issue https://github.com/n3utrino/hal-test
Maybe it is just a configuration issue.
Swagger Model
{
  "content": [
    {
      "id": "string",
      "name": "string"
    }
  ],
  "links": [
    {
      "href": "string",
      "rel": "string",
      "templated": true
    }
  ]
}

Return from service
{
  "_embedded": {
    "guys": []
  },
  "_links": {
    "self": {
      "href": "http://localhost:8080/guys"
    },
    "profile": {
      "href": "http://localhost:8080/profile/guys"
    },
    "search": {
      "href": "http://localhost:8080/guys/search"
    }
  }
}

I got it almost working.
by using the http://springfox.github.io/springfox/docs/snapshot/#answers-to-common-questions-and-problems ObjectMapper Wierdness FAQ Code
Now the remaining problem is the _embedded collection rel which looks like this in the definition
"_embedded": [
    {
      "id": "string",
      "name": "string"
    }
  ],

but is returned as
"_embedded": {
    "guys": []
  },

it seems like springfox is not taking in
@RepositoryRestResource( collectionResourceRel = "guys",itemResourceRel = "guy")

related to #1879 ?

Thanks for reporting.


Don't use report for isArchived check

Explanation of Change

Fixed Issues

$
PROPOSAL:
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[ ] I linked the correct issue in the ### Fixed Issues section above
[ ] I wrote clear testing steps that cover the changes made in this PR

[ ] I added steps for local testing in the Tests section
[ ] I added steps for the expected offline behavior in the Offline steps section
[ ] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[ ] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[ ] I included screenshots or videos for tests on all platforms
[ ] I ran the tests on all platforms & verified they passed on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[ ] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Have to fix the jest unit tests, I think we can do this by calling Onyx.set with the private_isArchived key inside the reportNameValuePairs collection

Update: The main problem here is the Jest unit tests. For example, Sidebar test is current failing. But running
Onyx.merge("reportNameValuePairs_7794523800315586", {private_isArchived: "something"});
does change the text in the sidebar to include (archived)

Hi @allgandalf, could you please take a look at this comment when you have a chance. I've been working on this PR on the side but looking to prioritize some other backend tasks so wanted to get some frontend expertise :)
This PR should set the foundation for using the reportNameValuePairs collection in the frontend. More context about that is in the linked issue

Looking into a bit more, running Onyx.merge for the reportNameValuePairs collection from the console only seems to work for workspace chats, not other reports like DMs. Whereas Onyx.merge for the reports collection works on DMs as well (in staging)

Yup, lets not worry about the failing lint for now, we can revisit whether or not we want to fix those once everything else is ready. The diff is pretty big as you said.

Hi @allgandalf! Have you had a chance to look at this?

Hi @allgandalf, did you get a chance to look at this today? Looking to merge in the next couple of days


Update cross-ministry-hiring.md

Thanks for the updates.  They will be merged as part of the next PR


Unexpected output when class attribute and constructor arg have same name (napoleon bug)

This is an upstream bug: https://github.com/sphinx-doc/sphinx/pull/11143
Suppose we have the following class:
class Example:
    """
    A Class

    Parameters
    ----------
    blah:
        Description of parameter blah
    """
    def __init__(self, blah: CodeType):
        pass

    blah: ModuleType

We get the following output (just the parameters):
   Parameters:
      **blah** (*module*) -- Description of parameter blah

Expected output:
   Parameters:
      **blah** ("CodeType") -- Description of parameter blah

If you want I can provide a monkey patch that implements my fix in https://github.com/sphinx-doc/sphinx/pull/11143 on existing versions of sphinx. I'm not sure how far we want to go in patching with upstream bugs.

Unless upstream rejects the PR I see no reason to do it here 🤔

Well the current behavior is quite clearly wrong so I sure hope they'll accept it. In my experience they are a bit slow about reviewing things. I'll open a PR.
Actually, one thing worth noting is that if we got the upstream change in, we would end up with the parameter type rendered as *code* (and no link if we use intersphinx/html) rather than "CodeType" (and a link). For some reason, Napoleon will fetch parameter types for class constructor args but not for parameters or function / method args. I think we might just want to disable this upstream parameter fetching.
In an ideal world, it would emit a napoleon-render-type event called with the object to produce a text representative of the object.

This broke Google style annotations marked as Attributes: from showing types in class header docstrings. (napoleon_attr_annotations = True)
For those who ran into this you will have to unpatch the patch:
import sphinx_autodoc_typehints
def _revert_patch():
    pass

sphinx_autodoc_typehints.patches._patch_google_docstring_lookup_annotation = _revert_patch

Unfortunately it doesn't apply the same style to the types without some overriding of GoogleDocstring._parse_attributes_section, but atleast you can get your types back into the header.


KeptnTask defaults not provided

The KeptnTaskDefinition spec shows retries and timeout parameters but doesn't list the defaults.
https://lifecycle.keptn.sh/docs/crd-ref/lifecycle/v1alpha3/#keptntaskdefinitionspec

Running a task without specifying retries or I see:
apiVersion: lifecycle.keptn.sh/v1alpha3
kind: KeptnTask
metadata:
spec:
  ...
  retries: 10
  ...
  timeout: 5m0s
  ...

The crd-ref-docs tool does not support this, however, if this  is merged we could add the info as an annotation to kubebuilder to make it visible in the docs.
In the meantime, we could also add such info in the description field 🤔

I'll put the label on hold since we depend on the external tool to provide this functionality


Support for Fireworks API Models with DSPY

Hello DSPY community.  I am trying to work out why my use of firework is failing when loaded into DSPY.   I've been trying to find an example without success, but I'm hoping someone who has experience with getting hosted models to work can clue me in to how to do this with dspy.
MyLM-1: <dsp.modules.gpt3.GPT3 object at 0x000002A2D198DBD0>
----------------------------------
-- TEST 1 ---
Using Local Model: Loaded from Chat UI
----------------------------------
-- TEST 2 ------------------------
Test Fireworks Usage without DSPY
Of course! I'm happy to assist you in a safe and respectful manner. This is a test. Please let me know if you have any other questions or if there's anything else I can help you with.
----------------------------------
-- TEST 3 ------------------------
MyLM-2: <dsp.modules.gpt3.GPT3 object at 0x000002A2D3DB23D0>
An unexpected error occurred a 3: Error code: 404 - {'detail': 'Not Found'}

What the output shows is

the Fireworks API key is correct.
the model I am using can be found and used by my python code.
something about DSPY loading the model causes it to fail.

This seems like a bug.  I thought I would report it and ask if there is a way to load models from Fireworks into DSPY?  If not, I think it would be a good feature, as my students don't have the resources to deal with local models, or hosted models at cost.  Fireworks offers free way for them to experiment with and learn DSPY.  Thanks.

ok for anyone who ever also runs into this problem... 1) I figured out that there is a log file that is output by openai object (good to know) with the (very counterinuitive) name: azure_openai_usage.log.  In it I found this:
HTTP Request: POST https://api.fireworks.ai/inference/v1/chat/completions "HTTP/1.1 200 OK"            <-- this is what is output by Test 2, using openai.OpenAI()
HTTP Request: POST https://api.fireworks.ai/inference/v1completions "HTTP/1.1 404 Not Found"           <-- this is what is output by Test 3, using dspy.OpenAI()

Thus indicating that the / was missing after the v1 ...
So my code needed to be:
api_base="https://api.fireworks.ai/inference/v1/"
Not:
api_base="https://api.fireworks.ai/inference/v1"
The funny thing was that I had been trying different variations of using no v1, and v1 based on someone else's post where they had the same issue, but hadn't stumbled on trying v1 without the forward slash.  Now it is working.
Note:  The standard openai.OpenAI() is this (which works):
        base_url = "https://api.fireworks.ai/inference/v1",

And that is what threw me off.   The DSPY version requires the forward shash after v1, but the openai version requires v1 without the slash.  Ahhh sooo... ok problem solved.


Fix coverage

I separated the change from this PR: https://github.com/BlueBrain/NeuroM/pull/1053/commits/d62e5116ae96ef14e40151279fd52f6b90fc4440
So that the coverage in the master is fixed asap.

Wait, this will fail for py37 isn't it?

I am attaching Alexis's reply to a similar question of mine in that PR:
https://github.com/BlueBrain/NeuroM/pull/1053#discussion_r974983236


add Api(updatePreopenStrategy)

add Api(updatePreopenStrategy)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.wenping.qwp seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


make format comment not be added if it was always ok

Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

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

Project coverage is 89.78%. Comparing base (4e3b4ab) to head (c02a115).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #554   +/-   ##
=======================================
  Coverage   89.78%   89.78%
=======================================
  Files         108      108
  Lines       34498    34498
=======================================
  Hits        30975    30975
  Misses       3523     3523

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


Fix syntax error in test related to cupy (#9000)

Port of https://github.com/pydata/xarray/pull/9000

[ ] Closes #xxxx
[ ] Tests added
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

@andersy005 did something go wrong with the merge/rebase?
@hmaarrfk this looked the same as #9000 - isn't this already commited?
(or maybe I am misunderstanding something)

the difference is the target branch: the fix is already on main, this goes to the namedarray feature branch (backend-indexing)

I am closing this pull request as I've updated the backend-indexing branch and resolved the merge conflicts.


Add SAW AES proof.

Use Galois' SAW tool to prove correctness of OpenSSL's AES implementation.

I'm wondering if it's useful to have a travis target that has enable-saw

I think the proof directory should follow the cyprto directory tree.

I see you have an eas.cry that comes from cryptol, and an eas.saw that proves certain things about aes.cry, but I currently don't see how any of those 2 files is used to check the OpenSSL implementation.

@richsalz said:

I think the proof directory should follow the cyprto directory tree.

I agree.  The AES related files currently in proof should be in proof/aes

Also, gut feeling...  this could be made into a config target of its own rather than a mere option.

this could be made into a config target of its own

I'd actually ask why dedicated target or option at all? The input that is used here is llvm byte-code for aes_core.c alone. Does one actually have to compile whole thing to take just single file? Isn't it sufficient to generate byte-code for that one source file? I mean it is sufficient, so why not do just that?
In case one argues that there is value in corresponding build passing 'make test'. I'd argue not really. What is exercised by 'saw' is llvm pseudo-code, while what is exercised by 'make test' (if it works, see previous comment) is actual machine code. One can only draw conclusion about correctness of input C code, but in such case what difference does it make how machine code was generated, with llvm pseudo-code in the middle or without?

The input that is used here is llvm byte-code for aes_core.c alone. Does one actually have to compile whole thing to take just single file? Isn't it sufficient to generate byte-code for that one source file? I mean it is sufficient, so why not do just that?

That's a good point...  for aes_core.c.  Will this apply for everything we might want to prove?  I can only assume that this proof on AES is meant as a proof of concept, so we need to think of what else might get the same kind of handling.  On the other hand, it is doable to emit llvm code for a select set of files, and it's not very hard to get support for it with the build system either (I'll get back on that).

Will this apply for everything we might want to prove?

It's impossible to answer such general question affirmatively, but let's put it this way. It's more than likely to be the case for 'saw', i.e. you more than likely have to rip out, or rather generate llvm byte-code for specific module and implement some shim code to facilitate the experiment.

So my main concerns with this pull request are:

What is the license of some of those files, and can we get them covered by a CLA?
The CFLAGS / LDFLAGS related changes.

@levitte: Is the CFLAGS / LDFLAGS something you can work on?

I can look into the cflags / ldflags thing. It's not going to be easy, but should be doable.

@benlaurie, if you're interested, I played around with your work and did an integration into our build system.  Have a look at https://github.com/levitte/openssl/tree/add-saw.
It has a crude start of running saw as part of the test suite, but I've yet to verify that it works as expected.

Update: I've fiddled enough with my branch, it builds cleanly and tests cleanly on Linux, mostly with ready made packages, all I needed to add was the SAW kit.

After some additional consideration I'm leaning toward arguing against integrating this with build system the way it's suggested. With following rationale. What are prime goals for arranging the build system the way we do? a) To have a way to describe build procedure in platform-independent manner, and b) make it flexible enough to permit site-specific adaptations.
As for a). It should be noted that in the context "platform-independent" refers rather to Makefile than to specific OS, or more specifically it's essentially Unix[-like] environment vs. Windows vs. VMS. Question that pops into mind is whether or not it's actually interesting or necessary to support anything but Unix in this case? And if not, then how come pre-tailored proof/Makefile wouldn't do? As for necessity [to support non-Unix[-like] environments]. One should recognize that this stuff is not something that every user needs (or even affords) to do. And provided that outcome is "transferable" [in sense that successful outcome applies to all platforms], it's not unreasonable to limit support to Unix-likes and tell users to perform it on Linux or MacOS. [Well, Cygwin and msys are likely to work too.] Another argument against investing too hard into integrating this with "big" build system is question about tomorrow. I mean tomorrow we might want to use another tool in addition to this one and how would we approach it? Tweak makefile generator to become even more complex, i.e. less manageable? When pre-tailored Makefile would actually do?
As for b). Judging from this case flexibility (of the kind we're talking about here) is not required or even appreciated. In other words pre-generated proof/Makefile would actually suffice. Well, it needs to find to source directory, and question would be if referring to .. as source directory is sufficient, or do we introduce additional target to unix-Makefile.tmpl that passes few pointers to proof/Makefile.
As for "tomorrow". Of course tomorrow situation might be different and we might have to do things differently. But the keyword is "have to". I mean I don't see reason to invest into integration with "big" build system unless we actually have to. And I'd say that in this case we don't actually have to, i.e. that pre-tailored proof/Makefile is sufficient. I'd say that initial criteria for "have to" is that verification tool would work on actual processor-specific binary code [which is not case here.] Should/may I make counter-suggestion based on this request?

@dot-asm, I hear you.  The support PR I made could be seen as an academic exercise (and as such, it's not lost on me even if it never goes into or base code).

Should/may I make counter-suggestion based on this request?

By all means, feel free!

So what is the status of this?

Is this at all interesting?  Considering no one has said anything here for a couple of years, I'm tempted to close this.  However, should anyone find this interesting...

I think it is interesting and while this PR may never got done, having a proof around so that we could do work on formally-verified crypto would be helpful.  (Amazon's s2n does it, for example)

I think this should be closed. I don't disagree that formally-verified crypto would be a good thing - but there has been no activity on this for nearly 3 years. If someone shows interest again then we can always reopen.


Generated documentation missing widget generic post message events

After running the ./bin/run command to generate the docs, looking at the generated documentation, it seems to be missing the widget generic post message events.
mx/load
mx/ping
mx/navigation
mx/focusTrap
I'm not sure if this is intentional or not, if so please close this issue.

It's intentional, at least for now it is. We'll need those docs in the future (along with any other widgets that have post messages), so if you want to repurpose this issue for that, that'd be great.

Also, let's keep assignees for when someone takes the issue to go work on it. @inphomercial

Also, let's keep assignees for when someone takes the issue to go work on it. @inphomercial

Sorry, I'm used to the reviewers section on gitlab, totally thought that's what I was assigning.


web 用 socket io 1.7 连接不上问题.WebSocketTransport

因为调用了下面 close的代码,导致连接不上.
if (client != null && client.isTransportChannel(ctx.channel(), Transport.WEBSOCKET)) {
log.debug("channel inactive {}", client.getSessionId());
client.onChannelDisconnect();
}
super.channelInactive(ctx);
if (client != null) {
client.send(packet);
}
channel.close();
ctx.close();
把代码改成
  if (client != null && client.isTransportChannel(ctx.channel(), Transport.WEBSOCKET)) {
        log.debug("channel inactive {}", client.getSessionId());
        client.onChannelDisconnect();
        client.send(packet);
        channel.close();
        ctx.close();
    }
    super.channelInactive(ctx);

this is correct. the channel should not be closed if it is not supposed to be disconnected. but i am wondering what is the point of sending the packet? can it / should it send a packet after it has already called onChannelDisconnect?


updated: Upload & Source Code

Checklist for submitting a pull request to Movies For Hackers:

[x] I have carefully read and comply with the Contributing Guidelines of this repo.
[x] I have searched the PRs of this repo and believe that this is not a duplicate.

1.) Upload

Title: Upload
Link: https://www.imdb.com/title/tt7826376/
Genre: Drama/Mystery/Sci-Fi
Rating: 8.0/10

Description: A man is able to choose his own afterlife after his untimely death, by having his consciousness uploaded into a virtual world. As he gets used to his new life and befriends his angel (real world handler), questions about his death arise.

2.) Source Code

Title: Source Code
Link: https://www.imdb.com/title/tt0945513/
Genre: Action/Drama/Thriller
Rating: 7.5/10

Description: A soldier wakes up in someone else's body and discovers he's part of an experimental government program to find the bomber of a commuter train within 8 minutes.

Source Code is pretty good as a movie but the title is very misleading. There is almost nothing in that movie that would be for hackers. For that reason, I don’t think it should be included.


Resource exhausted:  OOM when allocating tensor with TF 2.4.0

System information

Have I written custom code (as opposed to using a stock example script
provided in TensorFlow): The code is from PyImageSearch.com, it runs fine on TF 2.3.1
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 Pro, version 20H2, OS build: 19042.685
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue
happens on a mobile device: -
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.4.0 (sorry, 2.4 is uninstalled now, I cannot run that command)
Python version: 3.7.5
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source): -
CUDA/cuDNN version: 11.0.2_451.48 / 11.0
GPU model and memory: NVIDIA GeForce RTX 2060, 6 GB RAM
Exact command to reproduce: run my python script with my data, after around 940-960 epochs it runs out of memory

Describe the problem
There is a bug around TensorFlow 2.4.0: the exact same code runs fine with the following components in python:
tensorflow==2.3.1
tensorflow-gpu==2.3.1
cuda_10.1.105_418.96_win10.exe
cudnn-10.1-windows10-x64-v<IP_ADDRESS>.zip
But give a "Resource exhausted:  OOM when allocating tensor" error after 900 and some epochs with TF 2.4.0:
tensorflow==2.4.0
tensorflow-gpu==2.4.0
cuda_11.0.2_451.48_win10.exe
cudnn-11.0-windows-x64-v<IP_ADDRESS>.zip
In the logs, I found this:
/job:localhost/replica:0/task:0/device:CPU:0 by allocator cpu
Can it be, that TF is switching to cpu instead of gpu at one point?
Source code / logs
Logs of two runs:
bug.txt
bug2.txt

@lmocsi
Please share stand alone indented code and dependencies to replicate or if possible share a colab gist with error reported.

@lmocsi
Please share stand alone indented code and dependencies to replicate or if possible share a colab gist with error reported.

What do you mean by "stand alone indented code and dependencies"? All the code and the 8000 images?
What is a "colab gist with error reported"?

What do you mean by "stand alone indented code and dependencies"? All the code and the 8000 images?

I'm not sure if I can simplify the code for you to be able to reproduce the problem, since it is running on 8000 images, and the problem arises only above 900 iterations.
Could you instead compare the codes of TF 2.3.1 and 2.4.0 with respect to the errors described in the bug txt files?
Python37\lib\site-packages\tensorflow\python\eager\execute.py, line 60 seems to be the starting point.

I'm not sure if I can simplify the code for you to be able to reproduce the problem, since it is running on 8000 images, and the problem arises only above 900 iterations.
Could you instead compare the codes of TF 2.3.1 and 2.4.0 with respect to the errors described in the bug txt files?
Python37\lib\site-packages\tensorflow\python\eager\execute.py, line 60 seems to be the starting point.

Have you tried using smaller batch sizes for your training?

Have you tried using smaller batch sizes for your training?

No. The exact same batch size works perfectly on TF 2.3.1.

No. The exact same batch size works perfectly on TF 2.3.1.

Please try to provide a simple minimal reproducer code so that people can use it to bisect the issue and then create a regression test to prevent the issue from appearing in the future.

Please try to provide a simple minimal reproducer code so that people can use it to bisect the issue and then create a regression test to prevent the issue from appearing in the future.

As I've said, creating a "simple minimal reproducer code" is extremely difficult in this case, almost at the level of solving the problem.

As I've said, creating a "simple minimal reproducer code" is extremely difficult in this case, almost at the level of solving the problem.

Hello.
Tagging myself into this issue and keeping it alive.
I believe that I might be facing this issue too.
I have upgraded from tf1.14 to 2.4 recently and I think my code is good, although I need to generate some small generic standalone code in the process of debugging my code.
It will take me a few weeks to get some code in a Colab to see if I can replicate it there.
Will let you know the outcome.
Please advise if anyone resolves this.

Hello.
Tagging myself into this issue and keeping it alive.
I believe that I might be facing this issue too.
I have upgraded from tf1.14 to 2.4 recently and I think my code is good, although I need to generate some small generic standalone code in the process of debugging my code.
It will take me a few weeks to get some code in a Colab to see if I can replicate it there.
Will let you know the outcome.
Please advise if anyone resolves this.

Similar issue here. OOM exception during a call to model.fit() while it is trying to allocate a tensor.
(0) Resource exhausted:  OOM when allocating tensor with shape[3072,768] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
The recommendation I have seen everywhere on github and stackoverflow is to reduce the minibatch size. I don't think the batch size is the issue in my case since:

error occurs only in the 13th trials. Each trial uses a new instance of the same model architecture. batch size = 8. Previous instance is discarded each time. Why would first 12 trials fit comfortably into GPU memory and not the 13th?
I can run 12 trials with batch size = 16. Also crashes at 13th.
nvidia-smi logs shows the GPU RAM utilisation doesn't exceeds 58% (batch size = 8) and returns to 0% before each trial (indicating that there is no GPU memory leak).

Reproduced with tensorflow 2.3.1, 2.4.0, 2.4.1; 1080 ti; ubuntu 20.04.

Similar issue here. OOM exception during a call to model.fit() while it is trying to allocate a tensor.
(0) Resource exhausted:  OOM when allocating tensor with shape[3072,768] and type float on /job:localhost/replica:0/task:0/device:GPU:0 by allocator GPU_0_bfc
The recommendation I have seen everywhere on github and stackoverflow is to reduce the minibatch size. I don't think the batch size is the issue in my case since:

error occurs only in the 13th trials. Each trial uses a new instance of the same model architecture. batch size = 8. Previous instance is discarded each time. Why would first 12 trials fit comfortably into GPU memory and not the 13th?
I can run 12 trials with batch size = 16. Also crashes at 13th.
nvidia-smi logs shows the GPU RAM utilisation doesn't exceeds 58% (batch size = 8) and returns to 0% before each trial (indicating that there is no GPU memory leak).

Reproduced with tensorflow 2.3.1, 2.4.0, 2.4.1; 1080 ti; ubuntu 20.04.

@geoffroy-noel-ddh are you using python generators with a tf.keras.Model() and fit()

@geoffroy-noel-ddh are you using python generators with a tf.keras.Model() and fit()

@normanheckscher Thanks for asking. No, the model is instantiated and trained in a method which is called by a loop. I managed to fix the issue, which was due to my training callback (to implement early stopping) being a class instance. By instantiating the callback within the loop, the memory error disappeared. I assume that singleton instance was somehow holding resources from being freed.

@normanheckscher Thanks for asking. No, the model is instantiated and trained in a method which is called by a loop. I managed to fix the issue, which was due to my training callback (to implement early stopping) being a class instance. By instantiating the callback within the loop, the memory error disappeared. I assume that singleton instance was somehow holding resources from being freed.

Have you considered limiting gpu memory growth?
Make sure you close all python sessions and exit python interpreter to free up memory and try running script as:
#On top of your script
import tensorflow as tf
gpu = tf.config.list_physical_devices('GPU')
tf.config.experimental.set_memory_growth(gpu[0], True) #limits gpu memory
# Rest of your code

I have the same issue. @ymodak memory growth does not help. I still get an OOM with keras and tensorflow 2.4 while it was working with 2.3 and 2.2. The memory growth option should not help here. Correct me if I am wrong, but it's only enable / disable that tensorflow reserves all memory in front up vs. when needed.

any updates?

any updates?

I'm short on time to commit to this, so I'll probably never get to the bottom of it. My conclusion is that the source of this problem is within the tensorflow/cuda code or its a python incompatibility.
Ultimately, I'm just going to revert my codebase back to tensorflow 1.1x, an older version of cuda and import keras as a separate python library. This worked for me in the past and it should work again.


Clean README

Server package doesn't exist any more
Signed-off-by: Zhang Wei<EMAIL_ADDRESS>

Sorry, the server package is still pending to be moved here, as it says in:
This package is still pending to be extracted from the Docker engine.

I'm okay with removing this from the readme, we'll have to rewrite it again anyways.

Ah, I didn't notice it, and now I know.
It's all OK, I'll close it now. :smile:


[spark] Supports Spark Streaming Source

Purpose

Linked issue: close #xxx

Tests

API and Format

Documentation

A following pr will to support the admission control to limit he rate of data ingested.

Hi @YannByron , thanks for the contribution.
I don't get why you need to introduce a new StreamingScanner. Can we just use Table.newReadBuilder.newStreamScan?
What is the requirement in Spark streaming?

I try to refactor StreamTableScan for spark streaming read: #1905

Merged.


Payment screen integration

but key might change... as it is hust the response of an API.
I think the other way might be more stable?
On Sun, Nov 29, 2020 at 16:56, Anup<EMAIL_ADDRESS>wrote:

@reznord commented on this pull request.

In src/containers/widget/index.js:

@@ -81,6 +101,24 @@ const Widget = ({
onNextClick={handleDonateNextClick}
/>
);

 case "payment-screen":

   return (

     <PaymentScreen

       title={widgetTitle}

       currency={currency}

       onRequestClose={closeModal}

       selectedAmount={selectedAmount}

       {...invoiceDetails}

If the keys won't change it won't be a problem, I am just spreading al the props instead of passing each key.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


fix schema validate required property

What this PR does / why we need it?
#1126
Summary of your change
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.昊棠 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report
Base: 74.49% // Head: 72.02% // Decreases project coverage by -2.48% :warning:

Coverage data is based on head (143de73) compared to base (1464b78).
Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head 143de73 differs from pull request most recent head 1d736fe. Consider uploading reports for the commit 1d736fe to get more accurate results

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #1127      +/-   ##
============================================
- Coverage     74.49%   72.02%   -2.48%
+ Complexity    18507    17982     -525
============================================
  Files           716      716
  Lines         76320    76075     -245
  Branches      16353    16273      -80
============================================
- Hits          56857    54793    -2064
- Misses        12611    14582    +1971
+ Partials       6852     6700     -152

Impacted Files
Coverage Δ

...ava/com/alibaba/fastjson2/schema/ObjectSchema.java
88.40% <100.00%> (+0.57%)
:arrow_up:

...java/com/alibaba/fastjson2/JSONWriterUTF8JDK9.java
1.62% <0.00%> (-84.21%)
:arrow_down:

.../src/main/java/com/alibaba/fastjson2/util/Fnv.java
25.58% <0.00%> (-51.17%)
:arrow_down:

...in/java/com/alibaba/fastjson2/JSONReaderASCII.java
57.78% <0.00%> (-32.69%)
:arrow_down:

...main/java/com/alibaba/fastjson2/util/JDKUtils.java
46.85% <0.00%> (-24.74%)
:arrow_down:

...va/com/alibaba/fastjson2/reader/ValueConsumer.java
16.66% <0.00%> (-16.67%)
:arrow_down:

.../java/com/alibaba/fastjson2/JSONReaderJSONBUF.java
62.15% <0.00%> (-10.07%)
:arrow_down:

...ain/java/com/alibaba/fastjson2/JSONReaderUTF8.java
71.43% <0.00%> (-7.85%)
:arrow_down:

...in/java/com/alibaba/fastjson2/JSONReaderJSONB.java
61.92% <0.00%> (-6.90%)
:arrow_down:

...ain/java/com/alibaba/fastjson2/util/DateUtils.java
78.56% <0.00%> (-6.45%)
:arrow_down:

... and 58 more

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

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


Add message logging callback

Maybe we can integrate this directly into the websocket so it will also work for 1.6


In test suites, replace instances of make_fake_text with faker.sentence()

In the test suites, particularly test_views, tests will occasionally fail because our make_fake_text function sometimes has \ns in the text it generates. I've been making the substitution of faker.sentence() for make_fake_text as I come across it over the past few months, but it would be worth doing a full go-through of the tests to ensure no make_fake_texts remain.
Why this is worth fully solving, rather than just fixing bit-by-bit as we go: In trying to figure out #607, we're getting three distinct kinds of errors (as far as I can tell) - ones related to make_fake_text, ones related to CantusIndex switching from http to https, and ones related to ConnectionErrors. It would be helpful if we could resolve all of the first kind of errors, making it easier to focus on the truly puzzling ConnectionErrors.

fixed by #617


Make a demo video of a successful bank card payment

Similar to my Stripe videos: https://github.com/mage2pro/stripe#demo-videos

AlphaCommerceHub integration with Magento 2. Part 1. Capture a bank card payment


Allow for use of old external string indexing

make changes in #400 to be optional

Changes Unknown when pulling 23878d65531063c5934ae0103e9a19358d845fb3 on bmyerz/un-stringz into ** on master**.

Changes Unknown when pulling 23878d65531063c5934ae0103e9a19358d845fb3 on bmyerz/un-stringz into ** on master**.


Path.combine doesn't work on web with the html renderer

Path.combine is unimplemented in the web engine for the html renderer.
Full context
  static Path combine(PathOperation operation, Path path1, Path path2) {
    assert(path1 != null); // ignore: unnecessary_null_comparison
    assert(path2 != null); // ignore: unnecessary_null_comparison
    if (engine.useCanvasKit) {
      return engine.CkPath.combine(operation, path1, path2);
    }
    throw UnimplementedError();
  }

However, the framework uses it in two places:
https://github.com/flutter/flutter/blob/fe16c206ea19a9e8b9b5ff5ac7b73ea707f98e39/packages/flutter/lib/src/cupertino/text_selection_toolbar.dart#L282
https://github.com/flutter/flutter/blob/fe16c206ea19a9e8b9b5ff5ac7b73ea707f98e39/packages/flutter/lib/src/painting/notched_shapes.dart#L162
Is it intentional that Path.combine can't be used on web with the html renderer?  Should we be guarding against that in these two usages in the framework? CC @mdebbar

Deduplicating into https://github.com/flutter/flutter/issues/44572


cannot see or install any extentions

Type: Bug
cannot see or install any extentions on my mac mini m2
open vscode
search for extentions
error while fetching extensions. XHR timeour: undefinedms
VS Code version: Code 1.83.1 (Universal) (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:46:55.789Z)
OS version: Darwin arm64 23.0.0
Modes:

Hi @lud89 Thanks for reaching out. If you're using a VPN client or some local firewall, please turn these off and retry. If the error is still persisting, it will help us to investigate, if you can share the network log ( command: Developer: Open Logs Folder).
Regards,
VS Marketplace Team

Closing the issue as there have been no updates for a week. If the problem persists you can contact us with the requested network log.
Thanks,
VS Marketplace Team


(BetterChatbox) See Server Profile

When in a server, the profile shown upon tapping ones pfp isn't that of the active server (so no roles, server profile edit option, ect).  It would be awesome if it brought up one's server profile instead. Also if the avatar were to change to your server avatar (if different) that would just be icing!

it already has both of those features

it already has both of those features

After trying again, it does in fact show server avatars now, however it does not show server profile on tap whatsoever at least for me.
v1.2.1

What I'd expect to see:

What I actually see:

must be a weird bug only you are experiencing, as i haven't gotten any other reports