Problems with Fedora 28

So apparently Fedora 28 includes emoji by default!
Unfortunately they went for Noto Emoji. And you can't uninstall it without uninstalling like the whole system.
So I guess I'll have to fix this somehow.
Unfortunately I don't have very much time for the next 1-2 months so a fix might take a bit longer...

the easiest would be to overwrite the file.
i did the same on Ubuntu:
After installing fonts-noto-color-emoji, i replaced /usr/share/fonts/truetype/noto/NotoColorEmoji.ttf with the file i had just built.
This has the advantage of ensuring that the correct config is applied, but the disadvantage of that file running the risk of being overwritten by the package manager on a (system) upgrade
But, anyway, the "correct configuration" (on Debian/Ubuntu) is provided by https://gist.github.com/igalic/74370cad53264c306c34672ec5945559 and pretty much always enabled

(I'm not sure whether this is still relevant)


Add a test to verify #542 is not an issue

Reading #542 I see we miss a test for that use case.
So I added one and the test passes as expected.
Perhaps there was a bug in the jsonpatch library we're using at the time
🤷
/assign mattmoor
Fixes #542

/lgtm
/approve


JPMS compatible schema output paths.

JPMS requires resources that are accessible from outside the module to be in unique and open packages.
To achieve this, we place the generated schema in the same package as the source type.
(Update some build conventions too)

coverage: 98.667% (+0.4%) from 98.23%
when pulling ecc70d9a66a9d5a5c3f4e6f7cfd16a3412ceba2f on jpms-schema-paths
into 618ff8a19034b242e8ccd6e4f56d7ef938e52334 on main.


Add Take by Risshuu

Song Name
Take
Artist Name
Risshuu & Choko
Source
Youtube
Youtube Link
https://www.youtube.com/watch?v=65Smh8rwdJI
Direct File Link
No response
Song ID
1130348
Start Offset [ms]
0
Extra
Created from Auto Nong.

accept
Вт, 16 июля 2024 г. в 23:54, auto-nong[bot] @.***>:

Thanks for contributing!
Someone will soon review your request.
Here is the JSON result for the reviewer:
{
"name": "Take",
"artist": "Risshuu & Choko",
"source": "youtube",
"startOffset": 0,
"yt-id": "65Smh8rwdJI",
"songs": [
1130348
]
}
To accept the request, a reviewer needs to write "accept".
—
Reply to this email directly, view it on GitHub
https://github.com/FlafyDev/auto-nong-indexes/issues/1420#issuecomment-2231613581,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BIKC2GOK4TCSUCUXIYETA7LZMVT6NAVCNFSM6AAAAABK7FIOSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZRGYYTGNJYGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


[DEMO] Dressed quantum classifier with Jax and HuggingFace

General information
Name
Skylar Chan

Demo information
Title
Hybrid Quantum Transfer Learning with Pennylane, Jax, and Flax
Abstract
This demo shows how to train a dressed quantum circuit to classify MNIST with Jax, Flax, and HuggingFace. This demo shares some code with the multilabel chest X-ray classifier developed in arXiv:2405.00156.
Relevant links
https://github.com/schance995/dqc-demo

Hi @schance995 , thanks so much for sharing the code from your paper! The repository looks great and we'd be happy to give it a highlight.
When it comes to posting on social media, do you and/or your group or university have accounts we should tag? This would be on Twitter and LinkedIn. If you have a pennylane.ai profile, you can also let me know about your username.

Also, could you please tell us how you started using PennyLane for your research? That would be really valuable info for our team.

That sounds awesome; thanks a lot, @schance995 ! :D
You can see your community demo live here, and I've shared the social links with our Marketing Team, as well.
Great work with this one, it was easy to understand and very cool to see your work. I wish you the best with future projects. :)


Fix the Result project path.

Carthage does not checkout nested dependencies at the root Carthage/Checkouts/ folder.

@andersio maybe cut a 0.2.0 or 0.1.1?

Yep.


Issue with tiles stretching while rendering

I am running into an issue when I try and view the map in a resium viewer, the tiles are stretching and I cannot figure out how to resolve this.

I have checked to ensure the images are being served correctly and when looking in the resources, they appear normal, it is doing the stretching when it is being rendered in the container.
This is the code used to render from the locally hosted WMS server.:

That issue is not due to Resium. Discuss about it at Cesium Community


winget install anything results in: "0x80004002 : No such interface supported"

Brief description of your issue
I'm running cmd as administrator and trying to get anything at all to install, I've tried random packages like cpu-z, evernote, both are giving this error "0x80004002 : No such interface supported"
(I did search google and your issues here, I can't find this error string anywhere)
Steps to reproduce
Start, cmd, run as administrator, "winget install cpu-z"
Expected behavior
it installs?
Actual behavior
D:\>winget install cpu-z
Found CPUID CPU-Z [CPUID.CPU-Z]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://download.cpuid.com/cpu-z/cpu-z_1.96-en.exe
An unexpected error occurred while executing the command:
0x80004002 : No such interface supported

Environment
D:\>winget --info
Windows Package Manager v1.0.11451
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.17134.1845
Package: Microsoft.DesktopAppInstaller v1.11.11451.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Any other software?

I'm guessing no, but does it work if you run it from a non-admin command prompt and let it UAC the installer itself?

I get the same thing for any install I try, non-admin or admin - thanks!

@theinventor can you submit Feedback and share the URL?

@theinventor can you submit Feedback and share the URL?

Ok, I submitted and put this issue URL on it. Hope that's what you meant :)

@theinventor
We've published the v1.1 release candidate and updated our troubleshooting guide.
Can you confirm if this is still happening?


Changing seeds columns fails

If I have seeds that look like this
id,value
1,'hello'
2,'world'

and then change to look like this
id,status
1,'hello'
2,'world'

then I get
00:40:48  Runtime Error in seed so2_status_codes (seeds/status_codes.csv)
00:40:48    Binder Error: Table "so2_status_codes" does not have a column with name "status"

And the table must be manually deleted in order to work around.

well that sucks, I'm sure I can repro that pretty easily... 👀

Yep, easy to repro, but it looks like we match the behavior of other dbt adapters based on my reading of the code here: https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/include/global_project/macros/materializations/seeds/helpers.sql#L33
If you run dbt seed --full-refresh, the error goes away; the issue is that a seed table is only truncate'd by default, not dropped entirely, and it seems like that applies to any of the adapters.

Indeed, just confirming what @jwills read in the source - the Docs verify that behavior as designed.

Ahh ok, cool!
Thanks for quick response and maintaining this project!! :D


File dataset/babel/babel-smplh-30fps-male/../babel-teach/val.json is missing

Is it possible that some dependency is missing from the README?
When I run python -m sample.double_take --model_path ./save/Babel_TrasnEmb_GeoLos/model000850000.pt --dataset babel --handshake_size 20 --blend_len 10, I get the fowllowing output:
generating samples
Loading dataset...
Traceback (most recent call last):
  [some debugger stuff]
  File "/workspaces/text2animation/priorMDM/sample/double_take.py", line 281, in <module>
    main()
  File "/workspaces/text2animation/priorMDM/sample/double_take.py", line 95, in main
    data = load_dataset(args, n_frames)
  File "/workspaces/text2animation/priorMDM/sample/double_take.py", line 270, in load_dataset
    data = get_dataset_loader(name=args.dataset,
  File "/workspaces/text2animation/priorMDM/data_loaders/get_data.py", line 75, in get_dataset_loader
    dataset = get_dataset(name, num_frames, split, load_mode, batch_size, opt, short_db, cropping_sampler, size)
  File "/workspaces/text2animation/priorMDM/data_loaders/get_data.py", line 63, in get_dataset
    dataset = DATA(split=split,
  File "/workspaces/text2animation/priorMDM/data_loaders/amass/babel.py", line 396, in __init__
    self.babel_annots = read_json(Path(datapath) / f'../babel-teach/{split}.json')
  File "/workspaces/text2animation/priorMDM/data_loaders/amass/file_io.py", line 21, in read_json
    with open(p, 'r') as fp:
FileNotFoundError: [Errno 2] No such file or directory: 'dataset/babel/babel-smplh-30fps-male/../babel-teach/val.json'

Note, that dataset/babel/babel-smplh-30fps-male exists as explained in the README.

Well, so it worked when I added the data from here. I guess this should be added to the README?

Thanks and sorry for the slow respond.
It is actually appears in the readme,
under:
Get PriorMDM dependencies
Download the processed version here, and place it at ./dataset/babel
didn't it work for you?

But then I only get babel-smplh-30fps-male.zip, and when I extract it I get:
root $ unzip babel-smplh-30fps-male.zip
Archive:  babel-smplh-30fps-male.zip
   creating: babel-smplh-30fps-male/
  inflating: babel-smplh-30fps-male/.DS_Store
  inflating: __MACOSX/babel-smplh-30fps-male/._.DS_Store
  inflating: babel-smplh-30fps-male/val_tiny.pth.tar
  inflating: babel-smplh-30fps-male/train_tiny.pth.tar
  inflating: babel-smplh-30fps-male/train.pth.tar
  inflating: babel-smplh-30fps-male/val.pth.tar

So the babel-teach folder is missing.

+1，the babel-teach folder is missing.

Thanks you for the notice and sorry for the delay,
I added the additional needed download to the readme file.
babel-teach, should be placed as well under dataset/babel

Thank you! I guess this is solved now. If not, I'll open a new issue.


Pair of websocketd

Hi
I was wondering if I can run one websocketd on one machine at one IP address, and another websocketd on another machine at another IP address -- and push data to and fro. Is this possible? Can I have some starting script for doing this, please?

In order to talk to websocketd you need a client. So if your client is program running under other websocketd it'll work but seem like there are better ways to solve any problems that possibly solved by doing all this dance.
So I'll leave it hanging for comments but would not personally advise pursuing.


Added possible Setting foreign key solution

Would fix issue #115. It's not (yet) a perfect solution and I'm hoping you guys have a look and give some possible improvements on this point. Tested this with the latest commit of the CP Difference plugin.

I will change some things, and will make setSetting and getSetting support foreignKey too, so there will be no need of an extra function.


Nuki Opener timeout after upgrade to 9.03-master8

PROBLEM DESCRIPTION
Timeouts when attempting to open Nuki Opener.
Can't open the intercom door.
All 4 retry attempts appear within 1 second, expecting to delay a bit.
Noticed these errors couple of days after upgrading to #554 ...
nuki/opener/action electricStrikeActuation
nuki/opener/action ack
nuki/opener/commandResult error
nuki/opener/retry 1
nuki/opener/commandResult error
nuki/opener/retry 2
nuki/opener/commandResult error
nuki/opener/retry 3
nuki/opener/commandResult error
nuki/opener/retry 4
nuki/opener/retry failed

REQUESTED INFORMATION

[x] Read the Contributing Guide and Policy and the Code of Conduct
[x] Searched the problem in issues
[x] Searched the problem in discussions
[x] Searched the problem in the docs
[x] Searched the problem in the chat
[x] Device used (e.g., ESP32-S3): ESP32
[x] Nuki Hub binary firmware version number used: 9.03-master8

[x] Pre-compiled
[ ] Self-compiled

[x] Provide the output of http://nukihubIP/info:

------------ NUKI HUB ------------
Version: 9.03-master8
Build:<PHONE_NUMBER>9.169.1
Build type: Release
Build date: 2024-12-03
Updater version: 9.03-master8
Updater build:<PHONE_NUMBER>9.169.1
Updater build date: 2024-12-03
Uptime (min): 84
Config version:<PHONE_NUMBER>
Last restart reason FW: NotApplicable
Last restart reason ESP: ESP_RST_BROWNOUT: Brownout reset (software or hardware)
Free internal heap: 61096
Total internal heap: 260360
PSRAM Available: No
Network task stack high watermark: 7148
Nuki task stack high watermark: 5072

------------ GENERAL SETTINGS ------------
Network task stack size: 12288
Nuki task stack size: 8192
Check for updates: No
Latest version: 9.03-master8
Allow update from MQTT: Yes
Web configurator username: Not set
Web configurator password: Not set
Web configurator enabled: Yes
Publish debug information enabled: No
MQTT log enabled: No
Webserial enabled: No
Bootloop protection enabled: Yes

------------ NETWORK ------------
Network device: Built-in Wi-Fi
Network connected: Yes
IP Address: <IP_ADDRESS>
SSID: MOVISTAR_BD8C
BSSID of AP: 94:83:C4:4F:3D:8E
ESP32 MAC address: 24:6F:28:7C:6C:F8

------------ NETWORK SETTINGS ------------
Nuki Hub hostname: nukihub
DHCP enabled: Yes
RSSI Publish interval (s): 60
Find WiFi AP with strongest signal: No
Restart ESP32 on network disconnect enabled: Yes
MQTT Timeout until restart (s): Disabled

------------ MQTT ------------
MQTT connected: Yes
MQTT broker address: <IP_ADDRESS>
MQTT broker port: 1883
MQTT username: ***
MQTT password: ***
MQTT base topic: nuki
MQTT SSL CA: Not set
MQTT SSL CRT: Not set
MQTT SSL Key: Not set

------------ BLUETOOTH ------------
Bluetooth TX power (dB): 9
Bluetooth command nr of retries: 3
Bluetooth command retry delay (ms): 100
Seconds until reboot when no BLE beacons received: -1

------------ QUERY / PUBLISH SETTINGS ------------
Lock/Opener state query interval (s): 1800
Publish Nuki device authorization log: No
Max authorization log entries to retrieve: 5
Battery state query interval (s): 1800
Most non-JSON MQTT topics disabled: No
Publish Nuki device config: No
Config query interval (s): 3600
Publish Keypad info: Yes
Keypad query interval (s): 1800
Enable Keypad control: Yes
Publish Keypad topic per entry: No
Publish Keypad codes: Yes
Allow checking Keypad codes: No
Max keypad entries to retrieve: 10
Publish timecontrol info: Yes
Keypad query interval (s): 1800
Enable timecontrol control: No
Publish timecontrol topic per entry: Yes
Max timecontrol entries to retrieve: 10

------------ HOME ASSISTANT ------------
Home Assistant auto discovery enabled: Yes
Home Assistant auto discovery topic: homeassistant/
Nuki Hub configuration URL for HA: http://<IP_ADDRESS>

------------ NUKI LOCK ------------
Lock enabled: Yes
Paired: Yes
Nuki Hub device ID:<PHONE_NUMBER>
Nuki device ID: ***
Firmware version: 4.4.9
Hardware version: 7.0
Valid PIN set: Yes
Has door sensor: No
Has keypad: No
Timecontrol highest entries count: 0
Register as: App

------------ HYBRID MODE ------------
Hybrid mode enabled: Yes
Hybrid mode connected: Yes
Sending actions through official MQTT enabled: Yes
Time between status updates when official MQTT is offline (s): 600

------------ NUKI LOCK ACL ------------
Lock: Allowed
Unlock: Allowed
Unlatch: Allowed
Lock N Go: Disallowed
Lock N Go Unlatch: Disallowed
Full Lock: Disallowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed

------------ NUKI LOCK CONFIG ACL ------------
Name: Disallowed
Latitude: Disallowed
Longitude: Disallowed
Auto Unlatch: Disallowed
Pairing enabled: Disallowed
Button enabled: Disallowed
LED flash enabled: Disallowed
LED brightness: Disallowed
Timezone offset: Disallowed
DST mode: Disallowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed
Single Lock: Disallowed
Advertising Mode: Disallowed
Timezone ID: Disallowed
Unlocked Position Offset Degrees: Disallowed
Locked Position Offset Degrees: Disallowed
Single Locked Position Offset Degrees: Disallowed
Unlocked To Locked Transition Offset Degrees: Disallowed
Lock n Go timeout: Disallowed
Single button press action: Disallowed
Double button press action: Disallowed
Detached cylinder: Disallowed
Battery type: Disallowed
Automatic battery type detection: Disallowed
Unlatch duration: Disallowed
Auto lock timeout: Disallowed
Auto unlock disabled: Disallowed
Nightmode enabled: Disallowed
Nightmode start time: Disallowed
Nightmode end time: Disallowed
Nightmode auto lock enabled: Disallowed
Nightmode auto unlock disabled: Disallowed
Nightmode immediate lock on start: Disallowed
Auto lock enabled: Disallowed
Immediate auto lock enabled: Disallowed
Auto update enabled: Disallowed
Reboot Nuki: Allowed

------------ NUKI OPENER ------------
Opener enabled: Yes
Paired: Yes
Nuki Hub device ID:<PHONE_NUMBER>
Nuki device ID: ***
Firmware version: 1.10.1
Hardware version: 4.17
Opener valid PIN set: Yes
Opener has keypad: No
Timecontrol highest entries count: 0
Register as: Bridge
Nuki Opener Lock/Unlock action set to Continuous mode in Home Assistant: No

------------ NUKI OPENER ACL ------------
Activate Ring-to-Open: Allowed
Deactivate Ring-to-Open: Allowed
Electric Strike Actuation: Allowed
Activate Continuous Mode: Allowed
Deactivate Continuous Mode: Allowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed

------------ NUKI OPENER CONFIG ACL ------------
Name: Allowed
Latitude: Disallowed
Longitude: Disallowed
Pairing enabled: Allowed
Button enabled: Allowed
LED flash enabled: Allowed
Timezone offset: Disallowed
DST mode: Disallowed
Fob Action 1: Disallowed
Fob Action 2: Disallowed
Fob Action 3: Disallowed
Operating Mode: Allowed
Advertising Mode: Disallowed
Timezone ID: Disallowed
Intercom ID: Disallowed
BUS mode Switch: Allowed
Short Circuit Duration: Allowed
Eletric Strike Delay: Allowed
Random Electric Strike Delay: Disallowed
Electric Strike Duration: Allowed
Disable RTO after ring: Disallowed
RTO timeout: Disallowed
Doorbell suppression: Allowed
Doorbell suppression duration: Disallowed
Sound Ring: Disallowed
Sound Open: Disallowed
Sound RTO: Disallowed
Sound CM: Disallowed
Sound confirmation: Disallowed
Sound level: Disallowed
Single button press action: Disallowed
Double button press action: Disallowed
Battery type: Allowed
Automatic battery type detection: Allowed
Reboot Nuki: Disallowed

------------ GPIO ------------

I have opened via mobile app and now seems responsive.
Unless there's anything else to check, give me few days to see if this problem reocurrs again.

With the updated libs I also changed the way nuki ble library reconnects with the lock/opener. It tries to do this faster than before by not querying services each time it connects. Might give some issues though when something in the connection goes wrong and then does not recover.
Maybe connecting to the opener through the app disconnected the esp32 and the opener in some way that allows the esp32 to recover the connection afterwards.
Will see about forcing a full reconnect on errors.

The problem repeats after a while, despite I can open with the App and later with Nuki Hub, the same disconnect issue happens again (eg. the next day).

@duhow Is there any change with the 9.04 release?

Still having issues. Even after opening with the app, 2h later I would have issues with the device.
Right now I have unpaired and paired again the device, will report later how it goes...

Please report if this is fixed in 9.05-master4

Not sure if related, but i've updated to 9.05-master4 and after 4+ hours could not get in to the Opener or Lock:
Buzzer MQTT Log changed to nukiTask is running
8:50:43 AM - 1 minute ago
Buzzer MQTT Log changed to networkTask is running
8:50:17 AM - 1 minute ago
Buzzer MQTT Log changed to Result (attempt 1): Result (attempt 2): Result (attempt 3): Result (attempt 4): Query opener state failed
8:50:01 AM - 2 minutes ago
Buzzer MQTT Log changed to nukiTask is running
8:48:43 AM - 3 minutes ago
Buzzer MQTT Log changed to networkTask is running
8:48:17 AM - 3 minutes ago
Buzzer MQTT Log changed to Lock: Maximum number of retries exceeded, aborting.
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 4 of 3
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 3 of 3
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:24 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 2 of 3
8:47:23 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:23 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 1 of 3
8:47:23 AM - 4 minutes ago
Buzzer MQTT Log changed to Lock action result: error
8:47:23 AM - 4 minutes ago

Home Door MQTT Log changed to nukiTask is running
8:50:43 AM - 1 minute ago
Home Door MQTT Log changed to networkTask is running
8:50:17 AM - 2 minutes ago
Home Door MQTT Log changed to Result (attempt 1): Result (attempt 2): Result (attempt 3): Result (attempt 4): Query opener state failed
8:50:01 AM - 2 minutes ago
Home Door MQTT Log changed to nukiTask is running
8:48:43 AM - 3 minutes ago
Home Door MQTT Log changed to networkTask is running
8:48:17 AM - 4 minutes ago
Home Door MQTT Log changed to Lock: Maximum number of retries exceeded, aborting.
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 4 of 3
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 3 of 3
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:24 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 2 of 3
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock: Last command failed, retrying after 100 milliseconds. Retry 1 of 3
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action result: error
8:47:23 AM - 5 minutes ago
Home Door MQTT Log changed to Lock action received: lock
8:47:23 AM - 5 minutes ago

Please report if this is fixed in 9.05-master5. I'm optimistic the issue has been found and addressed.

No retries for me at least, so seems to work for now for both Opener and Lock.

This seems fixed. Please re-open if issues persist on 9.05-master5/9.05-beta1 and up.
In that case please add serial logs


File Acl permissions

Is it possible to add permissions (allUsers:readers) to a file during uploading
var myBucket = gcs.bucket('testbucket');
var file = myBucket.file('test.png');
file.createWriteStream({
	gzip: true,
set permission to allUsers:readers
})

There is, though it's a little more wordy than our API is usually:
file.createWriteStream({
    metadata: {
      acl: [
        {
          entity: 'allUsers',
          role: gcloud.storage.acl.READER_ROLE
        }
      ]
    }
  });

I'm struggling to think of a clean way to make that easier, but if you have any ideas, we will gladly try to accommodate!

I have tried that, but the file gets uploaded and no permissions are set. Here is my modified code
fs.createReadStream('test.png')
			  .pipe(file.createWriteStream({
			  	metadata:{
			  		acl:[
			  		{
			  			entity:'allUsers',
			  			role:gcs.acl.READER_ROLE
			  		}
			  		]
			  	}
			  }
			  ))
			  .on('error', function(err) {
			  	done();
			  })
			  .on('complete', function(metadata) {
					done();

			  });

am i missing something

I don't think so, that looks right to me. Can you paste what metadata returns in the complete callback?
Also, what version of gcloud are you running?

{ kind: 'storage#object',
  id: 'xxxx/temp/test.png/1439816836081000',
  selfLink: 'https://www.googleapis.com/storage/v1/b/xxxx/o/temp%2Ftest.png',
  name: 'temp/test.png',
  bucket: 'xxxx',
  generation: '1439816836081000',
  metageneration: '1',
  contentType: 'image/png',
  updated: '2015-08-17T13:07:16.080Z',
  storageClass: 'STANDARD',
  size: '53844',
  md5Hash: 'zAp5LEFzw2l',
  mediaLink: 'https://www.googleapis.com/download/storage/v1/b/xxx/o/temp%2Ftest.png?generation=1439816836081000&alt=media',
  acl:
   [ { kind: 'storage#objectAccessControl',
       id: 'xxx/temp/test.png/1439816836081000/allUsers',
       selfLink: 'https://www.googleapis.com/storage/v1/b/xxxx/o/temp%2Ftest.png/acl/allUsers',
       bucket: 'xxxx',
       object: 'temp/test.png',
       generation: '1439816836081000',
       entity: 'allUsers',
       role: 'READER',
       etag: 'COjKEAE=' },
     { kind: 'storage#objectAccessControl',
       id: 'xxx/temp/test.png/1439816836081000/user-00b4903770f8e313045586eab55',
       selfLink: 'https://www.googleapis.com/storage/v1/b/xxxx/o/temp%2Ftest.png/acl/user-00b4903770f8e313045586eab55',
       bucket: 'xxx',
       object: 'temp/test.png',
       generation: '1439816836081000',
       entity: 'user-00b4903770f8e313045586eab55',
       role: 'OWNER',
       entityId: '00b4903770f8e313045586eab55',
       etag: 'COjKudiXsMcCEAE=' } ],
  owner:
   { entity: 'user-00b4903770f8e313045586eab55',
     entityId: '00b4903770f8e313045586eab55' },
  crc32c: 'LOOQ==',
  etag: 'COjcCEAE=' }

Am using version 0.18.0

It looks like the right permissions were added:
metadata.acl[0] = {
  // ...
  entity: 'allUsers',
  role: 'READER'
}

How are you verifying the file is not being given the right permissions?

I was accessing it using the console.developers.google.com UI, and i cant set any permissions using it
am getting
Please include at least one owner's permission

However i have tested the actual url and its accessible to the public.

I get the "Please include at least one owner's permission" if I try to remove the owner permission.

After clicking the X next to the owner's permission:

Does your permissions dialog look different than mine?

This is what i get on the permissions dialog (no permissions are listed)

and on the bucket list view

@jgeewax I think you're the resident expert at ACLs. Is there any reason a file would say it uploaded would have this metadata, but then list nothing (see above screenshot)?

Anyone with leads on this issue?

Hmm weird. Is it possible that somehow we're overriding the owner (which should be the service account that uploaded the object) which leads to a weird situation in the UI?

How can I test this case

// @jgeewax

/cc @Capstan : Any idea what's going on here? Apparently the metadata response says it has an owner, but the UI disagrees.... ?

You cannot change the owner of an object. You can only overwrite an object and become the new owner. The UI is being a little simplistic in that being the owner implies having OWNER permission. You can grant other ACL entities OWNER permission, but you cannot remove the owner from the ACL list.
If you provide an ACL list on creation, we will naturally add the current user or service account creating the object to the ACLs.
FTR, use of predefined ACLs works as well.

If you had, for instance, added another entity owner permission, the dialog would have happily allowed you to save. However, GCS would then quietly re-add the original owner back into the ACL. I've filed a bug against the UI for this behavior.

OK, so there's nothing we need to do differently then? We're not
accidentally stripping an OWNER permission away when we shouldn't?

No, I think you are set. If the user tries to remove the OWNER permission, the service will correct them; no need for fancy validation client-side.

@lafama was that information helpful? Are you still having an issue?

@lafama please re-open if this is still an issue.


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.11.14 -> 8.11.15

terraform-ibm-modules/event-notifications/ibm (source)
module
patch
1.10.21 -> 1.10.22

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.11.15
Compare Source
Bug Fixes

deps: update terraform-module (#734) (4699c26)

terraform-ibm-modules/terraform-ibm-event-notifications (terraform-ibm-modules/event-notifications/ibm)
v1.10.22
Compare Source
Bug Fixes

deps: update terraform-module (#306) (fd0ace7)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 3.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Draft of UIKit interop

@dima-avdeev-jb No hurry of course, but is this still being worked on? Awesome work though!

@dima-avdeev-jb No hurry of course, but is this still being worked on? Awesome work though!

Yes, I am still working on it right now.

@Tiebe This PR will be moved to another branch. All this code will be saved.
https://github.com/JetBrains/androidx/tree/dima-avdeev/uikit-interop-3

@Tiebe This PR will be moved to another branch. All this code will be saved. https://github.com/JetBrains/androidx/tree/dima-avdeev/uikit-interop-3

Awesome, sounds good!


Game crashing bug with Flux Networks

Setup I had was power from Immersive Engineering diesel generator to Draconic Evolution energy storage multiblock, output flux plug of that multiblock was the particular item that I interfered at the time of crash.
http://paste.feed-the-beast.com/view/3c267bc5
Could not reproduce the crash, steps were something like this:

mash flux plug's max transfer amount field full of 9's
change name to random name
change ignore limit from false to true
press enter and close the GUI
wait few secs for update (does something funky with max transfer value) see that number was negative, few "MC not respondings" from Windows after that game crashed.

Version fluxnetworks-1.12.2-3.0.1

Couldn't recreate.


Relocations R_PPC_TPREL16_LO and R_PPC_TPREL16_HA unsupported

I'm not sure if this is a wut thing or a devkitPPC thing, but in trying to port some code to wut I've encountered the following errors when creating the rpx file:
ERROR: Unsupported relocation type 72
ERROR: Unsupported relocation type 70
ERROR: fixRelocations failed.

I'm using the CMake toolchain like in the hello_world C++ CMake example. Is the issue above caused by something in my environment?

70 and 72 definitely don't seem like valid relocations - closest I can get is assuming those are hex 70 and 72, which gives R_PPC_EMB_RELST_LO and R_PPC_EMB_RELST_HA - both of which are actually unsupported in elf2rpl. Are you able to share the code you've been working on, some object files (like the .elf cmake generated), or anything else that causes the issue?
If gcc actually generates relst relocations, we'll have to look at adding a special case or translation (or even a hack in devkitPPC).

use SDL2 and https://github.com/rw-r-r-0644/ffmpeg-wiiu will reproduce this error.

The title for this issue seems to be wrong.
According to wut-tools, 70 and 72 is R_PPC_TPREL16_LO and R_PPC_TPREL16_HA.
Those are for the Thread Local Storage ABI and not supported due to missing TLS support.

On my end there are different errors happen:
R_PPC_PLTREL24 (18) and R_PPC_LOCAL24PC (23)
ERROR: Unsupported relocation type 18
ERROR: Unsupported relocation type 23
ERROR: fixRelocations failed.

And ye, I also trying to link the SDL2 thing. Anyway, in addition to that, I do have a large pile of other libraries that are built from the source. I attempted to disable the -fPIC on all of them, but seems that took no effect... :thinking:

On my end there are different errors happen: R_PPC_PLTREL24 (18) and R_PPC_LOCAL24PC (23)
ERROR: Unsupported relocation type 18
ERROR: Unsupported relocation type 23
ERROR: fixRelocations failed.

And ye, I also trying to link the SDL2 thing. Anyway, in addition to that, I do have a large pile of other libraries that are built from the source. I attempted to disable the -fPIC on all of them, but seems that took no effect... 🤔

These relocations are used for position-independent code and are unrelated to TLS and this issue.
It sounds like one of the libraries in your "pile of other libraries" is built using position-independent code. Try a minimal test case only using packages from the pacman repos and see if the issue persists.

Ye, just now I found the last library where -fPIC was been enabled, and I disabled it, and thing got been built finally.


ruff --explain BLE001 wrong

$ ruff --explain BLE001
blind-except

Code: BLE001 (flake8-bugbear)

Message formats:

* Do not catch blind exception: `{name}

says it comes from flake8-bugbear while it comes from https://pypi.org/project/flake8-blind-except/.
I guess it's because of substring matching, where B is sorted before BLE.

\cc @not-my-profile, maybe from a recent refactor?

Ah yes my bad ... fix incoming!

Thanks!


Update build

Drop /vendor.
Update tests to Go 1.15.
Update djfarrelly/maildev to 1.1.0.
Update mixin test for Go 1.16.
Bump Go modules.

 Only bumping to 1.15 for now.

Also, there have been some changes to prometheus/common, so I've held that back.

You can rebase.

Ready for review finally.


Reduce mem overhead 2 electric boogaloo

This is an attempt to address #301.
This change does 2 main things to reduce the memory overhead.

Instead of opening multiple writers for each granule during an insert, we instead only open a single writer per insert and use that writer for all granule writes, resetting it after each granule has been written to. Of note, I initially tried to have the splitRowsByGranule function return map[*Granule][]parquet.Row and have the writers write those rows directly (can see in commit 41b8914). However this resulted in bad profiles being produced, so I'm not entirely sure that didn't work, but if anyone knows that would be an easy win to make this code cleaner.

Instead of holding the open parquet.File inside the SerializedBuffer object we instead just hold the []byte of the file object.

With these changes we see about an order of magnitude reduction in memory overhead.

This does slow down queries due to it needing to read the bytes as the file instead of just accessing them directly, however the slow down doesn't make Parca unusable, and is likely worth the trade off here, and we can make query improvements after this to address the lag. Also noticeably there's a large memory spike during persistence, this will be something to investigate as well.

Latest commit reduces the memory spike by about 1/2

I wonder if we should consider not useing parquet format but the arrow record format instead for in memory

Closing in favor of #189


godot: add mono support

Following the guide https://docs.godotengine.org/en/3.2/development/compiling/compiling_with_mono.html

Motivation for this change
The Godot game engine supports scripting with the C# programming language. However, in order to so it must be compiled with mono support. This pull request adds such an option to the Nixpkgs derivation.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

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

3 packages built:

godot
godot-headless
godot-server

Under 'Editor -> Editor Settings... -> Mono -> Builds' there are two options for building Godot mono projects:

dotnet CLI (default)
msbuild

This package currently works with 'msbuild' but I haven't been able to get it to work with 'dotnet CLI'.
When I manually build from source in a pure nix shell (nix-shell -E '(import <nixpkgs>{}).godot.override { withMono = true; }' --pure) I can get both to work, but when building with nix-build or nixos-rebuild I get the following error:
MSBUILD : error MSB1021: Cannot create an instance of the logger. Bad IL format.
Switch: GodotTools.BuildLogger.GodotBuildLogger,/nix/store/bryyihwav4xpjh9pfrr3wi4h0cwfcm28-godot-3.2.3/bin/GodotSharp/Tools/GodotTools.BuildLogger.dll;/home/leroy/.local/share/godot/mono/build_logs/ec2dfe320f37ca72e3b227f70b743849_Debug

I noticed some differences between the dll produced in the with nix-build and manually under nix-shell:
nix-build:
File Name                       : GodotTools.BuildLogger.dll
Directory                       : /nix/store/79wqr0kcka5d7y7mbbb2ga3h83xzjc7s-godot-3.2.3/bin/GodotSharp/Tools
File Permissions                : r--r--r--
Image File Characteristics      : Executable, No line numbers, No symbols, Large address aware, 32-bit, No debug, DLL
Linker Version                  : 2.31

nix-shell:
File Name                       : GodotTools.BuildLogger.dll
Directory                       : bin/GodotSharp/Tools
File Permissions                : rw-r--r--
Image File Characteristics      : Executable, Large address aware, DLL
Linker Version                  : 48.0

So, I am still working on this one.

Under 'Editor -> Editor Settings... -> Mono -> Builds' there are two options for building Godot mono projects:

dotnet CLI (default)
msbuild

This package currently works with 'msbuild' but I haven't been able to get it to work with 'dotnet CLI'.
When I manually build from source in a pure nix shell (nix-shell -E '(import <nixpkgs>{}).godot.override { withMono = true; }' --pure) I can get both to work, but when building with nix-build or nixos-rebuild I get the following error:
MSBUILD : error MSB1021: Cannot create an instance of the logger. Bad IL format.
Switch: GodotTools.BuildLogger.GodotBuildLogger,/nix/store/bryyihwav4xpjh9pfrr3wi4h0cwfcm28-godot-3.2.3/bin/GodotSharp/Tools/GodotTools.BuildLogger.dll;/home/leroy/.local/share/godot/mono/build_logs/ec2dfe320f37ca72e3b227f70b743849_Debug

I noticed some differences between the dll produced in the with nix-build and manually under nix-shell:
nix-build:
File Name                       : GodotTools.BuildLogger.dll
Directory                       : /nix/store/79wqr0kcka5d7y7mbbb2ga3h83xzjc7s-godot-3.2.3/bin/GodotSharp/Tools
File Permissions                : r--r--r--
Image File Characteristics      : Executable, No line numbers, No symbols, Large address aware, 32-bit, No debug, DLL
Linker Version                  : 2.31

nix-shell:
File Name                       : GodotTools.BuildLogger.dll
Directory                       : bin/GodotSharp/Tools
File Permissions                : rw-r--r--
Image File Characteristics      : Executable, Large address aware, DLL
Linker Version                  : 48.0

So, I am still working on this one.

Closed in favor of https://github.com/NixOS/nixpkgs/pull/177578.


Remove core.byteLength and add await core.stat()

@mafintosh This is ready for review. We should probably bikeshed the format a bit 😄

@mafintosh This is ready for another review.

Love it


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.10.72",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2754fa3b73df7d0ae042f3ed6cfd9df9042f6262"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "2754fa3b73df7d0ae042f3ed6cfd9df9042f6262",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "usb: dwc2: check return value after calling platform_get_resource()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.72 by commit 2754fa3b73df7d0ae042f3ed6cfd9df9042f6262. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001633


[Feature] Create CAA Records programmatically

I was running into problems when creating ACM Certificates, and the solution was to create CAA Records. I'd love to be able to create these programmatically as part of my pulumi codebase.

Hi @gunar
I believe I added this functionality as part of v2.9.0 of pulumi-cloudflare
Do you not seen the ability to do this?
Paul

Hey @stack72, well I can't find any docs nor source code pointing to the "CAA" record type. Maybe I'm missing something?

A CAA record is just another type of Record in Pulumi. I know the following works here:
import * as pulumi from "@pulumi/pulumi";
import * as cloudflare from "@pulumi/cloudflare";

const sampleCaa = new cloudflare.Record("sampleCaa", {
    data: {
        flags: "0",
        tag: "issue",
        value: "letsencrypt.org",
    },
    name: "mydomain.com",
    ttl: 600,
    type: "CAA",
    zoneId: "mydomain.com",
});

We are inheriting the lack of examples from the upstream provider here :/

Oh I hadn't realized there was a data field. The snipped above works! (but I had to remove the key name)
Thank you so much @stack72 — you're awesome!


Workflow fails when a dash ('-') is in the conditional "when" statement

Checklist:

[x] I've included the version.
[x] I've included reproduction steps.
[x] I've included the workflow YAML.
[x] I've included the logs.

Argo version: v2.9.2
What happened:
In a conditional workflow step (one using the "when" attribute), if there is a "-" character in the string value for when:, the workflow will fail.
What you expected to happen:
Strings containing - should be considered valid.
How to reproduce it (as minimally and precisely as possible):
Submit the following workflow:
# Conditionals provide a way to affect the control flow of a
# workflow at runtime, depending on parameters. In this example
# the 'print-hello' template may or may not be executed depending
# on the input parameter, 'should-print'. When submitted with:
#   argo submit examples/conditionals.yaml
# the step will be skipped since 'should-print' will evaluate false.
# When submitted with:
#   argo submit examples/conditionals.yaml -p should-print=true
# the step will be executed since 'should-print' will evaluate true.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: conditional-
spec:
  entrypoint: conditional-example
  arguments:
    parameters:
    - name: should-print
      value: "false"

  templates:
  - name: conditional-example
    inputs:
      parameters:
      - name: should-print
    steps:
    - - name: print-hello
        template: whalesay
        when: "{{inputs.parameters.should-print}} == true-dash-true"

  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [sh, -c]
      args: ["cowsay hello"]
      resources:
        requests:
          cpu: 1000m
          memory: 1Gi
        limits:
          cpu: 1000m
          memory: 2Gi

Workflow fails with the following output (--watch flag passed to argo submit):
Name:                conditional-9bnkg
Namespace:           my-namespace
ServiceAccount:      argo-runner-sa
Status:              Failed
Message:             Failed to evaluate 'when' expresion 'false == true-dash-true': Value 'true' cannot be used with the modifier '-', it is not a number
Created:             Mon Jul 27 15:07:33 -0400 (now)
Started:             Mon Jul 27 15:07:33 -0400 (now)
Finished:            Mon Jul 27 15:07:33 -0400 (now)
Duration:            0 seconds
Parameters:
  should-print:      false

STEP                  TEMPLATE             PODNAME  DURATION  MESSAGE
 ✖ conditional-9bnkg  conditional-example                     Failed to evaluate 'when' expresion 'false == true-dash-true': Value 'true' cannot be used with the modifier '-', it is not a number

Thanks!

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Try quoting? when: "{{inputs.parameters.should-print}} == \"true-dash-true\""?

🤦♂ That works! Thanks @simster7 If it's a small fix though it might still be nice to support dashes in strings without the escaped quotes since the following seems non-obvious:
This works:
when: "{{inputs.parameters.should-print}} == myvalue"

But this doesn't:
when: "{{inputs.parameters.should-print}} == my-value"

The library that evaluates these expressions actually requires quotes, but we as a convenience allow them to be omitted, so that they don't interfere with the overlapping quotes of the when field. Unfortunately, this is the other side of the coin.


Internet is not enabled

The library works great when internet is enabled, but if I turn off the internet, it goes into onDroidSpeechError "Internet is not enabled".
I think it internally uses google voice typing. I have the English US voice language package installed in my device for offline recognition. Still it shows the error and doesn't work.
Is there any fix to this?

This is more of an enhancement, as the default way this library works is only if internet is enabled. I can add this enhancement to the library, but it would take some time probably by this weekend.

Hi Vikram,
You did a great job out there !!! I am sure, so many people are not aware of this library.
I have been searching for this kind of setup from so long and now I found your solution. I have 2 questions in the current setup,

Is it a free library? If yes how can I keep the whole library in my git-repos and ink with my project (May be silly doubt but I am not sure how to do such thing)?
Can I change the language and accent (telugu, hindi, EN-us,uk and so on..)? If yes, your idea/suggestion will be much appreciated.
Will be waiting for your answer...  :) :)
Thanks,
Sateesh G

@punittt Added offline recognition feature #420
@Gsateesh Yes it is a free library and you can set specific languages as long it is supported by google. For more info please have a look at the wiki.


Allow a 'verbose' flag for raise_for_status()

raise_for_status() is super awesome, but a lot of the time, the error code and message is not informative enough to assist with debgugging when an exception is raised. It would be nice to have a verbose flag for raise_for_status that would also print the response body, where more details are often included. I would be happy to work on this, but wanted to make sure it is not already in the works.

If you do:
import requests

r = requests.get(url)

try:
    r.raise_for_status()
except requests.exceptions.HTTPError as error:
    print(error)
    print(error.response.text)

We don't print the body (and likely won't add it, even as a flag) for several reasons:

It may not exist (and therefore wouldn't be helpful)
It could be plain binary data which will certainly not help anyone
It could have characters that cannot be printed (and will cause even more problems)

You can certainly do this yourself and based on some searches on StackOverflow and our issues, it doesn't seem like anyone has had the need for this before.
I'm -0.5 if only because verbose would obviously default to False.

Thanks for the quick response @sigmavirus24. That makes a lot of sense. I was thinking that a verbose flag would avoid the need for the try/except structure, but it is simple enough to a make a little helper function that processes the request and does that. Thanks again! Please go ahead and close this out.

Verbose flag would be very nice


Create a component to provide styling options for feature layers in globe

We should reuse component created for map in https://github.com/kalisio/kdk/issues/110. Depending on the 2D/3D mode the underlying configuration changes to match Leaflet/Cesium descriptors (see e.g. Kano iframe sample).

[ ] Default visibility + near/far distance (https://cesium.com/docs/cesiumjs-ref-doc/DistanceDisplayCondition.html)
[ ] Markers icons - Cesium only supports Maki icons on billboards, for more customization we can also use a link to an external URL for the billboards.
[ ] Linear & Polygons - options should include the main properties available to colorize linear and polygons: line color, line width, fill color - See https://cesiumjs.org/Cesium/Build/Documentation/PolygonGraphics.html for reference in Cesium.
[ ] Clustering - basic options should be provided for billboards as we rely on built-in Cesium capabilities.
[ ] Popups
[ ] Tooltips
[ ] Infobox

Partially adressed by https://github.com/kalisio/kdk/issues/816.


Add extra dictionary support

Requires at least hunspell version 1.3.4 see the commit when this interface was introduced. I don't know whether there is a way to attach the function only for specific versions of hunspell.

A similar situation and a workaround came up in an early ruby-ffi discussion. I'll add another commit to use this approach.

When FFI attempts to bind a function that doesn't exist, it raises a FFI::NotFoundError exception. You could catch that when attaching the additional functions, and fail silently?

@cdchapman, thank you, this is exactly functionality that I need!
@postmodern, what should be done yet in this PR to get it merged?
One more idea for ease of use is to make add_dic to search for dictionaries in Hunspell.directories as FFI::Hunspell::Dict.open method does to ease of adding other languages dictionaries.
My use case: I want to check words with russian, english and my custom dictionary (with my domain words).
For now with the code from this pull request I can do it as:
require 'ffi/hunspell'
dict = FFI::Hunspell.dict('ru_RU')
dict.add_dic('/usr/share/hunspell/en_US.dic') # ← I want it to be just en_US, I don't want to stick to any one path (which is differs between distros, etc)
dict.add_dic('/home/envek/evl.ms/ebay.ru/misc/hunspell.dic') # dxg/MS is here

# Usage:
dict.check?('собака'.encode(dict.encoding)) # => true
dict.check?('dog'.encode(dict.encoding)) # => true
dict.check?('dxg'.encode(dict.encoding)) # => true

I can continue work on this PR with your permission. WDYT?

Sorry for the delay. Only one minor issue, but this looks ready to be merged.

Hi @Envek. Sorry for the delay. It would not make sense to use the russian affix file, for example, with the en_US dictionary because the affixes for each language mean different things. Extra dictionaries reuse the affix file from the main dictionary. See hunspell/hunspell#348.
A better approach would be the following:
require 'ffi/hunspell'
dict = FFI::Hunspell.dict('ru_RU')
dict = dict.add_dic('/full/path/to/russian_medical_words.dic') #

english_dict = FFI::Hunspell.dict('en_US')
english_dict.add_dic('/full/path/to/custom.dic') # dxg/MS is here

# Usage:
dict.check?('собака'.encode(dict.encoding)) # => true
dict.check?('полиглактином'.encode(dict.encoding)) # => true
english_dict.check?('dog'.encode(dict.encoding)) # => true
english_dict.check?('dxg'.encode(dict.encoding)) # => true

It is useful anyhow to know what language is being checked. An application could guess using some sort of heuristics, but it is good to be explicit about the guessing because it may choose the wrong dictionary.

Yes, I figured that and finally I did exactly this: have two main dictionaries for every language and two additional dictionaries (one for each language).
But anyway this PR is still needed.

Been busy at work. Finally got around to working on ffi-hunspell. Merged and will be in 0.6.0.

Is it possible by chance to release a new version to offer this new feature?


Rewards Update

Hello!,
I do not know what creates the problem, but occurred after update and change the ticket page.
Thanks for the great work.

i have issues also, i hope he updates soon to fix ill the issues

Hello,
They've changed the whole layout of the page, I have to start from scratch.
I'm rolling up next version (1.5) tomorrow.

Hello, I've got news about the update:
I reworked the interface of the page (removed stream, ads & useless stuff). Here is what it looks like:

Hello fellow farmers,
I didn't have time to code the new update these last days. If you want you can try out the new update "as-is" by installing the script from the /dev branch. By doing this you'll be able to test the script and communicate me bugs or suggestions!
Hope you'll like this update.

Hi, I'm rolling out 1.5 update, this issue will be closed.


Gstreamer: 1.14.0 -> 1.14.2

Motivation for this change
I could not run nox-review wip, as the resulting nix-build used more than 20GB of RAM...
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build gst_all_1

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: gst_all_1
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: gst_all_1
Partial log (click to expand)
/nix/store/d8pgp7xg5mgzzxin4hvnmrdxzdql1ip5-gst-libav-1.14.2
/nix/store/mhwi7pq77crni86s5m9f37lipmjl70sa-gst-plugins-bad-1.14.2
/nix/store/737vicn1g70ixa95i8pwkizyfgn083dy-gst-plugins-base-1.14.2
/nix/store/r7gpqcd50bkxkwys5gk7m3a9lqlwd1kq-gst-plugins-good-1.14.2
/nix/store/rk5amg70chfnrsi40j53va122vqr4fg3-gst-plugins-ugly-1.14.2
/nix/store/5rsyz70h5ayqqnb4ywm1fjbzn9w7iix6-gst-rtsp-server-1.14.2
/nix/store/fn24lambaza48ja3fgrdmjr1jp6335qn-gst-vaapi-1.14.2
/nix/store/kic46a4n22c4xlppmvvf00hr3h8zyhsv-gst-validate-1.14.2
/nix/store/3wfvnh8l12wjrd266061dr60wipf7x9i-gstreamer-1.14.2
/nix/store/55m0s87wkgdsaccsrhp8553v0j914gh6-gstreamermm-1.10.0

Success on aarch64-linux (full log)
Attempted: gst_all_1
Partial log (click to expand)
/nix/store/a0ja23qg337sxvk3f3ivvrfz70jlwvml-gst-libav-1.14.2
/nix/store/sbl5pq0qs7wdchyw218l34halap9a7zm-gst-plugins-bad-1.14.2
/nix/store/qmlbkvwwci616kpd0qmzgrxm7kjlzwlm-gst-plugins-base-1.14.2
/nix/store/sh4n3hzfzm9cihvi15xchvpv9v2ic2hh-gst-plugins-good-1.14.2
/nix/store/z60k5dc62vhm1akzlcrx9jp85p9kbc3s-gst-plugins-ugly-1.14.2
/nix/store/prvfb2m7f1gqlmqzibv66yq4vmv495ya-gst-rtsp-server-1.14.2
/nix/store/96k7aiaz9xvycl5fw3lbly7fls2i6r3x-gst-vaapi-1.14.2
/nix/store/q4dl7dkqp3chwxmcgc83rzkdz7qhkfaf-gst-validate-1.14.2
/nix/store/8gjqj1cpvrzalqs9b7yjmdf78ijfmjnk-gstreamer-1.14.2
/nix/store/46m95r7pvr08bzxgx8fi0ysfzs9bc8lh-gstreamermm-1.10.0

@vcunat will you merge this?

Should go in staging i think.

@matthewbauer is staging-next the correct one?

Yep that should work

Unless it's a security fix, changes should go to staging and not directly staging-next.

Yes, things are merged to staging instead, at least generally.

Is there any documentation, which pull request should end in which branch? I find it very confusing.

There's an RFC only so far: https://github.com/NixOS/rfcs/pull/26 but that part about where to merge seems to have worked well in the past few months that we're trying the workflow.

Okay, ty :)


KAFKA-18024 ConcurrentModificationException in Kafka OffsetFetcher - Proposal for Thread-Safety Fix - Update OffsetFetcher.java

KAFKA-18024 ConcurrentModificationException in Kafka OffsetFetcher - Proposal for Thread-Safety Fix
replaced HashMap with ConcurrentHashMap to ensure thread safety during concurrent modifications
More detailed description available in KAFKA-18024
All tests before and after the change pass in the same way. Unfortunately, I did not add additional tests specifically for this change, as it is difficult to test this type of modification.
Committer Checklist (excluded from commit message)

[x] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@kamalcph

Thanks for the patch, LGTM. The traversal and removal of entries from Map can happen concurrently due to retries.
@chia7712 Could you please take a second look? Thanks!

@mimaison @frankvicky @FrankYang0529 @gongxuanzhang @chia7712 Can you please take a second look?

@lianetm—IIRC, you looked at the offset fetch logic a fair amount in the past. Pinging you so you can weigh in (if you want).


sometimes qemu start failed (or serial port interrupted) when the kernel initialize serial device

This issue listed two cases:

The first case is described in hyperhq/hyperstart#285 and fixed in hyperhq/hyperstart#286

'TestSuite.TestSendContainerSignal' failed to end as attached.
In the test matrix, it's high probability there are one job (and only one) out of five jobs failed. And if > restart the job, it will pass.
log-toolong.txt

The second case is qemu stop/interrupted when guest initializing serial device.

And the remain disscussion of this thread is about the second case.

I0317 10:34:55.297563   23218 decommission.go:544] Pod[busybox] got vm exit event
I0317 10:34:55.297575   23218 decommission.go:592] Pod[busybox] umount all containers and volumes, release IP addresses
I0317 10:34:55.297588   23218 etchosts.go:97] cleanupHosts /var/lib/hyper/hosts/busybox, /var/lib/hyper/hosts/busybox/hosts
I0317 10:34:55.297616   23218 etchosts.go:101] cannot find /var/lib/hyper/hosts/busybox/hosts
I0317 10:34:55.297708   23218 decommission.go:572] Pod[busybox] sandbox info removed from db
I0317 10:34:55.297719   23218 decommission.go:577] Pod[busybox] tag pod as stopped
I0317 10:34:55.297726   23218 decommission.go:584] Pod[busybox] pod stopped
I0317 10:34:58.021414   23218 json.go:521] get hyperstart API version error: send ctl channel error, the hyperstart might have closed
E0317 10:35:19.764693   23218 hypervisor.go:49] SB[vm-QeEPbljMVQ] watch hyperstart timeout

another case, on TestSuite.TestCreateAndStartPod
log-toolong-1.txt

another similar one on TestSuite.TestRenameContainer
log-toolong-2.txt

I think it's more or less related with the hyperstart protocol handling, at least, it should not stall here if the protocol state machine transits to an illegal state. @laijs could you check this one?

looks the serial port disconnected while the kernel init the serial device...
I0316 16:48:30.441463   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] virtio-pci 0000:00:02.0: virtio_pci: leaving for legacy driver
I0316 16:48:30.447921   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
I0316 16:48:30.448010   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] virtio-pci 0000:00:03.0: virtio_pci: leaving for legacy driver
I0316 16:48:30.453452   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
I0316 16:48:30.453663   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver
I0316 16:48:30.458682   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
I0316 16:48:30.459030   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] virtio-pci 0000:00:05.0: virtio_pci: leaving for legacy driver

Based on the console message, Interrupt here, do you have any ideas @bergwolf @gao-feng ?
I0316 16:48:30.465716   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
I0316 16:48:30.489577   23090 vm_console.go:46] SB[vm-CRDiGlKuWp] [CNL] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A

the #554 is the same problem.
log-test-stopped.txt

not quite sure if this bug is fixed by https://github.com/golang/go/commit/5bcdd639331cd7f8d844fd38a674c4751423f938

@gao-feng go 1.8 only?

we would never read with zero length buffer:
        buf := make([]byte, 512)
        res := []byte{}
        for read < needRead {
                want := needRead - read
                if want > 512 {
                        want = 512
                }
                nr, err := conn.Read(buf[:want])

looks this commit is included in both 1.7 and 1.8.

The qemu in travis testing is 2.0.0

The qemu in jenkins belongs to ubuntu 16.04, and version is 2.5. This issue spread in both 2.0 and 2.5, and should be a guest kernel issue?

some cases from Jenkins

http://ci.hypercontainer.io:8080/job/hyperd-auto/304/console
http://ci.hypercontainer.io:8080/job/hyperd-auto/302/console

I checked about 20 recent build failures, all of this cases were happened with libvirt driver, and no qemu driver meet the init interrupt problem.

libvirt ended up using qemu command line:
-chardev socket,id=charchannel0,path=/var/run/hyper/vm-vBrtiilBzU/hyper.sock,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=sh.hyper.channel.0
while qemu driver uses:
-serial unix:/var/run/hyper/vm-UGcRAJrPUR/console.sock,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charch0,id=channel0,name=sh.hyper.channel.0

full command lines comparison.
libvirt:
/usr/bin/qemu-system-x86_64 -name vm-lWRHQAOeCW -S -machine pc-i440fx-2.0,accel=tcg,usb=off -cpu Broadwell,+abm,+pdpe1gb,+hypervisor,+rdrand,+f16c,+osxsave,+ss,+vme -m 128 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid f2728ef7-a964-47ce-8f8e-e45703988361 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-vm-lWRHQAOeCW/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-reboot -boot strict=on -kernel /var/lib/hyper/kernel -initrd /var/lib/hyper/hyper-initrd.img -append console=ttyS0 panic=1 no_timer_check -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x3 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x2 -fsdev local,security_model=none,id=fsdev-fs0,path=/var/run/hyper/vm-lWRHQAOeCW/share_dir -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=share_dir,bus=pci.0,addr=0x4 -chardev socket,id=charserial0,path=/var/run/hyper/vm-lWRHQAOeCW/console.sock,server,nowait -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/run/hyper/vm-lWRHQAOeCW/hyper.sock,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charchannel1,path=/var/run/hyper/vm-lWRHQAOeCW/tty.sock,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=sh.hyper.channel.1 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on
qemu:
/bin/qemu-system-x86_64 -machine pc-i440fx-2.0,usb=off -cpu core2duo -kernel /var/lib/hyper/kernel -initrd /var/lib/hyper/hyper-initrd.img -append console=ttyS0 panic=1 no_timer_check -realtime mlock=off -no-user-config -nodefaults -no-hpet -rtc base=utc,driftfix=slew -no-reboot -display none -boot strict=on -m 128 -smp 1 -qmp unix:/var/run/hyper/vm-oXLmDUBhSp/qmp.sock,server,nowait -serial unix:/var/run/hyper/vm-oXLmDUBhSp/console.sock,server,nowait -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x3 -chardev socket,id=charch0,path=/var/run/hyper/vm-oXLmDUBhSp/hyper.sock,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charch0,id=channel0,name=sh.hyper.channel.0 -chardev socket,id=charch1,path=/var/run/hyper/vm-oXLmDUBhSp/tty.sock,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charch1,id=channel1,name=sh.hyper.channel.1 -fsdev local,id=virtio9p,path=/var/run/hyper/vm-oXLmDUBhSp/share_dir,security_model=none -device virtio-9p-pci,fsdev=virtio9p,mount_tag=share_dir -daemonize -pidfile /var/run/hyper/vm-oXLmDUBhSp/pidfile -D /var/log/hyper/qemu/vm-oXLmDUBhS.log

didn't happen in recent Hykins, but still in travis, such as:
log-serial.txt

PRs for hyperd/runv travis are not merged yet
https://github.com/hyperhq/hyperd/pull/611
https://github.com/hyperhq/runv/pull/493

hykins/travis both use in-house built qemu now. Reopen if this is seen again.


Better handling of unhygienic header files

Ok, now instead of using macro definitions from one header file per dependency, we need to create begin/end header pairs and include them. This brings an additional flexibility i.e. we can #undef symbols which is what we want. Things look good to me:) Maybe @est77 should take a look too?

Exactly! Thanks for the review. If it looks good to you then it's fine :)


Are you training the entire YOLO network or freezing the first few layers and just training the last few layers ?

https://github.com/AlexeyAB/darknet#how-to-improve-object-detection Freezing the first few layers. This readme helps!

Hi @alexcdot, I am new to YOLO and much appreciated it if you could give me some pointers on how to freeze the first few layers for transfer learning and what to add in the yolov4-custom.cfg please. Thanks so much.

https://github.com/AlexeyAB/darknet#how-to-train-to-detect-your-custom-objects this section of the readme provides a step-by-step

@alexcdot, thanks for pointing it out and I am following the step-by-step tutorial. I have one question here that I would like to seek clarification on. After training on the custom dataset: cargo containers, cranes, etc (labels not found in the coco dataset) using the pre-trained weights yolov4.conv.137, will the _best.weights file be able to detect classes found in the coco dataset as well, i.e., person, cars, etc? Or it will just detect the custom dataset labels only?

It will only detect the custom dataset labels only. To detect the coco dataset classes, you could either just run a separate, pre-trained YOLO model, or retrain with the COCO dataset


hasClass returns false unexpectedly in v3

Hi!
I have the following piece of code (simplified), in my Jest/Enzyme based test suite:
    it('toggles calendar visibility on label click', () => {
        const component = (
            <DatePicker />
        );

        const datePicker = mount(component).find('.DatePicker');

        // Opening
        datePicker.find('.DatePicker__button').simulate('click');

        console.log(datePicker.getDOMNode().className);
        console.log(datePicker.hasClass('open'));

        expect(datePicker.hasClass('open')).toBe(true);

        // Closing
        datePicker.find('.DatePicker__button').simulate('click');

        expect(datePicker.hasClass('open')).toBe(false);
    });

I'm getting false on hasClass unexpectedly. The two console.logs I have in the code return as follows:

I've tried multiple combinations, like datePicker.getDOMNode().hasClass but these are not working either.
Thanks in advance for help!

Your simulate call isn't rerendering the wrapper; try datePicker.update() after each mutation.

you'll actually need to not call datePicker.update() but instead do:
const wrapper = mount(component);
const getDatePicker = () => wrapper.find('.DatePicker');

and do wrapper.update() and getDatePicker() afterwards or something like that. .update() should be called on the root.

Hmmm... So I got to this point, but I'm still unable to get expected results. Interestingly, the first expect() passed without an issue. The second, however, did not. Here's how it looks right now:
    it('toggles calendar on label click', () => {
        const testDate = new Date(2016, 0, 1);

        const component = (
            <DatePicker
                period="days"
                value={testDate}
            />
        );

        const mountedComponent = mount(component);
        const getDatePicker = () => mountedComponent.find('.DatePicker');

        // Opening
        getDatePicker().find('.DatePicker__button').simulate('click');
        mountedComponent.update();

        expect(getDatePicker().hasClass('open')).toBe(true);

        // Closing
        getDatePicker().find('.DatePicker__button').simulate('click');
        mountedComponent.update();

        console.log(getDatePicker().getDOMNode().className);
        console.log(getDatePicker().hasClass('open'));

        expect(getDatePicker().hasClass('open')).toBe(false);
    });

...and here's what the new console.logs are saying:

hmm. that is strange. Do you think you'd be able to provide a minimal repro in the form of a test or something?

Sure thing. I'll get back to you!

Could this be related to #1163? I'm seeing some interesting failures along these lines. If you were to console.log(getDatePicker().html() I think you'll find that the element does have the 'open' class.

I'm having the same issue. And it seems .update() doesn't always rerender, or at least doesn't rerender with the updated state for one of its children

I hope I'm on the same page here, but it seems like this isn't even related to dynamic updating of the component. mount and shallow show different behaviours.
With this test case I get one pass and one fail.
repro.test.jsx
import {mount, shallow} from 'enzyme'
import React from 'react'

const Comp = () => {
    return (

Hello world

    )
}

test('It finds the className on the mount()\'d wrapper', () => {
    const mountWrapper = mount(<Comp />)
    expect(mountWrapper.hasClass('test')).toBe(true)
})

test('It finds the className on the shallow()\'d wrapper', () => {
    const shallowWrapper = shallow(<Comp />)
    expect(shallowWrapper.hasClass('test')).toBe(true)
})

npm test -- repro

 FAIL  ./repro_test.js
  ● It finds the className on the mount()'d wrapper

    expect(received).toBe(expected)

    Expected value to be (using ===):
      true
    Received:
      false

      at Object.<anonymous> (repro_test.js:14:43)
          at Promise (<anonymous>)
      at Promise.resolve.then.el (node_modules/p-map/index.js:42:16)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)

  ✕ It finds the className on the mount()'d wrapper (21ms)
  ✓ It finds the className on the shallow()'d wrapper (4ms)

@antonyoneill's https://github.com/airbnb/enzyme/issues/1177#issuecomment-332658634 was correct for me; .hasClass failed, but dumping .html() shows that the expected class does actually show up.  Tweaking things to instead do .render().hasClass() instead of just .hasClass() then has the tests passing.

The problem seem to be with mount in general, not especially with hasClass or setState, ...
Even forcing an update of the wrapper doesn't make it to rerender with the updated data (or to rerender at all).
I didn't notice any issue with shallow.

Also, the v15 adapter and v16 gives different results as well. I upgrade to enzyme 3 with v15, then I'm trying to switch to v16, and some of my tests are failing again. All are using mount, and it seems it's always that the component should be updated but it's not the case. Calling .update() doesn't solve anything.

I have this issue as well:
Doesn't work:
 const dropDown = mount(<DropdownContainer {...defaultProps} />);

  expect(dropDown.hasClass('sg-dropdown--opened')).toEqual(false);
  expect(dropDown.state('isOpened')).toEqual(false);

  dropDown.simulate('click');
  expect(dropDown.hasClass('sg-dropdown--opened')).toEqual(true);
  expect(dropDown.state('isOpened')).toEqual(true);

  dropDown.simulate('click');
  expect(dropDown.hasClass('sg-dropdown--opened')).toEqual(false);
  expect(dropDown.state('isOpened')).toEqual(false);

And this one works:
 const dropDown = mount(<DropdownContainer {...defaultProps} />);

  expect(dropDown.hasClass('sg-dropdown--opened')).toEqual(false);
  expect(dropDown.state('isOpened')).toEqual(false);

  dropDown.simulate('click');
  expect(dropDown.find('.sg-dropdown').hasClass('sg-dropdown--opened')).toEqual(true);
  expect(dropDown.state('isOpened')).toEqual(true);

  dropDown.simulate('click');
  expect(dropDown.hasClass('sg-dropdown--opened')).toEqual(false);
  expect(dropDown.state('isOpened')).toEqual(false);

@elyobo @antonyoneill mine doesn't even get the class to show up when i do html();
using:
@types/enzyme 3.1.0
enzyme 3.1.0
@types/jest 21.1.4
enzyme-adapter-react-16 1.0.2
@types react 16.0.14

also if i'm using typescript does @types/enzyme take priority over the regular enzyme?

Hi All, any update on this?

Hi All, Getting the same error for finding the classname and it returns false even though the class exists. Any update on this?

Also stucked on this bug...
This is not working :
`
it('should change state when toggle cart description view', () => {
const component = ();
const descriptionDiv = component.find('div#description-view');
expect(descriptionDiv.hasClass('selected')).toBeFalsy();
descriptionDiv.simulate('click');
expect(descriptionDiv.hasClass('selected')).toBeTruthy();
descriptionDiv.simulate('click');
expect(descriptionDiv.hasClass('selected')).toBeFalsy();
});
`
=> output
Expected value to be truthy, instead received       false
To fix it I had to chain a find + hasClass on the shallow element (so multiplying selector's calls) :
`
it('should change state when toggle cart description view', () => {
const component = shallow();
const descriptionDivId = 'div#description-view';
const descriptionDiv = component.find(descriptionDivId);
expect(component.find(descriptionDivId).hasClass('selected')).toBeFalsy();
descriptionDiv.simulate('click');
expect(component.find(descriptionDivId).hasClass('selected')).toBeTruthy();
descriptionDiv.simulate('click');
expect(component.find(descriptionDivId).hasClass('selected')).toBeFalsy();
});
`

I believe this is actually caused by #1153, and that a wrapper.update() after each change currently would address it.

@davemcg3 if you could file a new issue with repro code, we can narrow down if it's an expected difference or a bug :-)

I believe this is actually caused by #1153, and that a wrapper.update() after each change currently would address it.

@ljharb Please don't close issues because of expectations and predictions.
wrapper.update() not helping. It's happening for me now. Here is test sample. Thanks.
test('Should set size', () => {
   const wrapper = mount(<Toggle size="medium" />)
   wrapper.update() // not helping 👎
   console.log(wrapper.html()) //

 ✅
   console.log(wrapper.getDOMNode().className) // toggle medium ✅
   expect(wrapper.hasClass('toggle medium')).toBeTruthy() // Failed 🤬
)

@renjithspace please don't tell me how to maintain my projects :-) this issue was closed over 2 years ago. If you'd like help, please file a new issue, and fill out the issue template (including, provide the code for Toggle).
Separately, a wrapper.update() is always a noop right after a mount/shallow, because there's nothing to update. Updating happens after a change (if you make an async change in your component, and there's no better way to write the component, then you have to find a way for your test to get at the Promise for the change so it can await it)

@ljharb got it. And I'm sorry, I didn't mean to be disrespectful.


(BKR-505) rescue SkipTest in confine_block

Prior to this, use of confine_block would result in all following code in the test case being skipped in situations where the host list had no matches for the confine_block.  The entire purpose of confine_block is to limit the scope of the confine to the passed block.
Also, ensure and rescue at the method level do not require an additional wrapping begin..end block.
This was tested locally against the acceptance test suite still in development (and currently partially blocked by this bug) at https://github.com/puppetlabs/beaker/pull/930
/cc @puppetlabs/beaker @justinstoller

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1470/
Test FAILed.

I have added acceptance tests for #confine_block here which also expose the bug and verify the fix.
:eyes:

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1474/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1475/
Test FAILed.

Failure unrelated to patch.


TextArea - Options like (Select|Copy|Paste) not translated

hi all,
I use inside my form the TextArea Element, but on our german iPhones the options like (Select|Copy|Paste) are not translated, how can I manage it?
Thanks,
Ben

https://github.com/GeekyAnts/NativeBase/blob/master/ISSUE_TEMPLATE.txt


Fix/382 boto3

I just rebase my branch that are fixing the unit test on yours, you should be able to merge your PR https://github.com/kevin1024/vcrpy/pull/411 then :)
FIY, the CI run on my github project : https://travis-ci.org/arthurHamon2/vcrpy/builds/546409245

I just looked at tests! Thank you!
I'll look into it as soon as I can.


ReferenceError: __decorate is not defined (1.0.18 on SystemJS)

I've been trying the latest release of ng2-bootstrap (1.0.18) with my angular-cli based project, thus running SystemJS. As soon as I use any component, it fails with the above error ReferenceError: __decorate is not defined:
zone.js:461 Unhandled Promise rejection: ReferenceError: __decorate is not defined
	    at eval (http://localhost:4200/vendor/ng2-bootstrap/components/datepicker/datepicker-inner.component.js:236:5)
	    at Object.eval (http://localhost:4200/vendor/ng2-bootstrap/components/datepicker/datepicker-inner.component.js:326:2)
	    at eval (http://localhost:4200/vendor/ng2-bootstrap/components/datepicker/datepicker-inner.component.js:329:4)

The exact line where it fails is:
__decorate([
        core_1.Input(),
        __metadata('design:type', String)
    ], DatePickerInnerComponent.prototype, "datepickerMode", void 0);

When looking at the sources from the release, it looks like the __decorate helper generation has been removed from the output javascript files.
When I compare the generated .jsfiles from 1.0.18 and 1.0.17, I can see that the __decorate helper function has disappeared in the files header.
I believe the culprit is this line:
    "noEmitHelpers": true,

This seems to assume the __decorate function would be provided upstream by some sort of other dependency. For some reason, the __decorate function isn't available within the SystemJS environment boostrapped by the angular-cli project. When I look at the .js files generated for my own sources, the __decorate function is always generated in the beginning of each file using decorators (for example, @Input).
Is there a particular reason why noEmitHelpers has been switched on in this commit?

it seems i have this problem also. Here is my error trace.
zone.js:461 Unhandled Promise rejection: ReferenceError: __decorate is not defined 	    at eval (http://localhost:4200/vendor/ng2-bootstrap/components/accordion/accordion.component.js:30:5) 	    at Object.eval (http://localhost:4200/vendor/ng2-bootstrap/components/accordion/accordion.component.js:46:2) 	    at eval (http://localhost:4200/vendor/ng2-bootstrap/components/accordion/accordion.component.js:49:4) 	    at eval (http://localhost:4200/vendor/ng2-bootstrap/components/accordion/accordion.component.js:50:3) 	Evaluating http://localhost:4200/vendor/ng2-bootstrap/components/accordion/accordion.component.js 	Evaluating http://localhost:4200/vendor/ng2-bootstrap/components/accordion.js 	Evaluating http://localhost:4200/vendor/ng2-bootstrap/ng2-bootstrap.js

@davidmarquis @matthewdaniel There was a messed up tsconfig.json, but this is fixed in the 1.0.20.

@Dinistro Thanks for the quick update!


loadingKey for Mutations?

I saw loadingKey for queries. But couldn't find it for mutations. Is it possible? I tried inside the code, but not working

https://github.com/Akryum/vue-apollo/issues/23


Support CtrlP's MRU mechanism

vim-startify is a great plugin, but it uses the same MRU mechanism as standard vim (i.e. the viminfo file), not the ~/.cache/mru/cache.txt information used by CtrlP. This leads to an inconsistency between the files listed by :CtrlPMRU and vim-startify. It would be great if vim-startify had an option to use CtrlP's cache instead.
If I get some time, I might look at creating a patch for this, but would welcome your comments.

I never really used ctrlp, but I'm looking into it.

I merged that into master now. Tell me if it works good enough for you.

I'm a little confused; the last changes on master seem to be 9 days ago? Not sure what you've changed?
To answer your previous question, I don't think it's quite that simple. Something strange is certainly going on for me. When I open vim with vim-startify, typically I'm only seeing one file in the recent files list, even though my ~/.vim/.viminfo shows 10 file marks and I've been using vim for some time (so you'd expect loads of recently used files - I assume it's the section marked "File marks: " which is relevant, correct?). So even ignoring CtrlP, something isn't right.
In fact, I think I may have figured out (partly) what's going on. Although I configure a different location for my .viminfo in my ~/.vimrc:
set viminfo='20,s10,/20,:50,h,n~/.vim/.viminfo

it seems that vim-startify ignores that and uses ~/.viminfo instead. I think vim ignores that when it writes to .viminfo and writes to mine, though. I think that may be causing the inconsistency I'm seeing.
Any thoughts?

The only time the plugin interacts with viminfo is by reading the internal variable v:oldfiles (:echo v:oldfiles). That variable gets filled at start and the viminfo file gets written at exit of Vim. So, when you opened some files and called :Startify, you wouldn't see the most recently opened files, because v:oldfiles doesn't get updated on-the-fly. The latest commit (was commited 9 days ago in a testing branch and merged into master yesterday) kind of fixes that issues by prepending newly opened files to v:oldfiles, so :Startify should always show the real recently used files.

Feel free to reopen, if you think there is something that should be changed in the plugin. :)


[SPARKTA-339] [SPARKTA-311] [SDK] [AGGREGATOR] [PLUGINS] [DRIVER]  Outputs by Cube and Write Cube

Description
All the logical that create dataFrames now are inside the aggregator module, this process is more efficient because we generate the dataFrame for each calculation in the cube, before we transform the DStream and then filter the DStream, this suffle and transformation process are omitted.
The schema generation is calculated in one site, when the policy are received in the SparktaJob, this sequence of schemas for each cube are heredated for all classes and objects. Before we have more logical on the output, and this is not their responsability.
Some functions are refactored and deleted.
In the CubeModel we have more options:
writer: {
outputs: ["cassandra", "mongo"]
fixedMeasure: "name:value"
dateType: "long"
isAutoCalculatedId: true
}
Test
All passed.
Some test are added for the new functions and classes.

++++1

test-at ISocketOMongoFiltersJsonIT fails


gi-crystal: 0.21.0 -> 0.22.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hugopl/gi-crystal/releases.
meta.description for gi-crystal is: GI Crystal is a binding generator used to generate Crystal bindings for GObject based libraries using GObject Introspection.
meta.homepage for gi-crystal is: https://github.com/hugopl/gi-crystal
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.1 with grep in /nix/store/svnk0mcf1h2w0z9h2i49ii2nfa1cx0k6-gi-crystal-0.22.1
found 0.22.1 in filename of file in /nix/store/svnk0mcf1h2w0z9h2i49ii2nfa1cx0k6-gi-crystal-0.22.1

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
collision
gi-crystal
rtfm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/svnk0mcf1h2w0z9h2i49ii2nfa1cx0k6-gi-crystal-0.22.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gi-crystal https://github.com/r-ryantm/nixpkgs/archive/26685c650a2c06dc785bcc0c50fcd2e0c4764979.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/26685c650a2c06dc785bcc0c50fcd2e0c4764979#gi-crystal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/svnk0mcf1h2w0z9h2i49ii2nfa1cx0k6-gi-crystal-0.22.1
ls -la /nix/store/svnk0mcf1h2w0z9h2i49ii2nfa1cx0k6-gi-crystal-0.22.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

collision
rtfm

1 package built:

gi-crystal

Maintainer pings
cc @sund3RRR for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/hugopl/gi-crystal/releases.
meta.description for gi-crystal is: GI Crystal is a binding generator used to generate Crystal bindings for GObject based libraries using GObject Introspection.
meta.homepage for gi-crystal is: https://github.com/hugopl/gi-crystal
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.2 with grep in /nix/store/806ky6d86znfcxjnppm0rghnjjqy275r-gi-crystal-0.22.2
found 0.22.2 in filename of file in /nix/store/806ky6d86znfcxjnppm0rghnjjqy275r-gi-crystal-0.22.2

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
collision
gi-crystal
rtfm

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/806ky6d86znfcxjnppm0rghnjjqy275r-gi-crystal-0.22.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gi-crystal https://github.com/r-ryantm/nixpkgs/archive/34a07729e61ecffed881b4b3c3739fbf2704c543.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/34a07729e61ecffed881b4b3c3739fbf2704c543#gi-crystal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/806ky6d86znfcxjnppm0rghnjjqy275r-gi-crystal-0.22.2
ls -la /nix/store/806ky6d86znfcxjnppm0rghnjjqy275r-gi-crystal-0.22.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages failed to build:

collision
rtfm

1 package built:

gi-crystal

Maintainer pings
cc @sund3RRR for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gi-crystal is: GI Crystal is a binding generator used to generate Crystal bindings for GObject based libraries using GObject Introspection
meta.homepage for gi-crystal is: https://github.com/hugopl/gi-crystal
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.22.3 with grep in /nix/store/s695aykgsk82h195pzq9lzjm4rydbp5y-gi-crystal-0.22.3
found 0.22.3 in filename of file in /nix/store/s695aykgsk82h195pzq9lzjm4rydbp5y-gi-crystal-0.22.3

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

gi-crystal

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/s695aykgsk82h195pzq9lzjm4rydbp5y-gi-crystal-0.22.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gi-crystal https://github.com/r-ryantm/nixpkgs/archive/b60dcf66357229a37595636c9e2702bae16ec4fc.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b60dcf66357229a37595636c9e2702bae16ec4fc#gi-crystal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/s695aykgsk82h195pzq9lzjm4rydbp5y-gi-crystal-0.22.3
ls -la /nix/store/s695aykgsk82h195pzq9lzjm4rydbp5y-gi-crystal-0.22.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

gi-crystal

Maintainer pings
cc @sund3RRR for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gi-crystal is: GI Crystal is a binding generator used to generate Crystal bindings for GObject based libraries using GObject Introspection
meta.homepage for gi-crystal is: https://github.com/hugopl/gi-crystal
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.23.0 with grep in /nix/store/mn7kzxlnqn9xp1mkrc3d970jx2rw5qjy-gi-crystal-0.23.0
found 0.23.0 in filename of file in /nix/store/mn7kzxlnqn9xp1mkrc3d970jx2rw5qjy-gi-crystal-0.23.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

gi-crystal

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mn7kzxlnqn9xp1mkrc3d970jx2rw5qjy-gi-crystal-0.23.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gi-crystal https://github.com/r-ryantm/nixpkgs/archive/6b2e1dfa2fe2ccfae8c584658481a4a285f80a62.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6b2e1dfa2fe2ccfae8c584658481a4a285f80a62#gi-crystal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mn7kzxlnqn9xp1mkrc3d970jx2rw5qjy-gi-crystal-0.23.0
ls -la /nix/store/mn7kzxlnqn9xp1mkrc3d970jx2rw5qjy-gi-crystal-0.23.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gi-crystal

Maintainer pings
cc @sund3RRR for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gi-crystal is: GI Crystal is a binding generator used to generate Crystal bindings for GObject based libraries using GObject Introspection
meta.homepage for gi-crystal is: https://github.com/hugopl/gi-crystal
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.24.0 with grep in /nix/store/855y065d6dkf42lqwz0whqyidgv174yv-gi-crystal-0.24.0
found 0.24.0 in filename of file in /nix/store/855y065d6dkf42lqwz0whqyidgv174yv-gi-crystal-0.24.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

gi-crystal

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/855y065d6dkf42lqwz0whqyidgv174yv-gi-crystal-0.24.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gi-crystal https://github.com/r-ryantm/nixpkgs/archive/a7fcaa9be219b10b70c7cb8c8455bdc88aa579c3.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/a7fcaa9be219b10b70c7cb8c8455bdc88aa579c3#gi-crystal

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/855y065d6dkf42lqwz0whqyidgv174yv-gi-crystal-0.24.0
ls -la /nix/store/855y065d6dkf42lqwz0whqyidgv174yv-gi-crystal-0.24.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

gi-crystal

Maintainer pings
cc @sund3RRR for testing.


RLS: 0.20.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks conda-forge maintainers! 🎉


Laravel 6.0 and 6.1 Support

Please add support for Laravel 6.1

Should be supported. What composer error are you getting?

I think the problem is jenssegers/model needs to be tagged with a new version.
Cheers

@rjsworking  Yea, that's definitely holding some of my projects up as well. I believe the necessary changes have been merged. Waiting for a release.

@mikebronner The workaround is fork the jenssegers/model package, update it's composer json to support L6.1 and use it in your projects/packages composer.json: "jenssegers/model": "dev-master".

@rjsworking This should now be fixed in 1.0.3. Please let me know how that works for you.

Try 1.0.4 ... made a mistake in pushing 1.0.3. Sorry about that.

Np. It's working.
Thank you very much.


On Ubuntu, installation instruction fail if swig is not installed

The file requirements.txt lists box2d-py whose building depends on the presence of swig, which is not installed by default on Ubuntu (tested on 20.04). Installing swig (with sudo apt install swig) solves the problem. It might be helpful to add a note to the README about this problem.

Thank you.
Finally, we considered that the repo should just allow muzero to be installed and that there was no point in encumbering the installation with game-specific dependencies. We removed box2D but added an error message with installation instructions.

Thank you.
Finally, we considered that the repo should just allow muzero to be installed and that there was no point in encumbering the installation with game-specific dependencies. We removed box2D but added an error message with installation instructions.