软件无法正常打开

Translated Report (Full Report Below)
Incident Identifier: E4483780-0B2A-4B1B-8628-ACDF7FAD0EB3
CrashReporter Key:   FA00274D-BC6B-EB3F-A21B-6EA520AC3294
Hardware Model:      MacBookPro15,4
Process:             蓝奏云盘 [1624]
Path:                /Applications/蓝奏云盘.app/Contents/MacOS/蓝奏云盘
Identifier:          org.chenhb23.lanzou
Version:             1.0.8 (1.0.8)
Code Type:           X86-64 (Native)
Role:                Default
Parent Process:      launchd [1]
Coalition:           org.chenhb23.lanzou [1566]
Date/Time:           2021-12-29 21:30:18.0516 -0500
Launch Time:         2021-12-29 21:30:18.0334 -0500
OS Version:          macOS 12.1 (21C52)
Release Type:        User
Report Version:      104
Exception Type:  EXC_CRASH (SIGKILL (Code Signature Invalid))
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Termination Reason: CODESIGNING 1
Triggered by Thread:  0
Thread 0 Crashed:
0                                 	       0x109de6ac0 _dyld_start + 0
1                                	       0x105c84000 ???
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000
rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x00007ff7ba27bbd8
r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
rip: 0x0000000109de6ac0  rfl: 0x0000000000000200  cr2: 0x0000000000000000
Logical CPU:     0
Error Code:      0x00000000
Trap Number:     0
Binary Images:
0x109de2000 -        0x109e4dfff  ()  ???
0x105c84000 -        0x105cabfff  () <5cf444e6-280a-33a3-87ff-b56a6b4ec25c>
Error Formulating Crash Report:
dyld_process_snapshot_get_shared_cache failed
EOF

Full Report
{"app_name":"蓝奏云盘","timestamp":"2021-12-29 21:30:18.00 -0500","app_version":"1.0.8","slice_uuid":"5cf444e6-280a-33a3-87ff-b56a6b4ec25c","build_version":"1.0.8","platform":0,"bundleID":"org.chenhb23.lanzou","share_with_app_devs":1,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.1 (21C52)","incident_id":"E4483780-0B2A-4B1B-8628-ACDF7FAD0EB3","name":"蓝奏云盘"}
{
"uptime" : 1800,
"procLaunch" : "2021-12-29 21:30:18.0334 -0500",
"procRole" : "Default",
"version" : 2,
"userID" : 501,
"deployVersion" : 210,
"modelCode" : "MacBookPro15,4",
"procStartAbsTime" :<PHONE_NUMBER>386,
"coalitionID" : 1566,
"osVersion" : {
"train" : "macOS 12.1",
"build" : "21C52",
"releaseType" : "User"
},
"captureTime" : "2021-12-29 21:30:18.0516 -0500",
"incident" : "E4483780-0B2A-4B1B-8628-ACDF7FAD0EB3",
"bug_type" : "309",
"pid" : 1624,
"procExitAbsTime" :<PHONE_NUMBER>840,
"cpuType" : "X86-64",
"procName" : "蓝奏云盘",
"procPath" : "/Applications/蓝奏云盘.app/Contents/MacOS/蓝奏云盘",
"bundleInfo" : {"CFBundleShortVersionString":"1.0.8","CFBundleVersion":"1.0.8","CFBundleIdentifier":"org.chenhb23.lanzou"},
"storeInfo" : {"deviceIdentifierForVendor":"16631C5B-574D-5EFD-8FA8-D1F6DE3293B5","thirdParty":true},
"parentProc" : "launchd",
"parentPid" : 1,
"coalitionName" : "org.chenhb23.lanzou",
"crashReporterKey" : "FA00274D-BC6B-EB3F-A21B-6EA520AC3294",
"bridgeVersion" : {"build":"19P647","train":"6.1"},
"sip" : "disabled",
"isCorpse" : 1,
"exception" : {"codes":"0x0000000000000000, 0x0000000000000000","rawCodes":[0,0],"type":"EXC_CRASH","signal":"SIGKILL (Code Signature Invalid)"},
"termination" : {"namespace":"CODESIGNING","flags":66,"code":1},
"extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
"faultingThread" : 0,
"threads" : [{"triggered":true,"id":34096,"threadState":{"r13":{"value":0},"rax":{"value":0},"rflags":{"value":512},"cpu":{"value":0},"r14":{"value":0},"rsi":{"value":0},"r8":{"value":0},"cr2":{"value":0},"rdx":{"value":0},"r10":{"value":0},"r9":{"value":0},"r15":{"value":0},"rbx":{"value":0},"trap":{"value":0},"err":{"value":0},"r11":{"value":0},"rip":{"value":4460538560,"matchesCrashFrame":1},"rbp":{"value":0},"rsp":{"value":140701956815832},"r12":{"value":0},"rcx":{"value":0},"flavor":"x86_THREAD_STATE","rdi":{"value":0}},"frames":[{"imageOffset":19136,"symbol":"_dyld_start","symbolLocation":0,"imageIndex":0},{"imageOffset":0,"imageIndex":1}]}],
"usedImages" : [
{
"source" : "P",
"arch" : "x86_64",
"base" :<PHONE_NUMBER>,
"size" : 442368,
"uuid" : "cef5a27a-d50b-3020-af03-1734b19bc8c5",
"name" : ""
},
{
"source" : "P",
"arch" : "x86_64",
"base" :<PHONE_NUMBER>,
"size" : 163840,
"uuid" : "5cf444e6-280a-33a3-87ff-b56a6b4ec25c",
"path" : "\u0004",
"name" : "\u0004"
}
],
"vmSummary" : "ReadOnly portion of Libraries: Total=816K resident=0K(0%) swapped_out_or_unallocated=816K(100%)\nWritable regions: Total=8196K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8196K(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nSTACK GUARD                       56.0M        1 \nStack                             8192K        1 \nVM_ALLOCATE                          8K        2 \n__DATA                              32K        3 \n__DATA_CONST                        80K        1 \n__LINKEDIT                         240K        4 \n__TEXT                             592K        2 \n===========                     =======  ======= \nTOTAL                             64.9M       14 \n",
"legacyInfo" : {
"threadTriggered" : {
}
},
"trialInfo" : {
"rollouts" : [
{
"rolloutId" : "60da5e84ab0ca017dace9abf",
"factorPackIds" : {
  },
  "deploymentId" : 240000008
},
{
  "rolloutId" : "607844aa04477260f58a8077",
  "factorPackIds" : {
    "SIRI_MORPHUN_ASSETS" : "6103050cbfe6dc472e1c982a"
  },
  "deploymentId" : 240000066
},
{
  "rolloutId" : "602ad4dac86151000cf27e46",
  "factorPackIds" : {
    "SIRI_DICTATION_ASSETS" : "6193d03f2171a2330e561dfc"
  },
  "deploymentId" : 240000290
},
{
  "rolloutId" : "5ffde50ce2aacd000d47a95f",
  "factorPackIds" : {

  },
  "deploymentId" : 240000090
},
{
  "rolloutId" : "5fc94383418129005b4e9ae0",
  "factorPackIds" : {

  },
  "deploymentId" : 240000196
},
{
  "rolloutId" : "601d9415f79519000ccd4b69",
  "factorPackIds" : {
    "SIRI_TEXT_TO_SPEECH" : "61c11dcd2cb6041dc630dc63"
  },
  "deploymentId" : 240000357
}

],
"experiments" : [
]
},
"reportNotes" : [
"dyld_process_snapshot_get_shared_cache failed"
]
}
Model: MacBookPro15,4, BootROM 17<IP_ADDRESS>.0 (iBridge: 19.16.10647.0.0,0), 4 processors, Quad-Core Intel Core i5, 1.4 GHz, 16 GB, SMC
Graphics: Intel Iris Plus Graphics 645, Intel Iris Plus Graphics 645, Built-In
Display: Color LCD, 2560 x 1600 Retina, Main, MirrorOff, Online
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, LPDDR3, 2133 MHz, SK Hynix, H9CCNNNCLGALAR-NVD
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, LPDDR3, 2133 MHz, SK Hynix, H9CCNNNCLGALAR-NVD
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x870), wl0: Jul 16 2021 18:25:13 version 16.20.3<IP_ADDRESS>.105 FWID 01-30be2b3a
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB31Bus
USB Device: T2Bus
USB Device: Touch Bar Backlight
USB Device: Touch Bar Display
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 63.5
完全不懂代码，求大佬帮忙

已支持 macOS Monterey 系统（Intel平台），可重新下载 1.0.8 版本后再试

emmm 这回可以打开了，但下载后还是显示为一个html的文件，跟之前一样…还是请大佬再看看TAT


iOS Pairing issue: when first pairing request is actively rejected via button tap, subsequent connections do not result in new pairing request

Hi
I have been using version 2.0-pre1 for some time which, for the most part works well on both Android and iOS.
The main issue I have with it relate to pairing on iOS. My device (Nordic NRF52832-based) includes encrypted characteristics, via BLE 'Just Works', when the iPhone connects to these characteristics, it forces a bond, which pops up an (iOS generated) dialogue box asking the user if they wish to pair.
If the user taps 'cancel', or simply waits for the dialog to time out (10 seconds), then subsequent attempts to connect to the same device fail as they do not produce the 'Do you want to bond' dialog.
Steps to reproduce

From iOS, attempt to connect to a BLE device with encrypted characteristics

When the 'Do you want to pair with XXX' dialog box appears, tap 'cancel'

Try to connect to the same BLE device once again

Observe that iOS does not generate a pair 'Do you want to pair with XXX' dialog, and that the connection has failed.

Expected behavior
iOS should always ask the user 'Do you want to pair with XXX' when an encrypted characteristic is encountered that is not covered by an existing bond.
Actual behavior
iOS fails to ask the user 'Do you want to pair with XXX' on subsequent connection attempts where the user actively rejected a previous connection attempt.
If I restart my app, then iOS will again start to ask the user 'Do you want to pair with XXX' again. As long as user selects 'Pair', the implementation works well, but I cannot control the iOS dialog, or change its timeout so I need to handle this issue.
Configuration
V2.0-pre1
iOS 12, iPhone 7

Hi @veletron2,
I'm the friendly issue checker.
It seems like (50.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!


Ring API unable to fetch session

@riveraj33 looks like I'm eating my words on the API never changing 🤦♂.  Ring broke some of the old android endpoints being used by the ring-api library.  I'm updating my fork to use new endpoints and should have a fix out soon.

Hey thanks! I was wondering why I couldn’t disarm when I got home. Looking forward to the fix!

Is there a chance this was fixed on its own somehow? Everything seems to be working fine since this morning.

@riveraj33 looks like Ring must have seen it as a bug and fixed it on their end.  Everything is operational again.  I may circle back in the future and change some of the endpoints being used, but everything seems to be working great as-is for now.


Only emit FIPS startup log when running a server component

Release note:
NONE

Merging to unblock CI on the main pipeline.


Add initial support for bm25 with groupBy

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

Project coverage is 95.23%. Comparing base (d604db8) to head (6808eb7).
Report is 20 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #967      +/-   ##
==========================================
- Coverage   95.23%   95.23%   -0.01%
==========================================
  Files         173      173
  Lines       17836    17852      +16
==========================================
+ Hits        16986    17001      +15
- Misses        850      851       +1

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

Closing in favour of https://github.com/weaviate/weaviate-python-client/pull/978


2.1.9: Edit toolbar not working

in CKEditor Configuration, selecting a toolbar and clicking "edit" does not result in any loading of title or buttons to be edited.
Tested in DNN 7.4.2, CDN usage disabled, Gravity Skin and Container.

oops, it seem to work, but takes lot of time to load.

edit toolbar takes more than 30 seconds to load and there is no visual feedback.

With what browser does this happens? i can add a loading animation but at least in chrome it only takes a few seconds

with Edge it takes 30 seconds to load a toolbar, to save or cancel.
Firefox is faster, it needs just 12 seconds.
Some kind of an indicator would be helpful.

okay when i have time i add a spinner. its weird that ff and edge can not handle the js fast enough in chrome its bellow then 2 seconds


Support RETURNING schema statistics in INSERT statement

Change:

Support RETURNING schema statistics in INSERT statement(PLSQL)
Support FROM clause schema statistics in method(TRIM specifically)

需要修复下代码冲突


api

Hi there
is there any way to get to an api so it could be integrated into homeassistant?
i don't seem to be able to find anything about it
would be nice to be able to remotely change and monitor temps and maybe change fan and heat/cool
thnx

At some point I would like to write an API, but I don't have time at the moment. I haven't worked with Home Assistant before, but if you can write custom HTML GET/POST messages, you can use the ThermOS web backend to control everything and get the data that you want.
If you take a look at thermostat_web.py, any definition that has @app.route(urlpath, methods=['POST']) above it is a worker function. You can post a form to that url path to do things such as set the temperature or edit a schedule entry.
Any definition that is preceded by @app.route(urlpath, methods=['GET']) is a function that will return data.

you got  an example on how to do a post
example would be nice for turning fan from on to auto and system from auto to cool and heat
thnx

I am also trying to extract data and push data to server from a remote endpoint.. Any suggestions of where to start would be helpfull. Your work is awesome and works well locally.

I'm pretty busy right now, but I'll try to get you guys some examples this evening

So here's just a quick post method with a python script:
import requests
url="http://localhost/hold"
data= {
    'onoffswitch':'on', #on=Cool, #off=Heat
	'target': u'75', #Target Temp
	'timeFrame': u'.25' #time in hours
    }
requests.post(url, data=data)

In this example, you first import the requests module.
2) you set the url (Note the '/hold' at the end), in my case, I was testing on the same machine that ThermOS was running. Otherwise, replace localhost with your Thermostat local IP
3) data that you want to send. Since we are sending data to the 'hold' function, there is specific names that must be used
4) post the request and the Thermostat will handle the rest
It will be up to you to figure out how to implement it into homeAssistant though as I'm not familiar with their API. I'll post some references for you to access other functions when I get a chance.

We figured it out now the whole thermostat is controllable from
homeassistant
homeassistant:
customize:
sensor.fan_mode:
friendly_name: Fan
haaska_hidden: true
icon: mdi:fan
sensor.system_mode:
  friendly_name: Mode
  haaska_hidden: true
  icon: mdi:settings

sensor.indoor_temperature:
  friendly_name: Indoor Temp
  haaska_hidden: true
  icon: mdi:thermometer-lines

sensor.operation_set_point:
  friendly_name: Setpoint
  haaska_hidden: true
  icon: mdi:oil-temperature

sensor.fan_on:
  friendly_name: Fan Status
  haaska_hidden: true
  icon: mdi:fan

sensor.operation_mode:
  friendly_name: Operation Mode
  haaska_hidden: true
  icon: mdi:air-conditioner

group:
thermos:
name: thermos
entities:
- sensor.fan_mode
- sensor.system_mode
- sensor.indoor_temperature
- sensor.operation_set_point
- sensor.fan_on
- sensor.operation_mode
- input_select.heat_cool
- input_select.temp
input_select:
heat_cool:
name: Heat Cool
options:
- HEAT
- COOL
- OFF
initial: COOL
temp:
options:
- '65'
- '66'
- '67'
- '68'
- '69'
- '70'
- '71'
- '72'
- '73'
- '74'
- '75'
- '76'
- '77'
- '78'
- '79'
- '80'
initial: '74'
automation:

alias: "Change Thermostat"
trigger:

platform: state
entity_id: input_select.heat_cool
platform: state
entity_id: input_select.temp
action:
service: script.turn_on
entity_id: script.run

alias: "Change input select of temp if Thermostat is changed manully"
trigger:

platform: state
entity_id: sensor.operation_set_point
action:
service: input_select.select_option
data_template:
entity_id: input_select.temp
option: '{{ states.sensor.operation_set_point.state }}'

alias: "Change input select of mode if Thermostat is changed manully"
trigger:

platform: state
entity_id: sensor.system_mode
action:
service: input_select.select_option
data_template:
entity_id: input_select.heat_cool
option: '{{ states.sensor.system_mode.state }}'

script:
run:
sequence:
- service: shell_command.heat_cool_select
shell_command:
heat_cool_select: curl -d "mode={{ states.input_select.heat_cool.state
}}&target={{ states.input_select.temp.state }}" -X POST
http://<IP_ADDRESS>:8880/system
sensor:

platform: scrape
resource: http://<IP_ADDRESS>/_liveUpdate
select: '#fanModeContainer'
name: Fan Mode
icon: mdi:fan

platform: scrape
resource: http://<IP_ADDRESS>/_liveUpdate
select: '#systemModeContainer'
name: System Mode
icon: mdi:nest-thermostat

platform: scrape
resource: http://<IP_ADDRESS>/_liveUpdate
select: '#indoorTempContainer'
name: Indoor Temperature
icon: mdi:thermometer
unit_of_measurement: °F

platform: scrape
resource: http://<IP_ADDRESS>/info
select: '#cool'
name: Operation Cool

platform: scrape
resource: http://<IP_ADDRESS>/info
select: '#heat'
name: Operation Heat

platform: scrape
resource: http://<IP_ADDRESS>/info
select: '#fan'
name: Operation Fan

platform: scrape
resource: http://<IP_ADDRESS>/_liveUpdate
select: '#targetTemps'
name: Operation Set Point
unit_of_measurement: °F

platform: template
sensors:
fan_on:
friendly_name: "Fan Running"
value_template:  "{{ 'ON' if 'ON' in
states.sensor.operation_fan.state | upper else 'OFF' }}"

platform: template
sensors:
operation_mode:
friendly_name: "Operation Mode"
value_template: >-
{% if
states.sensor.operation_cool.state.split(':')[1] |trim | upper == 'ON' %}
COOL
{% elif
states.sensor.operation_heat.state.split(':')[1] |trim | upper == 'ON' %}
HEAT
{% else %}
OFF
{% endif %}

IMPORTANT: This email is intended for the use of  the  individual
addressee(s)  named  above  and  may  contain information that is
confidential,  privileged  or  unsuitable  for  overly  sensitive
persons  with  low  self-esteem, no sense of humour or irrational
religious beliefs. If you are not  the  intended  recipient,  any
dissemination,  distribution  or  copying  of  this  email is not
authorised (either explicitly or implicitly) and  constitutes  an
irritating  social  faux  pas. Unless the word absquatulation has
been used in its correct context somewhere  other  than  in  this
warning, it does not have any legal or grammatical use and may be
ignored. No animals were  harmed  in  the  transmission  of  this
email,  although  the  yorkshire  terrier  next door is living on
borrowed time, let me tell you. Those of you with an overwhelming
fear  of  the unknown will be gratified to learn that there is no
hidden message revealed by reading  this  warning  backwards,  so
just ignore that Alert Notice from Microsoft: However, by pouring
a complete circle of salt around yourself and your  computer  you
can  ensure  that  no harm befalls you and your pets. If you have
received this email in error, please  add  some  nutmeg  and  egg
whites  and place it in a warm oven for 40 minutes. Whisk briefly
and   let    it    stand    for    2    hours    before    icing.
Legal Notice: Receipt of this message constitutes your unconditional
acceptance of agreement with all terms, conditions, conclusions and
opinions, either expressed or implied, as interpreted by the author without
further clarification. Use of any information contained herein [inclusive
of any and all attachments] or omitted in part or in whole from the actual
message is strictly prohibited and will be subject to collection of
significant financial damages.
The views of my employer do not conform to my views, or to any accepted
standard of logic that the Greeks thought up anyway...
None of the ideas expressed above are actually mine. They are told to me by
Luthor and Ferdinand, the five inch tall space aliens who live under my
desk. In return for these ideas, I have given them permission to eat any
dust bunnies they may find under there.
No trees were destroyed in the sending of this message, however, a
significant number of electrons were terribly inconvenienced.
On Tue, Oct 17, 2017 at 1:14 PM, mholgatem<EMAIL_ADDRESS>wrote:

So here's just a quick post method with a python script:
import requests
url="http://localhost/hold"
data= {
'onoffswitch':'on', #on=Cool, #off=Heat
'target': u'75', #Target Temp
'timeFrame': u'.25' #time in hours
}
requests.post(url, data=data)
In this example, you first import the requests module.
2) you set the url (Note the '/hold' at the end), in my case, I was
testing on the same machine that ThermOS was running. Otherwise, replace
localhost with your Thermostat local IP
3) data that you want to send. Since we are sending data to the 'hold'
function, there is specific names that must be used
4) post the request and the Thermostat will handle the rest
It will be up to you to figure out how to implement it into homeAssistant
though as I'm not familiar with their API. I'll post some references for
you to access other functions when I get a chance.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholgatem/ThermOS/issues/8#issuecomment-337290077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQ8mOsa3YUacC1RPGTUu3SPIfHvgkQDks5stOB6gaJpZM4Pxye_
.

wow, very cool! Is this all that is required or are there additional scripts that go with this to operate it?

that is all thats required and we can set cool heat off we can set temps
and it shows all modes
i run it on a 5 inch touchscreen
ppl are getting interested now in it since total cost to make the whole
thing is about 60-70$
On Oct 19, 2017 7:37 PM, "mholgatem"<EMAIL_ADDRESS>wrote:

wow, very cool! Is this all that is required or are there additional
scripts that go with this to operate it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholgatem/ThermOS/issues/8#issuecomment-338066763,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQ8mKqWF7UUX-iWSJf3ufV-bRGaYUBzks5st90hgaJpZM4Pxye_
.

https://photos.app.goo.gl/OT74t3n6PFoixyxM2
On Oct 19, 2017 7:37 PM, "mholgatem"<EMAIL_ADDRESS>wrote:

wow, very cool! Is this all that is required or are there additional
scripts that go with this to operate it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholgatem/ThermOS/issues/8#issuecomment-338066763,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQ8mKqWF7UUX-iWSJf3ufV-bRGaYUBzks5st90hgaJpZM4Pxye_
.

https://photos.app.goo.gl/wyprCgSj4T3NglqG2
On Oct 19, 2017 7:37 PM, "mholgatem"<EMAIL_ADDRESS>wrote:

wow, very cool! Is this all that is required or are there additional
scripts that go with this to operate it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholgatem/ThermOS/issues/8#issuecomment-338066763,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQ8mKqWF7UUX-iWSJf3ufV-bRGaYUBzks5st90hgaJpZM4Pxye_
.

ah, ok. I see your shell command now. Very nice! I'm going to re-open this issue, so that I remember it. When I have some time, I'll build it into the project (if you don't mind). BTW, how did you come across this project?

well there was not really a good thermostat thats DIY so i spend a couple
hours googeling and yours was the best one so i made one . then i needed
remote control so me and a friend spend a coupke days integrating it to
homeassistant.
now we got someone else working on a rest api and mqtt for it so we can use
the hvac module homeassistant has.
On Oct 19, 2017 8:03 PM, "mholgatem"<EMAIL_ADDRESS>wrote:

ah, ok. I see your shell command now. Very nice! I'm going to re-open this
issue, so that I remember it. When I have some time, I'll build it into the
project (if you don't mind). BTW, how did you come across this project?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholgatem/ThermOS/issues/8#issuecomment-338070464,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQ8mC3ZYoS4DqZeol1Qg_HJFcBFkSmDks5st-M1gaJpZM4Pxye_
.

very cool. If you guys are familiar with github, you are always welcome to create a pull request. I'm always eager to have help on these projects.

yeah we will once we got rest and mqtt working
this thermostat is going places quick now
we will have a writeup on our homeassistant  project and module page soon
.... the guy thats supposed to write it is looking after his wife atm in
the hospital she had surgery yesterday so itll be a couple days
On Oct 19, 2017 8:17 PM, "mholgatem"<EMAIL_ADDRESS>wrote:

very cool. If you guys are familiar with github, you are always welcome to
create a pull request. I'm always eager to have help on these projects.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mholgatem/ThermOS/issues/8#issuecomment-338072419,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQ8mPfzfh7vMc5KSt38Duf_03yizcjQks5st-atgaJpZM4Pxye_
.

Good Morning mholgatem
I am the guy that got nominated to write this up... LOL ... I am open to anyway to write it up... At first a had a fork and was going to add a file of the homeassistant thermo.yaml (package) config and a readme with pics and discriptions of the wiring and formatting of the touchscreen. I am new to git and was worried that it could take credit away from you... Any suggestions... My plan was a git for Homeassitant DIY thermo powered by mholgatem? I didnt know if having your software on the git would be best or a link..  I dont like links it has users digging around and getting lost.

and also would this fork update from changes on your end.. I think the Home Assistant option you give you more exposure

I don't really care much about credit, I just like to see how people use my code. But what I was thinking is that we can make an installer for the Home Assistant stuff. As far as I am aware, the config yaml files just need to be copied into the correct Home Assistant folder, right? We could do a thing like this:

Install ThermOS → Check for Home Assistant installation → if no Home Assistant, ask if you'd like to install Home Assistant → Copy thermo.yaml to correct Home Assistant folder
Then ask if this will be run with a touch screen or in headless mode

If you want to figure out the config stuff, you can either send it to me via email<EMAIL_ADDRESS>or you can create a pull request by clicking 'create new pull request' on the code page.

yes but the home assistant install is not quite that easy.. The yaml for the thermos would have to have the correct ip of the thermos and you would need to secure home assistant with ssl and a dyndns..and config a password... Let me think... I think zombu would know a little better than I since All i did is the homeassistant config for him

setting the correct ip is easy, I have lots of bash scripts that do that sort of thing. I would set up the home assistant to be local network only, so that the ssl/dyndns/password stuff can be skipped. My thinking is that if they want it public facing, then they can do the legwork to set that stuff up. I personally discourage setting up public facing hardware unless you are working on your own project or are making enough money doing it to cover legal fees. All that it takes is one litigious person to tie up all of your assets defending yourself in court.

Zombu is trying to use a tinkerboard that has more horsepower for the ha install.... will post when that happens

cool. let me know.
Are you guys running the thermostat on a separate board from the home assistant?

We are trying to give user a option for either way... a installer that will give option of home assistant installed or not ..... I have started the write up but its still alpha https://github.com/Vasiley/Diy_Thermostat_with_Homeassistant

it's looking good. If you want, you can also go here and scroll down to the Github Pages section, you can create your own project webpage like this.

Cool.... Once I get all info will try that Thanks
Just learning all this LOL

yeah, it's a lot to take in all at once. let me know if you have any questions.


Fix some bad formatting and links

@PProfizi and @anslpa  There were some format errors and broken links on the README and overall index pages. I cleaned both pages up. I will also soon be adding cheat sheet links for PyPDF-Post and cleaning up these same two files in that repo.

@ansys/pyansys-core Any chance someone could review and merge this PR?


Is it possible to automate step 3 also?

Is there any way to automate the step 3?
Browse to http://localhost:9000/setup (replace "localhost:9000" by your own URL) and follow the setup instructions.

I cannot remember if database propagation starts automatically or initial GET is required to initiate the propagation. A small curl step could be added easily. For me this is good manual step to verify upgrade


[RN] Type Error; Failed to set an indexed property on 'CSSSyleDeclaration'

Precondition:
The send page is opened
Steps to reproduce:

Click the "Scan QR" button
Pay attention to the blank page and the error message on the console

Actual result: The blank page is displayed after clicking the "Scan QR" button. User isn't able to open the "Scan QR" page
Expected result: The blank page should be opened after clicking the "Scan QR" button. User should bet able to open the "Scan QR" page
Checked on https://goodnative.netlify.app/ V1.3.1-1
LG V30+ // Android 8.0 // Google Chrome 85.0.4183.121
Desktop: Windows 10 // Google Chrome 85.0.4183.121

@mauriguz @MathiasMoralesDixtra
It's seems some styles are using props aren't available on the all platforms (like 'elevation' prop available Android only)
we have to include platform-specific  style props only if running target platform.
it's seems there's some webpack/babel plugins for that - please check configs in master branch. because in master that issue doesn't  appears

@MathiasMoralesDixtra @mauriguz @sirpy QR scanner works
Checked on native 1.3.1-1
LG V30+ // Android 8.0 // Google Chrome 86.0.4240.75
Desktop: Windows 10 // Google Chrome  86.0.4240.75


Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection.

Exception message:
Method not found: 'Microsoft.Extensions.DependencyInjection.IServiceCollection Microsoft.Extensions.DependencyInjection.ServiceCollectionExtensions.AddInstance(Microsoft.Extensions.DependencyInjection.IServiceCollection, !!0)'.

   at Microsoft.AspNet.Hosting.WebHostBuilder.BuildHostingServices()
   at Microsoft.AspNet.Hosting.WebHostBuilder.Build()
   at Microsoft.AspNet.TestHost.TestServer..ctor(WebHostBuilder builder)
   at Microsoft.AspNet.TestHost.TestServer.Create(Action`1 configureApp, Action`1 configureServices)

project.json:
{
  "version": "1.0.0-*",
  "description": "CNBlogs.Ad.BaseTests Class Library",
  "authors": [ "xishuai" ],
  "tags": [ "" ],
  "projectUrl": "",
  "licenseUrl": "",

  "frameworks": {
    "dnx451": { }
  },
  "dependencies": {
    "EntityFramework.Core": "7.0.0-rc2-16432",
    "EntityFramework.MicrosoftSqlServer": "7.0.0-rc2-16432",
    "Microsoft.AspNet.TestHost": "1.0.0-rc1-final",
    "xunit": "2.1.0",
    "xunit.runner.dnx": "2.1.0-rc1-build204"
  },
  "commands": {
    "test": "xunit.runner.dnx"
  }
}

Because I use this version 7.0.0-rc1-final, the emergence of this problem #3811, so I upgraded to this version 7.0.0-rc2-16432, but it appeared the above problems.
If it alone unit testing, it works.
And the problem is also related: https://github.com/aspnet/Home/issues/1138

I modified "Microsoft.AspNet.TestHost": "1.0.0-rc2-16032", it works.
https://github.com/aspnet/Home/issues/1138#issuecomment-160513322


Amazon S3 SDK Version

  Problem 1
    - Installation request for fineuploader/php-s3-server 1.1.0 -> satisfiable by fineuploader/php-s3-server[1.1.0].
    - fineuploader/php-s3-server 1.1.0 requires aws/aws-sdk-php 2.* -> satisfiable by aws/aws-sdk-php[2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, 2.4.10, 2.4.11, 2.4.12, 2.4.2, 2.4.3, 2.4.4, 2.4.5, 2.4.6, 2.4.7, 2.4.8, 2.4.9, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.6.0, 2.6.1, 2.6.10, 2.6.11, 2.6.12, 2.6.13, 2.6.14, 2.6.15, 2.6.16, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.6.6, 2.6.7, 2.6.8, 2.6.9, 2.7.0, 2.7.1, 2.7.10, 2.7.11, 2.7.12, 2.7.13, 2.7.14, 2.7.15, 2.7.16, 2.7.17, 2.7.18, 2.7.19, 2.7.2, 2.7.20, 2.7.21, 2.7.22, 2.7.23, 2.7.24, 2.7.25, 2.7.26, 2.7.27, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.7.7, 2.7.8, 2.7.9, 2.8.0, 2.8.1, 2.8.10, 2.8.12, 2.8.13, 2.8.14, 2.8.15, 2.8.16, 2.8.17, 2.8.18, 2.8.19, 2.8.2, 2.8.20, 2.8.21, 2.8.22, 2.8.23, 2.8.24, 2.8.25, 2.8.26, 2.8.27, 2.8.28, 2.8.29, 2.8.3, 2.8.30, 2.8.31, 2.8.4, 2.8.5, 2.8.6, 2.8.7, 2.8.8, 2.8.9, 2.8.x-dev] but these conflict with your requirements or minimum-stability.

composer.json
{
    "require": {
        "aws/aws-sdk-php": "^3.20",
        "fineuploader/php-s3-server": "1.1.0"
    }
}

how can i use with aws-php-sdk v3+ and amazon v4 options? (locale, etc)

If you want to use v3 or newer of the AWS SDK, I guess the project's composer.json file needs to be updated to support v2 and v3. Or if this is not possible, updated to support v3 and released as php-s3-server 2.0.

I've just downloaded the raw file from here, but the region key does not work. it still uses the default "us-east-1" for some reason. this is my first time using both AWS and this library so unsure where the issue is. i'm passing it as a string to the s3.FineUploader as a top level property.

Just to let you know I will be trying my hand at this
From this guide:
https://docs.aws.amazon.com/aws-sdk-php/v3/guide/guide/migration.html
The region is now required, what would be the best way to handle this, default to 'us-east-1' and then override from $_ENV if the region is set?

default to 'us-east-1' and then override from $_ENV if the region is set?

I guess we do need a sensible default. We'll always know the region for v4 signature requests, since that will be sent with the signature request. But for v2 signatures, guess we'll have to have a default set and allow for that to be overridden via an environment variable or perhaps a parameter/header in the HTTP request.

Also on the success callback to the endpoint the region wont be sent as there is no signature request
(required for verifyFileInS3)
I just stumbled apon getbucketlocation in the v3 SDK
Will reply with my results with getbucketlocation

Hiya
I have my endpoint working with the v3 sdk, I will commit later (after work) to my fork and link here so we can discuss any changes. I did need to add some params to uploadSucess to pass the region and signature version.
AFAIK there were no changes required to the signature section of endpoint.php, only for the success callback as this is where we use getS3Client
I am new to github so if you would like me to commit differently then let me know :)

Have updated endpoint.php on jaredcassidy/php-s3-server
my upload page params
request: {
                endpoint: 'https://mys3bucket.s3-eu-west-2.amazonaws.com',
                accessKey: 'xxxxx',
            },
            objectProperties: {
                region: 'eu-west-2',
                acl: "public-read"
            },
            signature: {
                endpoint: '/vendor/fineuploader/php-s3-server/endpoint.php',
                version: 4
            },
            uploadSuccess: {
                endpoint: '/vendor/fineuploader/php-s3-server/endpoint.php?success',
                params: {
                  region: 'eu-west-2',
                  version: 4
                  }

Can you open up a pull request so we can discuss further?

Sorry for the delay, have opened pull request
https://github.com/FineUploader/php-s3-server/pull/8

Hey there @jaredcassidy & @rnicholus,
This might be old news but instead of manually signing requests, why not use generate a presigned POST request using the AWS PHP SDK?
https://docs.aws.amazon.com/sdk-for-php/v3/developer-guide/s3-presigned-post.html


[FLINK-17287][github] Disable merge commit button

(I know it is already disabled, this is just for consistency and to introduce the asf.yaml concept to all repos)

LGTM, merging! Thanks @zentol.

LGTM, merging! Thanks @zentol.


Remove MahApps dependency on Wox.Plugin.ThemeManager

Currently for theming, we leverage its MahAppsLibraryThemeProvider.DefaultInstance
We should just create our own instance of this.  No need to get the entire library for this single item.

@punker76 has a PR for this

Shipped with 0.27 release. https://github.com/microsoft/PowerToys/releases/tag/v0.27.0


SharePoint Custom Policies setting deprecation by Microsoft

🐛 Summary
Microsoft is making updates to the custom scripting configuration options for Sharepoint and OneDrive. The purpose of this issue is to determine if we need to remove or revise policies MS.SHAREPOINT.4.1v1 and 4.2 based on the changes.
https://techcommunity.microsoft.com/t5/sharepoint/removing-custom-scripting-on-sharepoint-sites/m-p/4055563
As a result of #1216, two separate issues will be created to address this setting. This issue will address the removal of all references of policy group 4, Custom Scripting and its policies to include the baselines and rego.
Why does this work belong in this project?
This would be useful because as Microsoft rolls out this update, users of ScubaGear will experience errors as a result of the missing setting. This allows the ScubaGear and the SCBs to be update to date with this setting deprecation.
Implementation notes
Removal of all references to SharePoint policy group 4: custom scripting and its policies in baselines and rego.
Acceptance criteria
How do we know when this work is done?

[x] The following files will be updated to remove references to SharePoint policy group 4: custom scripting and its policies

[x] sharepoint.md
[x] SharepointConfig.rego
[x] ReportDetails.rego
[x] SharepointConfig_01_test.rego
[x] sharepoint.pnp.testplan.yaml
[x] sharepoint.spo.testplan.yaml

pulled in SCB changes approved in PR #1410


make mz_stream Send

Should answer #34.

Ok, I think this is good to go, thanks!
Can you add the unsafe impl to the main crate on stream::Stream, however? I believe it should also be safe to declare that as Sync as well.

I'm not sure about Sync really. There are a bunch a pointers and stuff in mz_stream that I would not want to see shared between two threads.

Here you go. Stream is Send as well.

Sync itself actually means that &T is safe to share among threads, which in this case it is because the type is correctly accessed via &mut T and such (e.g. there is no internal mutability). Can you also remove the Sync for mz_stream directly? (e.g. that doesn't belong in a *-sys crate)

Understood, thanks for the clarifications :)

Thanks!


Unify canonical ToS and Privacy

Currently we show the ToS in a modal from our code, but link to the support site from the footer. As of this writing, the version in our code is newer.
We have the privacy policy in a page. It's not on the support site anywhere.
Where should it be? Let's put it there. If it's on our site, we should make sure people can see the privacy policy when they haven't yet signed the ToS but have signed in.
@bradtaylor this is ultimately probably your call.

No longer a problem, we have an alternative fix.


Suggestion for overhead text coloring

I've been playing around with this plugin for the past few weeks and really enjoying the quality of life improvements I am getting out of it.
Some bosses have overhead text quotes that can be indicative of certain combat actions such as Cerberus's ghost announcement "Aaarrrooooooo" or the Deranged archaeologist special attack marked by "Learn to Read!". Unfortunately these overhead text popups do not appear in the chat log.
I would love to see a feature added to this plugin or another similar plugin made where these overhead texts can be specifically recolored as they appear. This would be helpful for those that have trouble seeing certain colors or on bosses that spam different quotes such as both archaeologist bosses.

This is out of scope for this plugin, in my opinion.  However if someone were to want to PR a feature to do this I would take a look.


No need of duplicated resources in zip and final dp.json

originally coming from here https://github.com/datahq/datahub-qa/issues/152
So we don't need source/tabular in zip and original in live datapackage.json (unless it's resource is non-tabular).
Acceptance Criteria

[x] no duplicates on after data get dataset
[x] no duplicate rsources in dp.json

Tasks

[x] refactor to skip source/tabular in OutputToZipProcessingNode
[x] refactor OriginalProcessingNode to handle exluding original taular source

maybe bring back source/non-tabulr?

[x] update tests in assembler
[x] update tests in specstore

FIXED


Preserve Source File Timestamps on Upload to Blobs

Which version of the AzCopy was used?
10.4.3
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
azcopy sync
What problem was encountered?
azcopy loses the original file metadata for Creation, LastWrite, and LastAccess.
How can we reproduce the problem in the simplest way?
Have you found a mitigation/solution?
This is certainly known that azcopy does not preserve file timestamps when uploading to blob storage. This can be remedied by optionally pushing the file timestamps up to Azure storage as metadata properties.
Recommendation is to add new switch --put-timestamps which will create three metadata attributes for each uploaded file:  CreationTimeUTC, LastWriteTimeUTC, LastAccessTimeUTC which have the UTC times of the original file. Using UTC time ensures no time zone issues.
The following illustrates how to do this using PowerShell :
$file = "SampleFile.txt"
$FileInfo = Get-ChildItem -Path $file
$FileMetadata = @{ "CreationTimeUTC"= $FileInfo.CreationTimeUtc; "LastWriteTimeUTC"=$FileInfo.LastWriteTimeutc; "LastAccessTimeUTC"=$FileInfo.LastAccessTimeUtc; "Origin"=$FileInfo.FullName }

$x = Set-AzStorageBlobContent -Metadata $FileMetaData -Container "contosoupload" -File ".\$file" -Blob $file -Context $c

As an further enhancement, AzCopy sync could be enhanced with a --use-timestamps which would preserve the file timestamps found in the metadata when downloading to a PC. It could also be used for the synchronization itself. This would allow AzCopy sync to work with multiple computers sharing the same container (i.e., shared synchronized data).
Another minor enhancement would be to have --Put-Origin switch which would add an Origin metadata attribute showing the file origin:

The use case I have is to move files from one PC to another and preserve all of the timestamps in the process.  One solution is to zip up the files before moving them. Works for a small number of files; not so great for a large number.
A crude work-around is to generate a file which contains all of the timestamps for the relevant files and upload that along with the files. The PowerShell below will generate such a file:
Get-ChildItem -File -Recurse `
    | Select-Object -Property FullName, Length, CreationTimeUtc, LastAccessTimeUtc, LastWriteTimeUtc, Attributes `
    | ConvertTo-json | out-file "FileTimestamps.json"

And then when you do a restore, you use the timestamps file to restore the original timestamps for all of the files after downloading completes.
This would be a whole lot easier if AzCopy could preserve the original file timestamps as blob metadata tags.

Versions 10.4 and later support preserving timestamps when uploading to Azure Files. I'll change the title to make it clear that this request is about blobs.

Any progress on adding this feature?  Even just preserving the source file's LastModified timestamp in ISO-8601 format with a --put-timestamps switch would be great.

@lesterw1 I've moved on to a different project, so can't answer your question sorry.  @rishabpoh or @zezha-msft might be able to respond.

Hi,
I have a scenario where I have to upload and download the huge file (TB) in Linux  and preserve date and time, Is this is feasible with new Azcopy 10.8 version ' --preserve-last-modified-date'

Is there any solution to maintain the last modified dates yet please?

+1 for this feature.

@rishabpoh or @zezha-msft Is there any update on this?  It's an easy feature to implement as it only requires adding a couple extra metadata fields and a switch such as --put-timestamps as shown in the comments above.

Sorry for the delay and we appreciate your patience.
To create an adequate solution, I'll be submitting a formal request to the service to add a user-settable lmt field. The reason is that the easier solution of simply using metadata is problematic: if only AzCopy was setting it, then how can AzCopy operate on existing files or the files uploaded by other tools? A user-settable lmt would solve this concern and let all tools leverage the same field.

Thanks @zezha-msft.  As for your point about simply using metadata, I don't see it as a problem. If the 'lmt' field is the blob last-modified-time, that would be great to be able to set. I asked for that feature years ago and there wa s alittle push-back from the dev teams due to some issue with billing (if my memory serves). If there is push back, then having the metadata would be the next best option.  Keep us posted on progress. Thank you.

@lesterw1 Thanks for the context!
I'll definitely be advocating for this change to happen since it improves the sync behavior immensely.
Service changes may take a while to ship unfortunately, but I think it ultimately is the best solution.

Service changes may take a while to ship unfortunately

Is there an approximate ETA?
The lack of this feature means many common operations are impossible. For example, copying a blob container to another container will reset timestamps, wiping out the info needed for tiering.
Similarly, legal hold and similar features (or end-user code doing the same thing) can't rely on the timestamps either, because they're not the "content timestamps", but "maintenance operation timestamps" instead. These have no business meaning.

Is there any update on this?
I have Raw blob container and curated blob containers and when ever I upload, they are getting the latest datetime and hard to sync
What is the ETA if planned on this ? TIA

@zezha-msft If LastWriteTimeUTC and CreateTimeUTC are used as the metadata property names (by convention), then any application (including AZCopy) could read / modify these attribute fields. This would not require and service level change to accomodate (i.e., to add an lmt field) since this would use the existing metadata fields.  These property names would simply be by convention, which AZCopy could write by default (or at least if a --put-timestamps switch was specified).

Of course, having two dedicated properties for this would be a great service extension. :)

Hi @leswaters @vansree, thanks for following up on this feature. We are actively working on it: https://github.com/Azure/azure-storage-azcopy/pull/1780
The new feature will allow the user to preserve POSIX attributes, including the timestamps, on blobs as metadata.

Released in 10.16.

This is not very useful for microsoft operating systems.
failed to parse user input due to error: in order to use --preserve-posix-properties, both the source and destination must be POSIX-aware (Linux->Blob, Blob->Linux, Blob->Blob)

Like @thierrylach said this doesn't work for windows os.
@zezha-msft are there any plans to implement it for windows?

Upvote for implementation on Windows

Looks like there's no hope in supporting this on windows as they have closed the issue that was created to track the effort. Oh, well :(

Closing this and leaving Windows without a solution is very unhelpful.
We need to be able to retain file timestamps and as far as I can see with the Metadata workaround it means uploading each individual file to Azure because you can't dynamically apply metadata for each file within a bulk upload, using recursive upload with azcopy of a folder of say 1000 local items would put the same metadata on all 1000. I'm not sure if this massively increases the overhead or if it inflates the actions count.
There must be a wider need for retaining the true timestamps of files from windows origin surely?


Whitelisting s3.amazonaws.com necessary for crazy egg

Whitelisting s3 necessary for crazy egg
Changes

Modified cfgov/cfgov/settings/base.py to whitelist s3.amazonaws.com.

Testing

Not sure how to test this locally. Issue can be seen by visiting https://www.consumerfinance.gov/consumer-tools/financial-well-being/ and viewing source.

Todos

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewer tool :arrow_right:

The CSP spec doesn't seem to allow whitelisting just the subdirectory, e.g. https://s3.amazonaws.com/trk.cetrk.com/*. This change seems risky as anyone can set up an S3 bucket and host a malicious script. Is there an alternative way to host the CrazyEgg script?

@chosak, you are correct. I'm closing this for now.


multiple github downloads of Metacello ... one is enough

There are multiple paths for downloading Metacello from github and during one session it should only be necessary to do it once ... can track download status of Metacello others and avoid multiple downloads

Check to make sure that it isn't multiple invocations of GsUpgrader in the script ...

evidence of a double Metacello get/load github download from a single gsUpgrader invocation:
---Step 1 of tODE bootstrap process: execute upgradeGlass.ws
-----Install GsUpgrader-Core package  from http://ss3.gemtalksystems.com/ss/gsUpgrader
-----Upgrade GLASS using gsUpgrader
======================
=====GLASS1 is loaded. Skipping GLASS upgrade.
---Step 2 of tODE bootstrap process: execute installMetacello.ws
---Step 3 of tODE bootstrap process: execute installGLASS1.ws
-----Upgrade GLASS1 using gsUpgrader
======================
=====Metacello Preview already loaded
======================
=====Upgrading Metacello
Fetched -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loaded -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loading baseline of BaselineOfMetacello...
Project: FileTree baseline
Project: Gofer stable [<IP_ADDRESS>]
Evaluated -> baseline [BaselineOfMetacello] >> reprimeRegistryIssue197
...finished baseline
	No instance migrations performed.
======================
=====Metacello Preview already loaded
======================
=====Upgrading Metacello
Fetched -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loaded -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loading baseline of BaselineOfMetacello...
Project: FileTree baseline
Project: Gofer stable [<IP_ADDRESS>]
Evaluated -> baseline [BaselineOfMetacello] >> reprimeRegistryIssue197
...finished baseline
	No instance migrations performed.

The second Metacello invocation was probably invoked by Grease or GLASS1:
======================
=====GLASS1 is loaded. Skipping GLASS upgrade.
---Step 2 of tODE bootstrap process: execute installMetacello.ws
---Step 3 of tODE bootstrap process: execute installGLASS1.ws
-----Upgrade GLASS1 using gsUpgrader
======================
=====Metacello Preview already loaded
======================
=====Upgrading Metacello
Fetched -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loaded -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loading baseline of BaselineOfMetacello...
Project: FileTree baseline
Project: Gofer stable [<IP_ADDRESS>]
Evaluated -> baseline [BaselineOfMetacello] >> reprimeRegistryIssue197
...finished baseline
	No instance migrations performed.
======================
=====Metacello Preview already loaded
======================
=====Upgrading Metacello
Fetched -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loaded -> BaselineOfMetacello-dkh.85 --- github://dalehenrich/metacello-work:master/repository [1409b64:master] --- github://dalehenrich/metacello-work:master/repository
Loading baseline of BaselineOfMetacello...
Project: FileTree baseline
Project: Gofer stable [<IP_ADDRESS>]
Evaluated -> baseline [BaselineOfMetacello] >> reprimeRegistryIssue197
...finished baseline
	No instance migrations performed.
======================
=====Upgrading Grease
Fetched -> BaselineOfGrease-dkh.9 --- github://GsDevKit/Grease:master/repository [393d061:master] --- github://GsDevKit/Grease:master/repository
Loaded -> BaselineOfGrease-dkh.9 --- github://GsDevKit/Grease:master/repository [393d061:master] --- github://GsDevKit/Grease:master/repository
Loading baseline of BaselineOfGrease...
Project: UTF8 stable [0.243]
Project: System-Digital-Signatures stable
Project: SMTPMail stable
...finished baseline
	No instance migrations performed.
======================
=====Upgrading GLASS1
Fetched -> BaselineOfGLASS1-dkh.48 --- github://glassdb/glass:master/repository [7300093:master] --- github://glassdb/glass:master/repository
Loaded -> BaselineOfGLASS1-dkh.48 --- github://glassdb/glass:master/repository [7300093:master] --- github://glassdb/glass:master/repository
Loading baseline of BaselineOfGLASS1...
Project: GoferProjectLoader stable [1.0-alpha2.2]
Project: Gofer Core <IP_ADDRESS>
Project: Gofer stable
Project: Grease baseline
Project: UTF8 stable [0.243]
Project: System-Digital-Signatures stable
Project: SMTPMail stable
Project: Metacello baseline
Project: FileTree baseline
Project: Gofer stable
Fetched -> GsSqueakCommon-Core-dkh.20 --- github://glassdb/glass:master/repository [7300093:master] --- github://glassdb/glass:master/repository
Evaluated -> 1.0-alpha2.2 [ConfigurationOfGoferProjectLoader] >> postLoadLoader
Evaluated -> baseline [BaselineOfMetacello] >> reprimeRegistryIssue197
Loaded -> GsSqueakCommon-Core-dkh.20 --- github://glassdb/glass:master/repository [7300093:master] --- cache
...finished baseline
	No instance migrations performed.


fix(su): allow board members to see the complete application

build is not passing due to temporary issues with CircleCI

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


How does the naming convention work?

I may be completely misunderstanding something, but I'm confused on two fronts. For one, it seems Amazon specifies a specific naming convention thats required to make "transforms" work, but this plugin doesn't seem to enforce that, right?
Secondly, in the readme example, the outputted fonts have, very nicely, a prepended "--font-" to them. This doesn't seem to be the default behaviour though. Are we supposed to put all our Figma font styles in a "fonts" folder? The Figma example you provided (albeit its for spacing) doesn't seem to have that naming convention.

Hey @mwargan,

Style dictionary has a specified structure that you can use to transform it. However you can customize this in the config file (the example in the transformer shows that https://github.com/lukasoppermann/design-token-transformer/blob/main/config.json)

For styles you need to prefix the names e.h. font/ to get this. This is specific to figma styles.
For custom styles you have the part in the name radii/sm → --radii-sm

I hope that helps, otherwise let me know what is still unclear.

Hey, this may be, because the name that is used is sizes and not size.
Could you maybe try to adjust your json and rename sizes to size (manually) and see if this works?
This would give us an idea of how we may be able to fix it.

Hey @lukasoppermann - on it. I've opened the relevant issue here: https://github.com/lukasoppermann/design-token-transformer/issues/4 feel free to close either and just let me know where you'd like to continue.

@lukasoppermann after further review, seems I don't have "sizes". The nearest is maybe "fontSize" in the .json file.

Okay, this is something I will have to investigate.
Normally style dictionary converts using cti syntax, but the plugin may not adhere to this format which may create the issue.
Alternatively the issue could be that the category does not match.
Can you do me a favour and add "category": "size" in the json on the gutterSize and a fontSize?
"gutterSize": {
  "category": "size",
  "value": 24,
  "type": "number",
  "unit": "pixel"
}

And afterwards try if the conversion works?

@lukasoppermann just tried adding the category key-value pair to both gutterSize and fontSize - still no dice :/

Okay. Thank you for testing it. I will look into the issue and try to solve it.

I am having this same issue, the figma plugin is exporting this:
{
    "tiny": {
        "fontFamily": {
            "type": "string",
            "value": "Avenir LT Pro"
        },
        "fontSize": {
            "type": "number",
            "unit": "pixel",
            "value": 32
        },
        "lineHeight": {
            "type": "string",
            "unit": "auto",
            "value": "normal"
        },
        ...
    }
}

But it should be this:
{
    "fontFamily": {
        "tiny": {
            "type": "string",
            "value": "Avenir LT Pro"
        }
    },
    "fontSize": {
        "tiny": {
            "type": "number",
            "unit": "pixel",
            "value": 32
        }
    },
    "lineHeight": {
        "tiny": {
            "type": "string",
            "unit": "auto",
            "value": "normal"
        }
    },
    ...
}

Hey @klarkc
is this an issue just with tailwind or does this solve the issue for amazon style dictionary?

@lukasoppermann both, the tool that I use to extract tailwind config from the exported dictionary expects CTI standard.

An option to enable / disable CTI convention on plugin settings is a viable solution?

Hey @klarkc so you tested with the inverted syntax and that solves the problem?
Adding an option to enable / disable CTI is definitely an option. Would you be interested in sending a PR?

@lukasoppermann yes it solves.
About a PR, right now I can't, but I'll try to make it as soon as possible, cause it's a big blocker here.

Just FYI @klarkc I added custom transformer examples to the design tokens transformer repo: https://github.com/lukasoppermann/design-token-transformer/blob/main/transformTokens.js so you can copy and adapt this to get the desired result.
e.g. this one matches any token on the json file that has the unit set to pixel and adds px to the end of the value.
StyleDictionary.registerTransform({
  name: 'size/px',
  type: 'value',
  matcher: token => {
    return token.unit === 'pixel' && token.value !== 0
  },
  transformer: token => {
    return `${token.value}px`
  },
})


ARROW-15598: [C++][Gandiva] Avoid using hardcoded raw pointer addresses in generated code

This change fixes sporadic crashes that happened with certain expression when caching only the generated object code. The crash was happening because the generated code contained raw hardcoded pointer addresses during building certain expressions, and when using this cache entry during subsequent times these addresses point to then invalid memory.
This change :

introduces an array of pointers that holds the pointers to function holders and in holders, that is filled up during the annotate stage passed to the generated function during execution. The generated IR contains indices to this array instead of hardcoded addresses.
includes string literal in the generated IR as a global variable instead of a raw pointer address to the process memory.

Undid the earlier change of removing the GANDIVA_ENABLE_OBJECT_CODE_CACHE flag since that code path still does a lot of unnecessary work hampering performance, which I will refactor in another PR.


Issue #356 Force google maps to use the lat/long for the location on …

…the map, not the address

Need to check if this actually fixes the problem, not so easy to reproduce


Pr test & Task2

You should not commit or push files like  .DS_store, README, external/ .
For this PR, just commit and push changes in src/battle_game/core

Code in folder src/battle_game/core looks good to me, but you had better describe your unit briefly when raising a PR


[BEAM-161] Fix decompression of a concatenation of gzip streams in CompressedSource

I pulled in the patch from<EMAIL_ADDRESS>and gave him authorship of the commit.

R: @kennknowles

LGTM

rename to BEAM-167? 161 is FAQ.

Fixed BEAM-161 -> BEAM-167 in commit history by rewording commits


Does not explain how to use connection strings

There is a fair amount of v2 code out there that starts out from a connection string (which is arguably easier to keep as a single secret), and none of the examples on this page explain how to use connection strings and migrate v2 code to v10.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dae2738c-ba71-e828-ce61-7d6ae66b06aa
Version Independent ID: ace95080-b838-40e3-2fcd-fce8da08e9de
Content: Upload, download, list, and delete blobs using Azure Storage v10 SDK for JavaScript
Content Source: articles/storage/blobs/storage-quickstart-blobs-nodejs-v10.md
Service: storage
Sub-service: blobs
GitHub Login: @mhopkins-msft
Microsoft Alias: mhopkins

@rcarmo Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

+1 on this, it's a big pain to alter from connection string to two secrets everywhere.  Furthermore this way of providing creds will not work with Azure Functions using storage emulator.   V2 was great as it automatically got the connection string from env variables.  The code to post a simple blob with v10 is now much longer and more complex than v2.


fix minio storage test

What this PR does / why we need it:
Special notes for your reviewer: fix minio storage test
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:
Fix minio storage test

/ok-to-test

Thanks @wengyao04 ! you got the milestone PR 1k :)
/lgtm
/approve

/retest


Fix dependency versions for pods

https://github.com/DylanVann/react-native-fast-image/blob/2a3438c0d0b81c81116d2e73ad7cf871da0662dd/react-native-fast-image.podspec#L23-L25
Guys I'd say is insanely unsafe to not fix a version for the pod dependencies. With the new SDWebImage update you will need to update this dependency declaration because they removed those subspecs.
I propose;

You strictly force the dependency version pod 'SDWebImage/GIF', '4.4.6' for instance.
You weakly force the dependency version pod 'SDWebImage/GIF', '~> 4' OR pod 'SDWebImage/GIF', '~> 4.4' for instance.
If you don't want to force dependency versions, I'm afraid you will need to update the package.

Hope it helps!

Some people just like to live on the edge.
Nah I agree, you're right they should be specified.


[TE] rootcause poc - chart toolbar

This PR moves (mostly) display and chart related settings from the top into a dedicated chart toolbar.

can we get a screenshot of this toolbar?


Improve fnv64a hashing algorithm by remove all allocations

Hi everyone,
Lastly I've seen 2 great tutorial how to profile and optimize Go programs. Based on that knowledge I found some small improvements in your bigcache package. I started from adding allocation reporting for all of your benchmarks. After further analysis in pprof tool it showed me that your usage of fnv64a hash function was a bit inefficient. There were 2 not necessary allocations. Here is the output of your benchmarks before the changes:

BenchmarkWriteToCacheWith1Shard-4                            	 2000000	       963 ns/op	     617 B/op	       5 allocs/op
BenchmarkWriteToLimitedCacheWithSmallInitSizeAnd1Shard-4     	 2000000	       828 ns/op	      65 B/op	       4 allocs/op
BenchmarkWriteToUnlimitedCacheWithSmallInitSizeAnd1Shard-4   	 1000000	      1591 ns/op	    3470 B/op	       4 allocs/op
BenchmarkWriteToCacheWith512Shards-4                         	 3000000	       540 ns/op	     611 B/op	       5 allocs/op
BenchmarkWriteToCacheWith1024Shards-4                        	 3000000	       537 ns/op	     611 B/op	       5 allocs/op
BenchmarkWriteToCacheWith8192Shards-4                        	 2000000	       581 ns/op	     628 B/op	       5 allocs/op
BenchmarkWriteToCacheWith1024ShardsAndSmallShardInitSize-4   	 2000000	       642 ns/op	     823 B/op	       5 allocs/op
BenchmarkReadFromCacheWith1024Shards-4                       	 5000000	       283 ns/op	      31 B/op	       4 allocs/op
BenchmarkReadFromCacheWith8192Shards-4                       	 5000000	       283 ns/op	      31 B/op	       4 allocs/op
PASS
ok  	github.com/allegro/bigcache	28.775s

Benchmark results after my changes:

BenchmarkWriteToCacheWith1Shard-4                            	 2000000	       886 ns/op	     577 B/op	       3 allocs/op
BenchmarkWriteToLimitedCacheWithSmallInitSizeAnd1Shard-4     	 2000000	       761 ns/op	      41 B/op	       2 allocs/op
BenchmarkWriteToUnlimitedCacheWithSmallInitSizeAnd1Shard-4   	 1000000	      1545 ns/op	    3446 B/op	       2 allocs/op
BenchmarkWriteToCacheWith512Shards-4                         	 3000000	       495 ns/op	     571 B/op	       3 allocs/op
BenchmarkWriteToCacheWith1024Shards-4                        	 3000000	       501 ns/op	     571 B/op	       3 allocs/op
BenchmarkWriteToCacheWith8192Shards-4                        	 3000000	       533 ns/op	     590 B/op	       3 allocs/op
BenchmarkWriteToCacheWith1024ShardsAndSmallShardInitSize-4   	 3000000	       614 ns/op	     979 B/op	       3 allocs/op
BenchmarkReadFromCacheWith1024Shards-4                       	 5000000	       261 ns/op	      15 B/op	       2 allocs/op
BenchmarkReadFromCacheWith8192Shards-4                       	 5000000	       248 ns/op	      15 B/op	       2 allocs/op
PASS
ok  	github.com/allegro/bigcache	28.084s

And comparison taken from benchcmp tool(https://godoc.org/golang.org/x/tools/cmd/benchcmp):

benchmark                                                      old ns/op     new ns/op     delta
BenchmarkWriteToCacheWith1Shard-4                              963           886           -8.00%
BenchmarkWriteToLimitedCacheWithSmallInitSizeAnd1Shard-4       828           761           -8.09%
BenchmarkWriteToUnlimitedCacheWithSmallInitSizeAnd1Shard-4     1591          1545          -2.89%
BenchmarkWriteToCacheWith512Shards-4                           540           495           -8.33%
BenchmarkWriteToCacheWith1024Shards-4                          537           501           -6.70%
BenchmarkWriteToCacheWith8192Shards-4                          581           533           -8.26%
BenchmarkWriteToCacheWith1024ShardsAndSmallShardInitSize-4     642           614           -4.36%
BenchmarkReadFromCacheWith1024Shards-4                         283           261           -7.77%
BenchmarkReadFromCacheWith8192Shards-4                         283           248           -12.37%

benchmark                                                      old allocs     new allocs     delta
BenchmarkWriteToCacheWith1Shard-4                              5              3              -40.00%
BenchmarkWriteToLimitedCacheWithSmallInitSizeAnd1Shard-4       4              2              -50.00%
BenchmarkWriteToUnlimitedCacheWithSmallInitSizeAnd1Shard-4     4              2              -50.00%
BenchmarkWriteToCacheWith512Shards-4                           5              3              -40.00%
BenchmarkWriteToCacheWith1024Shards-4                          5              3              -40.00%
BenchmarkWriteToCacheWith8192Shards-4                          5              3              -40.00%
BenchmarkWriteToCacheWith1024ShardsAndSmallShardInitSize-4     5              3              -40.00%
BenchmarkReadFromCacheWith1024Shards-4                         4              2              -50.00%
BenchmarkReadFromCacheWith8192Shards-4                         4              2              -50.00%

I've tested it against Go1.6.2 and 1.7beta1. On both versions results were better between 2-12% in ns/op. Less number of allocations should also improve the GC pauses.
The problem was that you have called fnv.New64a() every time. Under the hood it allocates bytes and it could be omit. One solution might be sync.Pool but it's not reliable in case of GC. Another is just take the Go standard library fnv64a implementation and remove the allocation which is made in New64a func.
Inspiration for this PR:
https://youtu.be/ZuQcbqYK0BY
https://youtu.be/N3PWzBeLX2M

Coverage increased (+0.009%) to 98.675% when pulling 2920ce862f05b70c81b959812a4429110381a9bd on mateuszdyminski:master into 7b000bdb362a2dad08c6e7abf5b0315b6aabc9cf on allegro:master.

Hi @mateuszdyminski
Thanks for PR. I left comments on it.

Moved implementation to fnv.go file.
Created test and benchmark for new fnv hash implementation. Here is the output from benchmark:

BenchmarkFnvHashSum64-4             100000000       11.1 ns/op     0 B/op         0 allocs/op
BenchmarkFnvHashStdLibSum64-4   20000000         67.3 ns/op   16 B/op         2 allocs/op

I also removed all ReportAllocs(). Thanks for tip with -benchmem flag.

LGTM!
@druminski would you like to review this patch?

@mateuszdyminski @janisz I have just analyzed this PR and I like it very much, great job and thanks for the contribution :)

We need to generate new benchmarks results for README

Ok, new bench results generated and updated in readme

Nice! Thanks for accepting PR : )


Retrofit 2.0

Update the sdk to use Retrofit 2.0

I don't expose the retrofit APIs directly.  What is it you're looking to get from the upgrade?

No update from reporter; closing.
@reddigfabian Feel free to re-open this if you have more info to provide!


How to configure endDate to optional?

Currently, initial endDate can be set to null, but not later on.

Hi @S-YOU
startDate and endDate are both returned by default, as the component features date range.
If you just need one date, just get the startDate of the returned value, if there's no use for endDate

Thanks for the reply.

If you just need one date, just get the startDate of the returned value, if there's no use for endDate

My usage is that endDate can be specify by user if they choose the fixed range, and also there is open date which does not have endDate. Also when editing the form, endDate can be on and off depends on the data. I can't seems to do setValue({startDate: 'validDate', endDate: null}) too.

For now, I would suggest using 2 Datepickers and enable asSingle
// start date
<Datepicker
  asSingle={true}
  useRange={false}
/>

// end date
<Datepicker
  asSingle={true}
  useRange={false}
/>

Use the first one for your start date and the other for your end date. So you can control which should be null

Great advice, thank you very much and quick reply!

Hi, just wondering if it's possible to implement an optional endDate for the single Datepicker with useRange={true}? I would like to use a single Datepicker component for that as there is limited horizontal space on my page. Thank you!

@JefteCaro

For now, I would suggest using 2 Datepickers and enable asSingle
// start date
<Datepicker
  asSingle={true}
  useRange={false}
/>

// end date
<Datepicker
  asSingle={true}
  useRange={false}
/>

Use the first one for your start date and the other for your end date. So you can control which should be null

WIth this approach, what will you set as the value for each component? Even though asSingle is set to true, the component seems to expect a value object containing startDate and endDate. And when you provide that value, it uses the start date.


Pack sse throttle handler

$subject

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.15 out of 16 committers have signed the CLA.:white_check_mark: hisanhunais:white_check_mark: mushthaq33:white_check_mark: chashikajw:white_check_mark: arunans23:white_check_mark: ruks:white_check_mark: wasuradananjith:white_check_mark: Chamindu36:white_check_mark: tharindu1st:white_check_mark: rmsamitha:white_check_mark: Nirothipan:white_check_mark: CrowleyRajapakse:white_check_mark: malinthaprasan:white_check_mark: uvindra:white_check_mark: HeshanSudarshana:white_check_mark: TheRasanjana:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.


[Bug] Inegration not starts after update to 0.23.0b0

The problem
After update to latest version 0.23.0b0 integration fails to start, rollback to 0.22.0 makes all work as expected again
Logger: homeassistant.config_entries
Source: config_entries.py:399
First occurred: 20:56:47 (3 occurrences)
Last logged: 20:58:05
Error setting up entry <IP_ADDRESS> for asusrouter
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 399, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/asusrouter/init.py", line 26, in async_setup_entry
await router.setup()
File "/config/custom_components/asusrouter/router.py", line 352, in setup
await self._init_sensor_coordinators()
File "/config/custom_components/asusrouter/router.py", line 563, in _init_sensor_coordinators
available_sensors = await self.bridge.async_get_available_sensors()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/asusrouter/bridge.py", line 224, in async_get_available_sensors
SENSORS: await self._get_sensors_sysinfo(),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/asusrouter/bridge.py", line 494, in _get_sensors_sysinfo
return await self._get_sensors(
^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/asusrouter/bridge.py", line 441, in _get_sensors
process(data) if process is not None else self._process_sensors(data)
^^^^^^^^^^^^^
File "/config/custom_components/asusrouter/bridge.py", line 564, in _process_sensors_sysinfo
if sensor_type in raw:
^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable
Your device model
Zenwifi Pro XT12
Firmware type
Stock
Firmware version
<IP_ADDRESS>.388_22127
Integration version with the issue
0.23.0b0
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
Core 2023.10.5
Is there anything useful in the logs?
Logger: homeassistant.config_entries
Source: config_entries.py:399
First occurred: 20:56:47 (3 occurrences)
Last logged: 20:58:05

Error setting up entry <IP_ADDRESS> for asusrouter
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 399, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/asusrouter/__init__.py", line 26, in async_setup_entry
    await router.setup()
  File "/config/custom_components/asusrouter/router.py", line 352, in setup
    await self._init_sensor_coordinators()
  File "/config/custom_components/asusrouter/router.py", line 563, in _init_sensor_coordinators
    available_sensors = await self.bridge.async_get_available_sensors()
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/asusrouter/bridge.py", line 224, in async_get_available_sensors
    SENSORS: await self._get_sensors_sysinfo(),
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/asusrouter/bridge.py", line 494, in _get_sensors_sysinfo
    return await self._get_sensors(
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/asusrouter/bridge.py", line 441, in _get_sensors
    process(data) if process is not None else self._process_sensors(data)
    ^^^^^^^^^^^^^
  File "/config/custom_components/asusrouter/bridge.py", line 564, in _process_sensors_sysinfo
    if sensor_type in raw:
       ^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable

Diagnostics information
No response
Additional information
No response

Hello. Sorry for the issue you are experiencing. I am already working on it

No problem happy to try and help find issues! 😊

@smarthomefamilyverrips, please, check whether it works now with 0.23.0b1

@Vaskivskyi now all seems to work as expected 👍🏻

Great! 👍🏻


[Genre] Select all/Deselect all

Add buttons to automatically add all and remove them from DiggerModel.

Might be easier to implement in presenter like:
genreList.forEach(genre => {
    props.model.addGenre(genre); /* or removeGenre depending on the function */
}

To not repeat much more code.


feature: support streaming large logs

adds support for streaming log file downloads to be able to support handling large log files.
Depends on https://github.com/Netflix/metaflow/pull/1856
Development environment changes:

mounts .aws folder in development docker-compose in order to provide S3 access for the local UI backend

TODO:

[ ] cleanup dependency changes due to temporarily installing the Metaflow client from a git branch

superseded


the dataset can not download !

sorry, I can not finish the downloading of the training dataset !  and I find that it is defferent from the shapenet dataset on https://www.shapenet.org/ ! Does anyone meet this problem? I want to how to convert right data！

All the dataset was converted to .dat format using point clouds, normal & camera intrinsics data generated from Shapenet dataset. Not sure how the .dat file has been created for dataset to train.

Thank you very much ! The problem was solved ! Hope you are well!
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2019年4月26日(星期五) 晚上8:30
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS><EMAIL_ADDRESS>主题: Re: [nywang16/Pixel2Mesh] the dataset can not download ! (#41)
All the dataset was converted to .dat format using point clouds, normal & camera intrinsics data generated from Shapenet dataset. Not sure how the .dat file has been created for dataset to train.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Can you tell me how you generated the dat format for your own dataset?

We have released the code for the dataset, please refer to GenerateData. If there are no further questions, I will temporarily close the issue.

Hi,
Do you know how to download the dataset and unzip it?

Hi,
Do you know how to download the dataset and unzip it from the link below?
https://drive.google.com/open?id=131dH36qXCabym1JjSmEpSQZg4dmZVQid


i18n framework

Description
Partially addresses #2426, #2468
This PR adds an i18n framework that we can work with.

automatically detect browser's language using the navigator detector in i18next-browser-languagedetector
adds a selector in the settings to choose between languages
persists chosen language in local storage automatically through i18next-browser-languagedetector.

Things to note
Some translations were done for  NavigationBar and Dropdown to demonstrate how the strings might be internationalized over time and some of the potential problems we might encounter.

Possible structure for translation files
There is only one translation file in this PR currently, but they could be organized into namespaces in the following manner.
/locales
  /en
    commons.json     //for all the components in commons
    academy.json
    achievement.json
    ...        //one json for each page

Applying translation at the correct level
In Dropdown, the useTranslation hook and the translate function was applied directly to the strings since these are located within the component itself.
const Dropdown: React.FC = () => {
  ...
  const { t } = useTranslation('translation', { keyPrefix: 'dropdown' })
  ...
  const myCourses = isLoggedIn ? (
    <MenuItem icon={IconNames.PROPERTIES} onClick={toggleMyCoursesOpen} text={ t('My Courses') } />
  ) : null;

However, the strings in NavigationBar are not located in the component. For example, some of the strings are found hardcoded as part of the many list entries in AcademyNavigationBar.tsx > getStaffNavLinkInfo. Furthermore, these entries are then passed into filterNotificationsByType, where a string comparison is performed between the entry's string and a hardcoded string. If we applied translation directly to the entry's string, a translated string would always fail this comparison, causing some logic to break. Therefore, translation is only applied at the rendering level.
<div className={classNames(navbarEntry.hiddenInBreakpoints?.map(bp => `hidden-${bp}`))}>
  <Translation keyPrefix={"navigationBar"}>
    {(t) => t(navbarEntry.text)}
  </Translation>
</div>

  export function filterNotificationsByType(
    assessmentType: AssessmentType
  ): NotificationFilterFunction {
    return (notifications: Notification[]) =>
      notifications.filter(n => {
        if (assessmentType === 'Grading') {
          return n.submission_id !== undefined;
        }
        return !n.submission_id && assessmentType === n.assessment_type;
      });
  }

https://github.com/source-academy/frontend/assets/72195240/847f3196-4bb6-4df0-a22f-3e11008d2734
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Code quality improvements

Checklist

[x] I have tested this code

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

5 of 13 (38.46%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 33.087%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/navigationBar/NavigationBar.tsx
0
2
0.0%

src/commons/dropdown/LocaleSelector.tsx
2
8
25.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
5282

Relevant Lines:
14855

💛  - Coveralls

thanks for the review @RichDom2185

we plan to bring more than just basic UI strings in the long run (see https://github.com/source-academy/frontend/issues/1943 for an example). Or even the sublanguage intro tab (with dynamic links):

i18next supports complex UI strings with the Trans component . The next step would definitely be identifying and externalizing all the English strings in the repo to follow i18n.
Actual translation can take place alongside this process.

design of using separate namespaces for different parts

Originally, i wanted to have a json file for each component containing strings, however, combining them into a nested structure is tricky and each separate json file is considered a namespace by i18next. Furthermore, the location of a string and where the translation is applied might be different, so there is less meaning to having one json file to each component.
I think namespacing will become clearer as more strings get externalized. My only concern is that the "commons" namespace will contain majority of the translated strings since most components are located under the commons directory, which might make it difficult for a translator to track down a string belonging to which component.


An OGR Driver would be nice

http://www.gdal.org/ogr_formats.html

That would be worth investigating. Is there documentation on OGR driver implementation?

http://www.gdal.org/ogr_drivertut.html

There is also a golang wrapper for gdal (havent really tried it) https://github.com/lukeroth/gdal

Thanks. This information is helpful.

fwiw, I would be looking toward eventually using tile38 as a data provider for tegola http://tegola.io/ an ogr driver would be helpful to get any ogr compliant data into a data store using ogr2ogr


[Enhancement] Use object instead of pointer for HyperLogLog::_hash_set

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Problem Summary(Required) ：

#6885 uses pointer instead of object for HyperLogLog::_hash_set to reduce memory usage of HLL and not include phmap.h in hll.h.
However, as for reading HLL column from disk,

using pointer will allocate memory 4096 times for  HLL hash_set of 4096 rows in a chunk,
while using object only need allocate 1 times for a chunk by _pool.reserve.

template <typename T>
bool ObjectColumn<T>::append_strings(const Buffer<starrocks::Slice>& strs) {
    _pool.reserve(_pool.size() + strs.size());
    for (const Slice& s : strs) {
        _pool.emplace_back(s);
    }

And using object doesn't cost much more than using pointer.

the empty flat_hash_set<uint64_t> is not very large, only with 32 bytes,
while using pointer costs 8 bytes.

    ctrl_t* ctrl_ = EmptyGroup(); // [(capacity + 1) * ctrl_t]
    slot_type* slots_ = nullptr;  // [capacity * slot_type]
    size_t size_ = 0;             // number of full slots
    size_t capacity_ = 0;         // total number of slots

Therefore, this PR uses object instead of pointer again.
Test
Environment

3 BE (each 16 vCPUs and 64GB RAM)
ssb_100g
Query is as follows, where v2 is  a HLL column, table contains 6e8 rows.

select hll_union_agg(v2) / 2 as a from lineorder_flat_bitmap_hll

Result

2.1: 1.5s
main-Before PR: 3s
main-After PR: 1.5s

run starrocks_admit_test

run starrocks_admit_test


Code cleanup in tests/

Some code cleanups in the tests/ directory
Improve gomega matchers under tests/ by
changing all Expect(len(var)).To(Equal(some-length)) to
Expect(var).To(HaveLen(some-length)) in tests/
If the expected length is 0, the the new matcher is BeEmpty().
Also, in tests/vmi_configuration_test.go:

remove if len(collection) > 0, before for range collection because
the range loop just skips empty collection and there is no need to check it.
replace if condition {return true} else {return false} by return condition.

None

/retest

/lgtm

/test pull-kubevirt-e2e-kind-1.22-sriov-nonroot
/test pull-kubevirt-e2e-k8s-1.23-sig-storage-nonroot
/test pull-kubevirt-e2e-k8s-1.23-sig-compute-migrations-nonroot

/retest

/test pull-kubevirt-e2e-kind-1.23-vgpu
/test pull-kubevirt-e2e-k8s-1.23-sig-storage-cgroupsv2

pull-kubevirt-e2e-kind-1.22-sriov

/test pull-kubevirt-e2e-kind-1.22-sriov


Gracefully shutdown grpc servers

Motivation
Closes #4867
Changes
Makes a call to graceful stop before force closing open connections.
Test Plan
See that CI is passing
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

This PR requires some investigation, it has uncovered a problem with our proof verification code.
TestSpacemeshApp_NodeService fails with the following output:
2023-08-25T08:24:40.4151030Z fatal error: unexpected signal during runtime execution
2023-08-25T08:24:40.4177990Z [signal SIGSEGV: segmentation violation code=0x2 addr=0x135edd74c pc=0x135edd74c]
2023-08-25T08:24:40.4178240Z
2023-08-25T08:24:40.4178320Z runtime stack:
2023-08-25T08:24:40.4178530Z runtime.throw({0x10462f78a?, 0x1790c9890?})
2023-08-25T08:24:40.4179340Z 	/Users/aviv/actions-runner/_work/_tool/go/1.20.5/arm64/src/runtime/panic.go:1047 +0x40 fp=0x1790c97e0 sp=0x1790c97b0 pc=0x102d88060
2023-08-25T08:24:40.4183330Z runtime.sigpanic()
2023-08-25T08:24:40.4183800Z 	/Users/aviv/actions-runner/_work/_tool/go/1.20.5/arm64/src/runtime/signal_unix.go:825 +0x244 fp=0x1790c9820 sp=0x1790c97e0 pc=0x102da1324
2023-08-25T08:24:40.4184020Z
2023-08-25T08:24:40.4184120Z goroutine 1732 [syscall]:
2023-08-25T08:24:40.4190400Z runtime.cgocall(0x1042fd5c4, 0xc00050b698)
2023-08-25T08:24:40.4190910Z 	/Users/aviv/actions-runner/_work/_tool/go/1.20.5/arm64/src/runtime/cgocall.go:157 +0x68 fp=0xc00050b660 sp=0xc00050b620 pc=0x102d52f58
2023-08-25T08:24:40.4191360Z github.com/spacemeshos/post/internal/postrs._Cfunc_verify_proof(0x13022da30, {0x2, {0xc00314c00c, 0x4, 0x4}, 0x0, {0xc000202120, 0x20, 0x20}}, 0xc00024a070, ...)
2023-08-25T08:24:40.4191750Z 	_cgo_gotypes.go:454 +0x4c fp=0xc00050b690 sp=0xc00050b660 pc=0x10364fe3c
2023-08-25T08:24:40.4192160Z github.com/spacemeshos/post/internal/postrs.(*Verifier).VerifyProof.func1(0xc000a58750, {0x2, {0xc00314c00c, 0x4, 0x4}, 0x0, {0xc000202120, 0x20, 0x20}}, 0x104c10f20?, ...)
2023-08-25T08:24:40.4192630Z 	/Users/aviv/go/pkg/mod/github.com/spacemeshos/post@v0.9.2/internal/postrs/proof.go:249 +0x150 fp=0xc00050b830 sp=0xc00050b690 pc=0x103653cc0
2023-08-25T08:24:40.4195930Z github.com/spacemeshos/post/internal/postrs.(*Verifier).VerifyProof(0x104c31d00?, 0xc001cca030, 0xc002aab260, 0xc0006aaee0, 0x1a, 0x4, 0x25, {0xff, 0xff, 0xff, ...}, ...)
2023-08-25T08:24:40.4196490Z 	/Users/aviv/go/pkg/mod/github.com/spacemeshos/post@v0.9.2/internal/postrs/proof.go:249 +0x878 fp=0xc00050baf0 sp=0xc00050b830 pc=0x1036539e8
2023-08-25T08:24:40.4196930Z github.com/spacemeshos/post/verifying.(*ProofVerifier).Verify(0xc000011328, 0x102d9d4e8?, 0xc002aab260, {0x2, 0x4, 0x20, 0x1a, 0x4, 0x25, {0xff, ...}}, ...)
2023-08-25T08:24:40.4197380Z 	/Users/aviv/go/pkg/mod/github.com/spacemeshos/post@v0.9.2/verifying/verifying.go:104 +0x288 fp=0xc00050bc10 sp=0xc00050baf0 pc=0x103658298
2023-08-25T08:24:40.4197910Z github.com/spacemeshos/go-spacemesh/activation.(*postVerifier).Verify(0xc0006da540, {0x104ed68e8, 0xc0001b6018}, 0x0?, 0xc002aab260, {0xc0006fe008, 0x1, 0x1})
2023-08-25T08:24:40.4198460Z 	/Users/aviv/actions-runner/_work/go-spacemesh/go-spacemesh/activation/post_verifier.go:44 +0x214 fp=0xc00050bdd0 sp=0xc00050bc10 pc=0x1040d7374
2023-08-25T08:24:40.4198940Z github.com/spacemeshos/go-spacemesh/activation.(*postVerifierWorker).start(0xc0011fee10, {0x104ed68e8, 0xc0001b6018})
2023-08-25T08:24:40.4199480Z 	/Users/aviv/actions-runner/_work/go-spacemesh/go-spacemesh/activation/post_verifier.go:131 +0x114 fp=0xc00050bed0 sp=0xc00050bdd0 pc=0x1040d83e4
2023-08-25T08:24:40.4199930Z github.com/spacemeshos/go-spacemesh/activation.(*OffloadingPostVerifier).Start.func1()
2023-08-25T08:24:40.4200490Z 	/Users/aviv/actions-runner/_work/go-spacemesh/go-spacemesh/activation/post_verifier.go:85 +0x48 fp=0xc00050bf20 sp=0xc00050bed0 pc=0x1040d7d98
2023-08-25T08:24:40.4200830Z golang.org/x/sync/errgroup.(*Group).Go.func1()
2023-08-25T08:24:40.4201180Z 	/Users/aviv/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:75 +0x70 fp=0xc00050bfd0 sp=0xc00050bf20 pc=0x1035eebd0
2023-08-25T08:24:40.4201450Z runtime.goexit()
2023-08-25T08:24:40.4201860Z 	/Users/aviv/actions-runner/_work/_tool/go/1.20.5/arm64/src/runtime/asm_arm64.s:1172 +0x4 fp=0xc00050bfd0 sp=0xc00050bfd0 pc=0x102dc1344
2023-08-25T08:24:40.4202190Z created by golang.org/x/sync/errgroup.(*Group).Go
2023-08-25T08:24:40.4202500Z 	/Users/aviv/go/pkg/mod/golang.org/x/sync@v0.3.0/errgroup/errgroup.go:72 +0x110

Full logs can be found here: https://github.com/spacemeshos/go-spacemesh/actions/runs/5973555476/job/16206053208?pr=4897
From what I can see it looks like there is a problem calling close on OffloadingPostVerifier while its workers are in the process of verifying a proof.

It looks like a race between  postrs.(*Verifier).VerifyProof and postrs.(*Verifier).Close which would explain why we only see it in some CI runs. Maybe @poszu can take a look? 🙂

bors merge


@vitejs/plugin-legacy doesn't work on ie11, the script isn't executed and it isn't transpiled.

Describe the bug
I am trying to run my application on IE 11, it's using react and typescript, but the transpiled scripts do not work at all.
The index.html page is loaded but it stays blank with and the script doesn't run.
I have setup a vanilla vite app to see if it was my React+Typescript setup and the problem also happens in the vanilla app, which I liked in the repo.
I also put an alert in the js to see if that would fire, but nothing happened, I also have no errors on the console.

The HTML file is loaded though:

The script file seems to have been downloaded even though it wasn't executed.

Also, I'm pretty sure IE11 wouldn't like import './style.css'; or the template string if the script was running.
I used the default vite.config.js from @vitejs/plugin-legacy for this:
import legacy from "@vitejs/plugin-legacy";

export default {
  plugins: [
    legacy({
      // for ie11
      targets: ["ie >= 11"],
      additionalLegacyPolyfills: ["regenerator-runtime/runtime"],
    }),
  ],
};

Removing type="module" from the script tag seems to allow the script to run but I don't know if it's a good idea to do that because I'm not too sure if vite needs that for any reason.
Also, as suspected, even though the script runs, I get syntax errors due to the code not being transpiled to js that is compatible with IE 11.
I don't know what to do here, any help is appreciated.
Thanks in advance.
Reproduction
https://github.com/ericmackrodt/vitejs-vite-wgu8t4
System Info
System:
    OS: macOS 11.5.1
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
    Memory: 629.89 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.15 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 97.0.4692.71
    Chrome Canary: 98.0.4743.0
    Firefox: 96.0.1
    Safari: 14.1.2
  npmPackages:
    @vitejs/plugin-legacy: ^1.6.4 => 1.6.4
    vite: ^2.7.2 => 2.7.13

Used Package Manager
yarn
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Do you use yarn build and using files in the dist folder?
The @vite/plugin-legacy only affects build mode.

How to do if some compatible bugs that we want to debugger in dev？

Do you use yarn build and using files in the dist folder? The @vite/plugin-legacy only affects build mode.
How to do if we want to debugger some compatible bugs in dev Env?

Do you use yarn build and using files in the dist folder? The @vite/plugin-legacy only affects build mode.
How to do if we want to debugger some compatible bugs in dev Env?

yarn build
yarn preview

so no Hmr mode ?

so no Hmr mode ?

so no Hmr mode ?

Vite provides fast dev env in the modern browsers, but not in IE11.
The @vite/plugin-legacy provides a prod legacy build for users.

The @vite/plugin-legacy only affects build mode.

The documentation doesn't make this clear enough.
The very first line of the documentation should say this on bold letters:
@vite/plugin-legacy only affects build mode, not dev mode!


Feature/#21.sequence equal

Coverage decreased (-0.1%) to 99.882% when pulling b0d603c6984e9083db1d49368026332cf5ae0b71 on nikolalukovic:feature/#21.SequenceEqual into da4900e8494f41d9c26e26483e21cf8a7d500dca on isc30:master.

in Linq.ts:
add export for EqualityComparer and StrictEqualityComparer

I'm curious, are you contributing in your spare time or you will use it at work?
You won (by far) the first contributor medal haha

Both actually. I'll definitely need something like this at work. And i'm able to work on this in both spare time and on work.

Hi there!
I'll have some free time, do you want me to finish those small changes + merge?

Hey, that would be great! Sorry for leaving the pr like this, i just don't have time currently...

haha don't worry I've also been busy af. Thanks a lot for your contribution!