Cannot get utf-8 text mail to show correctly

I am using Python 3 to send mail to the server:
import	traceback
import	smtplib
from	email.mime.text		import	MIMEText
from	email.mime.multipart 	import	MIMEMultipart

def sendmail(s_from : str, s_to : str, s_srv : str, s_txt='', s_html='', s_subj='', i_port=2525, s_login='', s_pw=''):

	assert(s_from > '' and '@' in s_from), 			f'No or invalid email receiver: {s_from}'
	assert(s_to > '' and '@' in s_from), 			f'No or invalid email sender: {s_to}'
	assert(s_srv > ''), 					'SMTP server not specified'
	assert(s_subj or s_txt or s_html), 			'Either subject, text or html must be specified'
	assert(s_login and s_pw or not (s_login or s_pw)),	'Login and password must either both be specified or not at all'

	msg 			=	MIMEMultipart('alternative')
	msg['Subject']		=	s_subj
	msg['From']		=	s_from
	msg['To']		=	s_to

	if s_txt:
		mime_txt	=	MIMEText(s_txt, 'plain', 'utf-8')
		msg.attach(mime_txt)
	if s_html:
		mime_html	=	MIMEText(s_html, 'html', 'utf-8')
		msg.attach(mime_html)

	smtp_srv		=	smtplib.SMTP(s_srv, i_port)
	if s_login:
		smtp_srv.login(s_login, s_pw)

	smtp_srv.sendmail(s_from, s_to, msg.as_string() )

def main():

	try:
		sendmail(
			s_from	=<EMAIL_ADDRESS>			s_to	=<EMAIL_ADDRESS>			s_srv	=	'localhost',
			s_txt	=	'Pure text body',
			s_html	=	'
HTML Header body
Normal body text',
			s_subj	=	'This is subject text'
			)

	except:
		li_s_err = str(traceback.format_exc()).split('\n')
		for s_err in li_s_err:
			print(s_err)

main()

If I remove the , 'utf-8 parameter in the two calls to MIMEText, the body of the email is displayed correctly.
Otherwise, it is displayed in mailslurper as PGgzPkhUTUwgSGVhZGVyIGJvZHk8L2gzPjxiPk5vcm1hbCBib2R5IHRleHQ8L2I+
Am I using the email.mime or smtplib modules wrongly, or is there a problem with mailslurper?

I'm having a smiliar issue. In the database the body mail is stored as follows:
https://pastebin.com/Rqvsk19K
In the mailsurper frontend it get's rendered like this:

I cannot click the links inside the e-mail nor read it properly. The email is stored as contentType 'text/html; charset="utf-8"' in the database.


 This might be better to do in reanalyze itself though? Or we can have an action in the editor that uses the editor to apply the edits. That would be easy to do as a first step. Although it'd only work in VSCode at first.

Removing types is much more involved, and unclear how to do automatically. E.g. one variant case.


How to log the errors for RunSqlScripts task?

It appears the Invoke-sqlcmd has a bug in it
https://connect.microsoft.com/SQLServer/feedback/details/779320/invoke-sqlcmd-does-not-return-t-sql-errors.
From what I've read on Stackoverflow, the bug has been fixed in SQL 2014 (I'm guessing this has to be the powershell modules on your build server).

All issues have new been fixed in new version

Hi Andrew,
Thanks for getting it fixed.
However the fix to drop the PowerShell SQLCMD increases issue for us.
The build service account would have ddl_admin, ddl_datawriter and ddl_datareader role membership and DBAs and Governance does not want the build account to modify the security/permissions of the database to be automated.
We are using SSDT for database development and using the SQLPackage.exe to generate to DeployReport and Scripts which DBAs will verify before they approve the deployment in UAT/PROD.
As you know the scripts generated by from dacpac by SSDT or SQLPackage.exe requires SQLCMD to be enabled.
We found your SQLToolkit to be perfect fit in the planned automation process, where it allowed the DBAs to review the Deploy report and scripts before they approve deployment except error logging within TFS.
If you can please re-enable(or have the different task for) the PowerShell  version, that would be great. I will find a workaround to see the errors if error logging cannot be fixed with Powershell SQLCMD option.
Regards
Dipen
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: Andrew Lackenby<EMAIL_ADDRESS>Sent: Thursday, 9 March 2017 9:30 PM
To: crimdon/SQLToolkit<EMAIL_ADDRESS>Cc: Dipen Patel<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [crimdon/SQLToolkit] How to log the errors for RunSqlScripts task? (#17)
All issues have new been fixed in new version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/crimdon/SQLToolkit/issues/17#issuecomment-285314744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYnA4eB9STaTBPLHlB8CeqLi9A-uHlHwks5rj9SSgaJpZM4MO3rq.
This email is intended for the addressee(s) named and may contain confidential and/or privileged information.
If you are not the intended recipient, please notify the sender and then delete it immediately.
Any views expressed in this email are those of the individual sender except where the sender expressly and with authority states them to be the views of the NSW Office of Environment and Heritage.
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL

Hi Dipen,
It looks handler I added to get some advanced logging from the DACPAC needed higher permissions. I'll try and pin that down more but until then, I've re-released the the toolkit and made the advanced logging optional on the DACPAC task.
Regards,
Andrew Lackenby

From: dipenpatelOEH<EMAIL_ADDRESS>Sent: 09 March 2017 22:41:00
To: crimdon/SQLToolkit
Cc: Andrew Lackenby; State change
Subject: Re: [crimdon/SQLToolkit] How to log the errors for RunSqlScripts task? (#17)
Hi Andrew,
Thanks for getting it fixed.
However the fix to drop the PowerShell SQLCMD increases issue for us.
The build service account would have ddl_admin, ddl_datawriter and ddl_datareader role membership and DBAs and Governance does not want the build account to modify the security/permissions of the database to be automated.
We are using SSDT for database development and using the SQLPackage.exe to generate to DeployReport and Scripts which DBAs will verify before they approve the deployment in UAT/PROD.
As you know the scripts generated by from dacpac by SSDT or SQLPackage.exe requires SQLCMD to be enabled.
We found your SQLToolkit to be perfect fit in the planned automation process, where it allowed the DBAs to review the Deploy report and scripts before they approve deployment except error logging within TFS.
If you can please re-enable(or have the different task for) the PowerShell version, that would be great. I will find a workaround to see the errors if error logging cannot be fixed with Powershell SQLCMD option.
Regards
Dipen
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: Andrew Lackenby<EMAIL_ADDRESS>Sent: Thursday, 9 March 2017 9:30 PM
To: crimdon/SQLToolkit<EMAIL_ADDRESS>Cc: Dipen Patel<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [crimdon/SQLToolkit] How to log the errors for RunSqlScripts task? (#17)
All issues have new been fixed in new version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/crimdon/SQLToolkit/issues/17#issuecomment-285314744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYnA4eB9STaTBPLHlB8CeqLi9A-uHlHwks5rj9SSgaJpZM4MO3rq.
This email is intended for the addressee(s) named and may contain confidential and/or privileged information.
If you are not the intended recipient, please notify the sender and then delete it immediately.
Any views expressed in this email are those of the individual sender except where the sender expressly and with authority states them to be the views of the NSW Office of Environment and Heritage.
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/crimdon/SQLToolkit/issues/17#issuecomment-285507101, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AREpckQUolralDsYZc2N-Puv-EVcPi9Hks5rkH_8gaJpZM4MO3rq.

Hi Dipen,
Just managed to do a bit more testing and the minimum per permissions I needed to give myself (for quite a simple package) was db_ddladmin and db_securityadmin. Anything else produced a permissions error when applying the DACPAC.
Regards,
Andrew Lackenby

From: dipenpatelOEH<EMAIL_ADDRESS>Sent: 09 March 2017 22:41:00
To: crimdon/SQLToolkit
Cc: Andrew Lackenby; State change
Subject: Re: [crimdon/SQLToolkit] How to log the errors for RunSqlScripts task? (#17)
Hi Andrew,
Thanks for getting it fixed.
However the fix to drop the PowerShell SQLCMD increases issue for us.
The build service account would have ddl_admin, ddl_datawriter and ddl_datareader role membership and DBAs and Governance does not want the build account to modify the security/permissions of the database to be automated.
We are using SSDT for database development and using the SQLPackage.exe to generate to DeployReport and Scripts which DBAs will verify before they approve the deployment in UAT/PROD.
As you know the scripts generated by from dacpac by SSDT or SQLPackage.exe requires SQLCMD to be enabled.
We found your SQLToolkit to be perfect fit in the planned automation process, where it allowed the DBAs to review the Deploy report and scripts before they approve deployment except error logging within TFS.
If you can please re-enable(or have the different task for) the PowerShell version, that would be great. I will find a workaround to see the errors if error logging cannot be fixed with Powershell SQLCMD option.
Regards
Dipen
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>From: Andrew Lackenby<EMAIL_ADDRESS>Sent: Thursday, 9 March 2017 9:30 PM
To: crimdon/SQLToolkit<EMAIL_ADDRESS>Cc: Dipen Patel<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [crimdon/SQLToolkit] How to log the errors for RunSqlScripts task? (#17)
All issues have new been fixed in new version
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/crimdon/SQLToolkit/issues/17#issuecomment-285314744, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYnA4eB9STaTBPLHlB8CeqLi9A-uHlHwks5rj9SSgaJpZM4MO3rq.
This email is intended for the addressee(s) named and may contain confidential and/or privileged information.
If you are not the intended recipient, please notify the sender and then delete it immediately.
Any views expressed in this email are those of the individual sender except where the sender expressly and with authority states them to be the views of the NSW Office of Environment and Heritage.
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/crimdon/SQLToolkit/issues/17#issuecomment-285507101, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AREpckQUolralDsYZc2N-Puv-EVcPi9Hks5rkH_8gaJpZM4MO3rq.


NO-ISSUE: Relax cri-o versioning requirement before full transition to 1.32

Created a follow-up USHIFT-5108 issue to fix the version requirements in 4.19 branch.

/test ?

/test ocp-full-conformance-rhel-eus

/override ci/prow/e2e-aws-tests-bootc ci/prow/e2e-aws-tests-bootc-arm


Kill sky_server by port instead of pid

We seem to have trouble killing sky_server by its pid. Instead, lets try
killing it by looking up which process is listening on the sky_server port.

This is hacks upon hacks, but lgtm.


Commissioning failed with error 32 for ESP32/M5 board and iOS chip tool (changed PID to 0xFEFF)

Problem
I'm unable to pair a M5/ESP32 board using recent Matter SHA cfab82d3a63fd4e035cca03c4063bb96079a27d9. Looks like there are commissioning failures.
This was working yesterday with 983fedfcbc38909d73b80f8b5c1d2d8ac163d0ff
Steps to reproduce:

Build iOS chip tool app & M5 board with cfab82d3a63fd4e035cca03c4063bb96079a27d9
Launch iOS chip tool app, scan in QR code to pair to start pairing

In step 2, looks like commissioning fails..seen this 100% with 2 boards
unable-to-pair-M5board-2-10-sha-chiptool-logs.txt
unable-to-pair-M5board-2-10-SHA-m5-logs.txt
M5 logs:
E (114848) chip[SVR]: Commissioning failed with error 32
E (114848) chip[SVR]: Commissioning failed (attempt 1): Error CHIP:0x00000032
On chip tool log:
2022-02-10 10:24:18.162827-0800  localhost CHIPTool[15969]: (CHIP) [com.zigbee.chip:all] ð´ [1644517458162] [15969:610610] CHIP: [CTL] Failed in verifying 'Attestation Information' command received from the device: err 605. Look at AttestationVerificationResult enum to understand the errors
2022-02-10 10:24:18.162852-0800  localhost CHIPTool[15969]: (CHIP) [com.zigbee.chip:all] ð´ [1644517458162] [15969:610610] CHIP: [CTL] Failed to perform commissioning step 8
2022-02-10 10:24:18.162871-0800  localhost CHIPTool[15969]: (CHIP) [com.zigbee.chip:all] ðµ [1644517458162] [15969:610610] CHIP: [CTL] Rendezvous cleanup
2022-02-10 10:24:18.162901-0800  localhost CHIPTool[15969]: (CHIP) DevicePairingDelegate Commissioning complete. NodeId 3 Status ../../../../../../../../../../../connectedhomeip/src/controller/CHIPDeviceController.cpp:1113: CHIP Error 0x000000AC: Internal error

OK. looks like if I keep the default VID : 0xFFF1, PID: 0x8000 pairing worked.. when I changed the PID: 0xFEFF or FEFE pairing fails

Was the PID changed in the attestation cert too?

No it wasn't. I didn't realize device attestation was enabled today. if there are steps add PID to attestation cert I can try

@cecille is there a script that can be run to regenerate the bits in ExampleDACs.cpp as needed?

It's on my list of things to do today - I haven't had a chance to clean it up yet. You can use the chip-cert tool to generate attestation certs that are signed by the PAI, but it's not completely straightforward how to get those into the correct format. If you wait until this afternoon, I should have something up.

https://github.com/project-chip/connectedhomeip/pull/15107

^ In order to add a new PID, you would need to add that PID to the for loop in the main function, then re-run. It will generate the required certs and keys and add them to the ExampleDACs.* files.

thanks using PID range 0x8000-0x8063 is working fine

Is it OK to close this issue now?

closing issue


⚠ Bofrost.at has degraded performance

In e31e582, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1652 ms

Resolved: Bofrost.at performance has improved in effe134 after 6 minutes.


Customize automatic generation of release notes

Added a configuration file that defines the categories to be used in
the release notes generated by GitHub.
This is for #164

LGTM, and I might start to "steal" your release process now 😆

no worries, we stole it too (from the Eclipse Ankaios project) :rofl:


addional console print when using rerun

At the moment we using cucumber with rerun format so we could run any failed test.
is it possible to have another format on top of rerun in the same statement such as pretty? i would like to know where the scenario failed....

Yes, just use multiple --format args. Only one can go to the console though.
e.g. cucumber --format rerun --output rerun.txt --format pretty


Git - remove git.experimental.inputValidation setting

As a result of these changes "git.inputValidation" setting may be changed (without even asking user!) in user and workspace settings, say from "always" to true. When workspace settings are under version control this causes a lot of pain. Also imagine a situation when different team members have different VS Code versions - someone needs setting value as a string, someone as a boolean.
Going forward, please avoid changing workspace settings in non-backwards-compatible manner.


Add maven support

To achieve debugging a maven project after 'mvn compile,' one needs to tweak the launch.json configuration with the following:
"startupClass": "${relativeFile}",
"options": [
  "-classpath",
  "${workspaceRoot}/target/classes"
]

@TSedlar  Code has been merged, please could you test the latest master branch and let me know if all is ok.
Thanks for your effort (updated readme.md to recognize your contribution)


TypeScript doesn't replace half overwrite properly anymore

open a TypeScript file
type cConsole
trigger IntelliSense, select console
🐛 text turns int cconsole instead of console, debugger shows that the suggestion isn't overwriting enough (overwriteBefore: 6)

Thanks for reporting this.
This regression  was introduced by my work to support completions with spaces or other special characters in them. I'll look into a fix for this while still allowing those string completions. My current thought is to compute the replacement range using the current logic plus the old word based range  logic and take whichever is the longer of the two. We could also check the replacement to see if it contains any spaces/special characters when computing the replacement range.

Thanks. The fix makes sense, nit - you could have used Range.union


Hotfix: version fix on python-engineio to debug uWSGI socket issue

fix: https://github.com/pinterest/querybook/issues/1319
related to: https://github.com/miguelgrinberg/python-engineio/issues/330
python-engineio (version between v4.5.1 and v4.7.0) has some bug on socket close logic.
Due to this issue, Querybook webserver got the error below all the time.
Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
  File "/usr/local/lib/python3.9/site-packages/engineio/socket.py", line 223, in writer
    ws.close()
  File "/usr/local/lib/python3.9/site-packages/engineio/async_drivers/gevent_uwsgi.py", line 70, in close
    uwsgi.disconnect()
SystemError: you can call uwsgi api function only from the main callable
2023-09-01T11:35:50Z <Thread at 0x7f63a8909040: writer> failed with SystemError

Traceback (most recent call last):
  File "src/gevent/greenlet.py", line 831, in gevent._gevent_cgreenlet.Greenlet.join
  File "src/gevent/greenlet.py", line 857, in gevent._gevent_cgreenlet.Greenlet.join
  File "src/gevent/greenlet.py", line 846, in gevent._gevent_cgreenlet.Greenlet.join
  File "src/gevent/_greenlet_primitives.py", line 61, in gevent._gevent_c_greenlet_primitives.SwitchOutGreenletWithLoop.switch
  File "src/gevent/_greenlet_primitives.py", line 61, in gevent._gevent_c_greenlet_primitives.SwitchOutGreenletWithLoop.switch
  File "src/gevent/_greenlet_primitives.py", line 65, in gevent._gevent_c_greenlet_primitives.SwitchOutGreenletWithLoop.switch
  File "src/gevent/_gevent_c_greenlet_primitives.pxd", line 35, in gevent._gevent_c_greenlet_primitives._greenlet_switch
  File "src/gevent/greenlet.py", line 906, in gevent._gevent_cgreenlet.Greenlet.run
  File "/usr/local/lib/python3.9/site-packages/engineio/socket.py", line 223, in writer
    ws.close()
  File "/usr/local/lib/python3.9/site-packages/engineio/async_drivers/gevent_uwsgi.py", line 70, in close
    uwsgi.disconnect()
SystemError: you can call uwsgi api function only from the main callable

This issue has been solved by python-engineio version 4.7.1 (released just 5 hours ago).
I deployed and tested Querybook with this version, and the issue was solved.

@okayhooni looks like querybook doesn't directly depend on python-engineio. And I checked the version of python-engineio when running make, it is python-engineio         4.9.0. Is it still an issue on your end if without this PR?


Marketplace workflow

@arduppal : Thanks for your contribution! The author, @kgremban, has been notified to review your proposed change.

Thanks @arduppal
#sign-off


raw is not allowed within modifyGraph in a withGraphJoined

Hello,
I am experiencing difficulty adding a raw column within a modifyGraph. This makes me think that raw is not allowed within withGraphJoined. Is there any other way I could achieve this?
The result contains my desired columns exlcept "translation" the result of raw((SELECT ${nameTranslatedColumn} )AS translation),
No error is thrown, but the column "translation" is just not included in the result.
This is how my relational map looks like
      category: {
        relation: Model.HasOneRelation,
        modelClass: join(__dirname, 'article-category'),
        join: {
          from: 'article_categories.id',
          to: 'articles.categoryId',
        },
      },

Thanks!
    const nameTranslatedColumn = userLanguage === Language.english
      ? 'null'
      : 'article_categories.name_'.concat(userLanguage)

    Article.findAll()
      .withGraphJoined('[translations, category]')
      .modifyGraph('translations', builder => void builder
        .andWhere('progress', 100))
      .modifyGraph('category', builder => void builder
        .select(
          'id',
          'name',
          raw(`(SELECT ${nameTranslatedColumn} )AS translation`),
        ))

Your code generates something like this SELECT "id", "name", (SELECT article_categories.name_fi) AS translation
You don't need to use a nested select or raw for that metter.
You can do this:
    const nameTranslatedColumn = userLanguage === Language.english
      ? null
      : 'article_categories.name_'.concat(userLanguage)

    Article.findAll()
      .withGraphJoined('[translations, category]')
      .modifyGraph('translations', builder => void builder
        .andWhere('progress', 100))
      .modifyGraph('category', builder => {
        builder.select('id', 'name')
        if (nameTranslatedColumn) {
          builder.select(`${nameTranslatedColumn} as translation`)
        }
      })

@koskimas Thank you so much for your answer. Would this way also work when userLanguage === Language.english? So the generated string would be "null as translation"? Or objection will confuse null with a column name rather that the value to be returned?

At least on postgres you can select null. So this should work
    const nameTranslatedColumn = userLanguage === Language.english
      ? null
      : 'article_categories.name_'.concat(userLanguage)

    Article.findAll()
      .withGraphJoined('[translations, category]')
      .modifyGraph('translations', builder => void builder
        .andWhere('progress', 100))
      .modifyGraph('category', builder => {
        builder.select('id', 'name')
        builder.select(`${nameTranslatedColumn} as translation`)
        }
      })

Thank you Sami @koskimas, very appreciated.

I just had the opportunity to run it and I had "column \"null\" does not exist\n" my database is postgres:12-alpine. That part of the query looks like
 left join (select \"id\", \"name\", \"icon\", \"created_at\", \"updated_at\", \"null\" as \"translation\" from \"article_categories\") as \"category\"
for some reason, it is adding double-quotes for the null.
Any idea how could I work around this?

It is working in this way, with a minimum modification:
`
const nameTranslatedColumn = userLanguage === Language.english
? 'null'
: 'article_categories.name_'.concat(userLanguage)
Article.findAll()
  .withGraphJoined('[translations, category]')
  .modifyGraph('translations', builder => void builder
    .andWhere('progress', 100))
  .modifyGraph('category', builder => {
    builder.select('id', 'name')
    void builder.select(raw(`${nameTranslatedColumn}`).as('translation'))
    }
  })

`
Thank you so much


Sonoma installer USB resulting in a reboot loop?

Hey!
As always, excellent work on the EFI here and glad to hear we can get Sonoma going on our L13Y's.
However i seem to be having a weird issue. So, i've created a Sonoma USB as per Apple's own instructions for making a USB installer. Then i've grabbed the latest EFI from here to get it bootable on the system.
The only changes i've made to the EFI are the SMBIOS (serial/etc), to match what i had with my Monterey install, and enabled the AirportitlwmS.kext and disabled the rest (of the Airport ones that is).
The USB does appear to boot, however just as the display brightness turns itself up the screen goes blank and the whole system restarts. When trying to boot again there is indication a kernel panic occurred as i get the "A problem occurred and your computer was restarted" message when i try to boot the USB again.
So i edited the EFI boot args to enable verbose boot, but i see no indication of a kernel panic at all, the system just appears to be booting the USB and then just as the installer graphical interface would startup the screen goes off and the whole system restarts. I have provided a screenshot just on the off chance something is there that could indicate whats going on? This is the last frame of verbose boot before screen goes blank and system restarts.

EDIT: Booting into Monterey off of this same new EFI (with the older version of the Airport kext loaded for it) has let me see the kernel panic log, i have attached it as well. Some sort of memory stack corruption going on?

Looks like it has something to do with Airport?

I'm seeing the exact same thing, though I didn't have the problem installing Ventura .  My wifi card is an AX201, so different to the type seven-of-eleven has.  What type do you have?

I was able to succesfully install Sonoma by swapping the airportitlwmS.kext in this EFI with the release targeting Mac OS 14.4.0 and later from the OpenIntelWireless repositry:
https://github.com/OpenIntelWireless/itlwm/releases/download/v2.3.0/AirportItlwm_v2.3.0_stable_Sonoma14.4.kext.zip
Once I got past the kernel panic issue I encountered the installer reboot issue that appeared with the release of 14.4, but it's easily fixed as documented here as well as other places.
After a few hours of using this laptop, it appears to be 100% rock solid and probably the best hackintosh I've ever had.  No issues with touchscreen or stylus pen, though I've only done a little testing in a drawing context with the stylus.
Thanks again for this awesome repo.

Well, all credit goes to @seven-of-eleven !
Happy to see you enjoy the L13 for all it has to offer! closing this issue..
Cheers,
Mifaxav

closing...


doesn't appear to work with music videos

I don't know if it's a matter of Jellyfin handling Music and Music Videos differently, but even after allowing my Music Video library for listen submission, it doesn't seem to do anything, neither a Now Playing status or a completed listen

When processing a played item, the plugin explicitly checks if the item is an audio item. Tbh it did not even occur to me to support music videos as that's something I have never used.
Allowing music videos should be fairly easy, although I think the listen submissions will be plain (only text, no metadata).

I did add a feature request in the Jellyfin feature requests hub, for what it's worth, so hopefully someday the second part will work~
https://features.jellyfin.org/posts/2484/add-musicbrainz-as-a-music-video-metadata-provider

@UltimateRiff Unless I'm mistaken, adding support for music videos to the MusicBrainz plugin means implementing a metadata provider for a Recording MBID. Which would also coincidentally address this issue.


Events strategy

Potentially interesting events:

All PyData conferences (and also local meetups when appropriate)
Some PyCon and EuroPython events (whenever there's a sufficiently large audience of data scientists, or the event is big)
Open Data Science Conference
Other: AI Summit, JupyterCon, WebSummit, Grace Hopper Celebration, QCon, OSCON?, FOSDEM?, OSCAFEST?

Bottom line: meet our users where they are.

All the events I mentioned above are (at least primarily) in-person events. But we could select some fully online or hybrid events as well. For example:

Big Data Technology Warsaw Summit

On the other hand, we'd need an event & CFP calendar so that we can plan accordingly.

Upcoming:

March 9 - Big Data Technology Warsaw Summit
March 13 - PyData London CFP deadline
March 18 - PyCon Lithuania CFP deadline
April 17 - PyCon.DE & PyData Berlin
May - JupyterCon in Paris and PyCon & PyData Lithuania
June - PyData London

I put in one for ODSC Europe 🥳

ODSC EU: https://odsc.com/europe/call-for-speakers-europe/

Round Two for Speaker Proposals Opens – February 27, 2023
Deadline for Round Two Speaker Proposals – April 3, 2023
Second Round Accepted Speakers Notification – May 1, 2023
Event takes place - June 14-15th, 2023

June - Data + AI summit https://www.databricks.com/dataaisummit/
September - Deep Learning Indaba 2023 https://deeplearningindaba.com/2023/
November - Web Summit Lisbon https://websummit.com/

EuroPython 2023 Call for Proposals (CFP) will be open between Monday, 6 March 2023 and Sunday, 19 March 2023

https://blog.europython.eu/europython-march-2023-newsletter/

Seen on LinkedIn: "As part of the development and growth of the Deep Learning Indaba, the organizing committee is welcoming workshop proposals for the first time." (source)

Deadline proposal submission: April 6, 2023

https://deeplearningindaba.com/2023/indaba/call-for-workshop-proposals/

OpenSouthCode 2023

The submission period is open till March 31 2023.

https://www.opensouthcode.org/conferences/opensouthcode2023

Let's keep this in the upcoming sprint and use the time to create an internal tracker for conferences/events and our planning around them.

Done, in review

Closing this as completed ✔


Add Alpine 3.12

Usabilla PHP Docker Template
Reviewers: @usabilla/oss-docker
Type
Please specify the type of changes being proposed:

Q
A

Documentation?
no

Dockerfile change?
no

Build feature?
no

Apply CVE Patch?
no

Remove CVE Patch?
no

Changelog

Please make sure you have checked our Contributing guidelines

Thanks a lot for that!

Took 5 seconds :joy: , plus 20 minutes building all images locally, plus 30 minutes doing this for my own images last week when they showed up on Dockerhub :sunglasses: . Also have some ideas combined with #151 that could automate this.

We can leave php 7.3 out of it, fewer versions is better and people can update to the newest shiny stuff!

Done :+1:


Automatically create and pushing policy bundles

The GitHub action seems to be working, see https://github.com/simonbaird/ec-policies/actions/runs/3316419981/jobs/5478191610 .

I added my Azure push password at the org level, see https://github.com/organizations/hacbs-contract/settings/secrets/actions .


Mistral-7B model fails from main on Wormhole N300

Describe the bug
Mistral demo test fails from the main branch. I added the correct path for the weights (which were fully downloaded, and I double checked the path) and it did not work. I manually added the exact same path to the weights in the testing code, and then it worked.
To Reproduce
Steps to reproduce the behavior:

Checkout to main
Run the command:
'pytest models/demos/wormhole/mistral7b/tests/test_mistral_model.py::test_mistral_model_inference[17-generative]`
See the error: 'FAILED models/demos/wormhole/mistral7b/tests/test_mistral_model.py::test_mistral_model_inference[17-generative] - AssertionError: weights consolidated.00.pth file does not exist. Please use the script `models/demos/wormhole/mistral7b/scripts/...'

Expected behavior
The PyTest passes.
Please complete the following environment information:

OS: [e.g. Ubuntu 20.04]
Version of software (f587cb5)
N300

did you forget to download something? Please show the full log
Please use the script `models/demos/wormhole/mistral7b/scripts/...'

Got it working on my end today after a new clone and build. Closing the issue accordingly.


Run runv with docker create busybox container failed

ENV:
ubuntu16.04.2 64bit
go version go1.10.1 linux/amd64
runv version 1.0.0
Docker version 18.03.0-ce
STEP:

according to the https://github.com/hyperhq/runv/tree/master instructions.
Some steps.
runv --kernel /var/lib/hyper/kernel --initrd /var/lib/hyper/hyper-initrd.img run mycontainer and it was successful, info as follow:
root@node-dev9:~# runv list
ID            PID         STATUS      BUNDLE             CREATED                     OWNER
mycontainer   79976       running     /containerbundle   2018-04-24T09:54:03+08:00   root
docker run --rm -it busybox and it was failed, info as follow:
root@node-dev9:~# docker run --rm -it busybox
set winsize failed, rpc error: code = Unavailable desc = all SubConns are in TransientFailure

Does it not support ubuntu16.04? Or something else？

@ZhangSenter Thanks for reporting! I can confirm the error in my local setup. Looks like something has changed in docker's network configuration.
I0424 13:49:07.180841   22405 network.go:433] get interface {47 48 <IP_ADDRESS>/16 02:42:ac:11:00:02 eth0 1500}
I0424 13:49:07.355826   22405 network.go:444] got mirredPairs: [{47 49}]
E0424 13:49:07.363465   22405 network.go:464] no such file or directory

Need to take a closer look at it.


Bump to 1.0?

Looks like the library's API is pretty stable (once #12 and #14 are closed).

:+1:

go ahead!

This is a widely-used library that has not changed in a while, and I don't intend to change it much going forward if I can help it.  I'll bump to 1.0 with my next publish.


Upgrade deploy scripts to nodejs 9.x

We need to upgrade all scripts from 7.x to 9.x and test on virtual machines. @belochub you can give this tasks to ours new guys.

https://github.com/metarhia/impress/tree/master/deploy

Closed in https://github.com/metarhia/impress/commit/7b6b8416da2c75c2e77a43b4eaa0149efeeb02b0.


CosmosDbStorage: read documents using the document client #2487

Remove SelfLink request. Please refer to this doc Remark section for SelfLink. https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.documents.client.documentclient.readdocumentasync?view=azure-dotnet .
When customer is using SelfLink request, when they are throttled, the database/collection names are not available to Cosmos DB. The recommendation is to use the ID-based link. It's also explained in the doc.

I believe this is already done.

This is fixed in here


Make Spark Thread pool configurable (#73)

Please merge the current bleeding branch or rebase the PR for the Snyk check to pass.
I believe they're detecting the already updated dependencies as vulnerabilities even though they would not be changed back.


Check whether there is an interface according to the cone of the camera

Check whether there is an interface according to the cone of the camera？

Sorry I do not know what you mean with this. Closing the issue.


Build v 2.7.5:

Update build scripts.
Update scripts that outputs the path to mathjax.
update recipe with m2-bash for win.

Linter check found the following problems:
The following problems have been found:
WARNING: /tmp/abs_e588ipckfc/clone/recipe/meta.yaml:34: missing_description: The recipe is missing a description
Warnings were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ef7dyrt3g4/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_99qk3tb7ly/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_195kk37xzh/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_11z86pcl3z/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_70qyqcvut_/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_2c7t42y0sp/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_ebo8vhnhl5/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_bb8sq9_dsk/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_458hx6s26x/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_09dtyl1276/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_0arnsr82p4/clone/recipe/meta.yaml:0: missing_section: The requirements section is missing.
Errors were found


Use Managed Identity rather than Service Principal

Can an MI not be used rather than an SP? It says here that MIs can be used with Key Vaults: https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/services-support-managed-identities#azure-key-vault

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

ID: 4997f245-c966-51a3-34c7-705c3cfbd4b0
Version Independent ID: 129fbe40-3b02-f2c1-ef13-b42d86ffdb77
Content: Setup TDE Extensible Key Management with Azure Key Vault - SQL Server
Content Source: docs/relational-databases/security/encryption/setup-steps-for-extensible-key-management-using-the-azure-key-vault.md
Product: sql
Technology: security
GitHub Login: @jaszymas
Microsoft Alias: jaszymas

@ChrisSommers -- thank you for your question.  Please look here for further information:

DBA Stack Exchange
Stack Overflow

cc @jaszymas for awareness


Ask dataclass to generate hash only if not implemented yet.

This allows one to define their own __hash__ methods if desired.

If you want this to stay working with possible future refactors, please add a unit test.

Good point, done.


Error: Disk object has no attribute 'Disk__hwmon_path'

Traceback (most recent call last):
  File "/home/grimhex/Desktop/projects/sysstats_api/test.py", line 3, in <module>
    print(d.get_temperature())
          ^^^^^^^^^^^^^^^^^^^
  File "/home/grimhex/Desktop/projects/sysstats_api/lib/python3.11/site-packages/diskinfo/disk.py", line 554, in get_temperature
    if not self.__hwmon_path:
           ^^^^^^^^^^^^^^^^^
AttributeError: 'Disk' object has no attribute '_Disk__hwmon_path'. Did you mean: '_Disk__byid_path'?

Code Executed for this error:
from diskinfo import Disk
d = Disk("sdc")
print(d.get_temperature())

I tried using it in my project and not getting it to work, so I tried the docs version in a separate script and that didn't work. (/dev/sdc exists)

Hi @ThreeTheOG, I've got two ideas to explain this:

In case of SATA drives you have to load drivetemp kernel module for temperature reading. This module will create the proper HWMON files in /sys filesystem.
You may have SAS/SCSI drive and this is not supported by drivetemp module. In this case I'm planning to support hddtemp for temperature reading in a future release.

Not loading the drivetemp driver was the issue, should have read the docs more carefully. Thanks for the quick response and the great work on this project.

I'm glad if it helps.


Task/account integration tests

Closes #68

This change is

Codecov Report

Merging #100 into master will increase coverage by 6.45%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #100      +/-   ##
============================================
+ Coverage     73.86%   80.31%   +6.45%
- Complexity     1071     1170      +99
============================================
  Files           108      108
  Lines          3531     3531
  Branches        152      152
============================================
+ Hits           2608     2836     +228
+ Misses          848      607     -241
- Partials         75       88      +13

Impacted Files
Coverage Δ
Complexity Δ

...va/org/oscm/rest/common/SampleTestDataUtility.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...java/org/oscm/rest/service/PriceModelResource.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...in/java/org/oscm/rest/service/ServiceResource.java
100% <ø> (ø)
7 <0> (ø)
:arrow_down:

...g/oscm/rest/service/CompatibleServiceResource.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

...rg/oscm/rest/service/TechnicalServiceResource.java
100% <ø> (ø)
7 <0> (ø)
:arrow_down:

...java/org/oscm/rest/service/TSSupplierResource.java
100% <ø> (ø)
4 <0> (ø)
:arrow_down:

.../org/oscm/rest/account/BillingContactResource.java
100% <ø> (ø)
6 <0> (ø)
:arrow_down:

...ava/org/oscm/rest/account/PaymentInfoResource.java
100% <ø> (ø)
5 <0> (ø)
:arrow_down:

...va/org/oscm/rest/account/OrganizationResource.java
100% <ø> (ø)
3 <0> (ø)
:arrow_down:

.../oscm/rest/account/data/AccountRepresentation.java
87.5% <0%> (+2.08%)
26% <0%> (+3%)
:arrow_up:

... and 15 more


Issue: Normalize step will write HDFS output (Big Space)

To some big data, this step spends too many spaces, try to think about how to make it compute on the fly.
To make it on the fly in train and varselect step is easy, while the old 'norm' step should be keeped to make sure compatible with old versions.

Gzip is used to compress normalized outputs
Users will be benefit if leverage variable selection more. for saving normalizing output
Parquet format is also support for NN algorithm to save normalizing space.

Close this issue and if further request reopen it


Persistence

Hey,
I'm trying to add this as a cache to one of our toolchain components, but I have problems with data not being persisted. I have 500 keys that contain json data and I am writing a u64 and a [u8] for each of them. Additionally, after each commit I am calling env#sync(true), but after restarting the tool, only half of the keys are there.
Specifically, this is a snippet from the impl that is used to persist data with lmdb-zero:
pub struct Memory<'a> {
    lmdb_env: &'a lmdb::Environment,
    lmdb_db: &'a lmdb::Database<'a>
}

impl<'a> Memory<'a> {
    #[inline]
    pub fn new (lmdb_env: &'a lmdb::Environment, lmdb_db: &'a lmdb::Database) -> Memory<'a> {
        Memory {
            lmdb_env: lmdb_env,
            lmdb_db: lmdb_db
        }
    }

    pub fn sync (&self) {
        self.lmdb_env.sync(true);
    }

    #[inline]
    pub fn put (&mut self, key: &str, data: &Vec<u8>) {
        let tx = lmdb::WriteTransaction::new(&self.lmdb_env).unwrap();

        {
            let mut access = tx.access();

            access.put(&self.lmdb_db, key, data.as_lmdb_bytes(), lmdb::put::Flags::empty()).unwrap();
        }

        tx.commit().unwrap();

        self.sync();
    }

    #[inline]
    pub fn put_u64 (&mut self, key: &str, data: &u64) {
        let tx = lmdb::WriteTransaction::new(&self.lmdb_env).unwrap();

        {
            let mut access = tx.access();

            access.put(&self.lmdb_db, key, data, lmdb::put::Flags::empty()).unwrap();
        }

        tx.commit().unwrap();

        self.sync();
    }

    /* other methods here */
}

There's one method used that effectively does a 7200 second cache per URL:
    fn client_cond_get (url: &str,
                        memory: &mut memory::Memory,
                        client: &client::HTTP
                    ) -> Vec<u8> {
        /* unixtime */
        let now = time::now().to_timespec().sec as u64;

        let mut url_ts_id = url.to_string();
                url_ts_id.push_str(&"_ts");

        let known_url_ts = memory.get_u64(&url_ts_id);

        if known_url_ts.is_some() {
            if (now - known_url_ts.unwrap()) < 7200 {
                return memory.get(&url).unwrap();
            }
        }

        let res = client.get(url);

        let _ = memory.put_u64(&url_ts_id, &now);

        memory.put(&url, &res);

        res
    }

So per http "get" operation there are at worst 2 reads and 2 puts, at best 2 reads (when data is obtained from the cache).
Could you maybe help me brainstorm possible issues I should be aware of when doing a commit? I am aware of the fact that a commit is writing to disk, but I don't know how to deal best with the OS disk buffering.
Thanks a lot.
Take this as a gift: 🍻

Hm, it seems entires doesn't change. (I did a env.stat() after each write)
Could it be that lmdb silently fails to write the keys?

Oh. It seems when writing a u64, it sometimes cannot be obtained correctly as a u64 back:

It seems when writing a u64

You may have been bitten by alignment requirements. I'll need to look into how to make this problem more obvious, especially since if you're not using LmdbRaw yourself you wouldn't even have seen the warning. You probably want to read and write Unaligned<u64> instead of a bare u64 (docs). In these cases, I usually do something like
use lmdb::Unaligned as U;

// ...

let value: U<u64> = access.get(&db, "somekey").unwrap();

I don't know how to deal best with the OS disk buffering.

You don't need to; the OS will maintain a coherent view of the file for all processes. The only thing sync accomplishes is that it tells the OS to actually write the data to disk so it is still there if a power failure occurs.

Nice, that worked like a charm. Thanks a lot.

Version 0.3.0 has some changes that will help with this kind of problem:

Value rejection errors now have error messages indicating the exact problem and pointing to relevant documentation.

This particular instance — trying to get a bare &u64 — is now a hard compile-time error as the bare primitive types other than i8 and u8 are no longer LmdbRaw, but must be wrapped with Unaligned.

Great, thanks a lot!


[ZEPPELIN-2049 : z0.7.1] Note name is gone when switch to personal mode

What is this PR for?
Note name is gone when switch to personal mode
There was a part of the note name that was missing processing.
So, I fixed it.
What type of PR is it?
Bug Fix - 0.7.1 related
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2049
How should this be tested?
You can personalized mode.
and then plase refresh note view.
and check to note name.
Screenshots (if appropriate)
before(problem)

after (resolved)

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

@jongyoul @Leemoonsoo
Could you review on this pr?

Thanks @cloverhearts for the fix.
LGTM!

Merge to master and branch-0.7 if no further comments


Customisation friendly

remove LINDAT references from UFALHome (put them to messages.xml)
remove LINDAT references from UFAL
could we move static pages to static directory in dspace-xmlui/...webapp/static?

the PR moves our themes so it is possible to overlay some parts.
moving the strings to messages will be done in #7

@vidiecan can we close this?


Support of escape characters

We have to support escape characters like \n, \t or \r.
Right now they don't get parsed. I don't know if it is possible to let swift handle this for all strings by default...

Sure if swift can handle these that would be nice. This feature too is nice to have but not strictly necessary and we should focus first on making the language correct first with our core features.

But if we implement this it would also be lovley if we could have string interpolation like swift 😍

Yes, but it is quite difficult to built a solid cli program without\n haha (for the showcase demo example)

true yeah we should handle that, also it would be nice to have a print without the newline.

yes, probably just differ between println and print is the easiest way

implemented


[BUG]: The landing chips are not link to specific roadmaps/

Description of the bug

Steps To Reproduce

Go to /, click on the chips/badges they are empty links, needs to point to roadmaps.

Additional Information

Resolved.


Add endpoint config

To prepare to point the DockerStats to a SWARM endpoint, the endpoint has to be configurable.
bash-4.3# cat /etc/fullerite/conf.d/DockerStats.conf
{
  "dockerEndPoint": "unix:///var/run/docker.sock"
}

This will work the same way as the previous hard coded const endpoint.
I haven't pointed it to something else, but I will.. :)

damn... my other PRs are mixing in.


operator DrawerView

What changes are proposed in this pull request?
Add support for rendering operator prompt in a side drawe
How is this patch tested? If it is not, please explain why.
Using a test operator with resolve_input code below:
def resolve_input(self, ctx):
    inputs = types.Object()
    inputs.str("name", label="Name", required=True)
    return types.Property(inputs, view=types.DrawerView(variant="right"))

Preview
https://github.com/voxel51/fiftyone/assets/25350704/66761e32-f7d3-4709-8a87-9f18a70cdc2d
Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.

Add DrawerView prompt style
What areas of FiftyOne does this PR affect?

[x] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[ ] Core: Core fiftyone Python library changes
[ ] Documentation: FiftyOne documentation changes
[ ] Other

Summary by CodeRabbit

New Features

Introduced a Resizable component for horizontal resizing of elements.
Added OperatorDrawer components to the SamplesContainer for enhanced operator interaction.
Implemented DrawerView for rendering operator prompts as left/right drawers, improving user interface flexibility.

Style

Updated styling for the Resizable component, including hover, active, and focus states.

Refactor

Updated import and usage of Resizable in Sidebar to accommodate modal states and improve resizing logic.

Chores

Reorganized imports and added new exports for Resizable and OperatorDrawer components.
Added DrawerView to baseViews array and introduced CUSTOM_PROMPTS constant for extended functionality.

Should the expanded sample view (modal) also support the drawer view? Some CSS/HTML needs to be adjusted I think

Should the expanded sample view (modal) also support the drawer view? Some CSS/HTML needs to be adjusted I think
Yah, good idea. Will extend the support to sample viewer


Koushi theme v2

This is the version 2 of my Koushi theme which has a PR for the old Spotify UI here https://github.com/morpheusthewhite/spicetify-themes/pull/345.
Important UI Changes

Outlines all major UI Elements (General screen, Device Menu, Context Menus, etc.) in Spotify with an alternative color. i.e Dark theme white outlines, Light theme black outlines.
Toggles UI Colors based on macOS's System appearance automatically.

Dark theme (default)

Light theme

What are the differences from the default theme?

Hey @morpheusthewhite thanks for your response. I guess adding outlines to everything isn't much of a cosmetic change but I thought having the color scheme that changes based on system appearance (it's hard coded in) would be a breaking change to the Default theme since normally you just choose a single color scheme and it won't change without you changing the config.ini file directly?
I'll leave the PR here but continue doing my own thing on my own repo. If you feel the PR isn't enough to have a separate theme from the Default feel free to close and no hard feelings :)

Same thing for my other PR. If you feel it's not enough feel free to close it.

I don't use MacOS so I don't really know how much that could be useful, I'll wait for some feedback before deciding

Not too many people seem interested in this theme. I will close.
Thanks for the PR, anyway.


Upgrade Confluent package to version 1.9.0

/azp run

/azp run

The PR doesn't update to 1.9.0, but to 1.8.2. Also, I think the references are only needed in the "Core" project.

Linking the PR -- https://github.com/Azure/azure-functions-kafka-extension/pull/361


Edit: Rouge TV

Channel ID (required)
RougeTV.ch
Channel Name
Carac1
Alternative Names
No response
Network
Carac Media
Owners
Media One Group
Country
CH
Subdivision
No response
City
Genêve
Broadcast Area
No response
Languages
fra
Categories
entertainment;xxx
NSFW
TRUE
Launched
No response
Closed
No response
Replaced By
Carac1.ch
Website
https://carac.tv/
Logo
https://i.imgur.com/mw3PbSU.png
Notes
Rouge TV got renamed Carac1, and have now 4 different channels. The 1st channel contains erotic programs, whilst the 3 others are thematical and are family-friendly.

We can't pass the check since ios already in database. I think we should mark this channel as closed with original name or remove it as a duplicate, maybe add old name to Carac1

Yep, better do this.


Fix the version of the dependencies

For modules, as a user, I expect to obtain a module that will not change in time (as long as the version is not different).
I know that, in theory, the ^ should ensure backwards compatibility but I have experienced bad stuff with some module to then discover the issue was a dependency of dependency. Those issues would not have happened if the dependencies version were static (without ^ or ~).
What do you think?

You can't control your dependency's dependencies. I think npm shrinkwrap is better suited for your use case.

If everyone is resigned like that, it will never be solved, you are right.
Shrinkwrap is annoying as it fixes also the source registry which may be problematic in corporate environments.
The owner of this module will anyway decide what he wants to do with his module.
I wish that more core module owner made the transition to fixing dependencies

Unfortunately if the versions were pinned more explicitly in this package, it would need to be republished every time there is a change or important fixes may not be available which is something I don't want to opt in to. And in any case, we have no control over the dependencies of our dependencies, so it would be an incomplete solution.
I recommend shrinkwrap or something with a lock file (yarn, npm 5) in production to solve this.

okay, your module, your choice.


Simplify folder structure and tidy up READMEs

Issue #, if available:
Closes #80
(but includes other proposed changes too)
Description of changes:

Pull notebooks/basic/Tutorial up to notebooks/getting_started, on the basis that there probably shouldn't need to be more than one introductory/tutorial set of notebooks? Immersion-day and blog-specific samples already have dedicated folders.
Update README.md and notebooks/README.md

To fix the links per #80, but also...
Clarifying what we mean by "notebooks" and why we use them, for new Forecast users who might not be familiar with the concept (it's possible to use Forecast without SageMaker, after all!)
Slimming down some of the repetition in the introduction to the getting started / tutorial notebooks

Make the S3 bucket name optional in the CF stack, because this is painful for multi-customer events: May as well let CF auto-generate unique bucket names!
Add a lifecycle config to enable widgets in JupyterLab, because JupyterLab is for winners 😎

Feedback very welcome - just proposing some updates!
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closing this PR from feedback that breaking existing hyperlinks with the restructure would be a pain


Upgrade libgit2

The current version of libgit2 is 0.18, and we are using 0.14.

Make sure to run the pyxet tests as part of verifying this version bump

Closed for other PR doing this.


Fixed emulator

Emulator was broken.
Tried to write to a const.
And was not returning a promise as was expected.

Great! Thanks! :)
Forgot to test the emulator last time apparently


Remove Redis and switch to an alternative

Recently, Redis has decided to change their license so the project is no longer fully open source. We should switch from Redis to a different alternative, as this is something I do not support. A possible alternative is KeyDB which claims to be a drop in replacement.

Switched to KeyDB on spark and Galaxy APIs. No need to change anything on the plugin side since the client is compatible with KeyDB.


66bit

what is the 66bit jigsaw prefix?

For Puzzle # 64 (with address 13zb1hQbWVsc2S7ZTZnP2G4undNNpdh5so), its private key prefixes are from
0000000000000000000000000000000000000000000000020000000
to
000000000000000000000000000000000000000000000003FFFFFFF
and its address prefix is 20D45A6A.


The Jenkins ver 2.138.3 version style does not take effect. I can't add a CSS file.

The  Jenkins ver 2.138.3  version style does not take effect. I can't add a CSS file.
Use the second method: HTTPS://cdn.rawgit.com/afonsof/jenkins-material-theme/gh-pages/dist/material-green.css
Clicking Save will not work.

You may try to use below CSS URL:
http://afonsof.com/jenkins-material-theme/dist/material-green.css


Add timestamp to component's initial build subpath

Signed-off-by: Mykola Morhun<EMAIL_ADDRESS>What this MR does
Adds timestamp to subpath field of tekton workspaces configuration in the pipeline run object of initial build.
Which issue this MR fixes
https://issues.redhat.com/browse/PLNSRVCE-53
How to test

Create an app and a components as usual.
Check, that created PipelineRun object has subpath with timestamp

Spoke with @mmorhun, he asked to hold on merging this til https://github.com/redhat-appstudio/application-service/pulls/48 is in

@mmorhun Can you rebase this PR?

/retest

Once more please :)

Rebased again


Access Denied on Deployment

Resource handler returned message: "Access Denied (Service: S3, Status Code: 403, Request ID:....)" when upgraded CDK version from 2.68.0 to 2.100.0.
Resource Type - AWS::S3::BucketPolicy
Logical ID - avscanstackVirusDefsBucketPolicy6539E060
const sc = new ServerlessClamscan(this, 'av-scan-stack', {});
this.inputBucket = new Bucket(this, 'av-scan-bucket', {
    autoDeleteObjects: true,
    removalPolicy: cdk.RemovalPolicy.DESTROY
});
sc.addSourceBucket(this.inputBucket);

Is this the issue that you're seeing?

Is this the issue that you're seeing?

Yes, same CloudFormation Error. and as you can see above I am not passing any existing S3 buckets to construct, those were created in an earlier version of the CDK and now when I upgraded my CDK version and trying to redeploy same stack it is throwing this issue.

Seeing the exact same problem with CDK 2.110.0:

That bucket policy has a statement on it that makes it immutable, except by the root user of the account.
That's a really odd permission to add to the bucket and needs further research why that is happening

Would it be possible to not make it immutable? Is there a reason behind making it immutable?

It's immutable to ensure that that ClamAV definition files are not tempered with
Only the account root user has the ability to modify the bucket policy and could remove the policy that makes it immutable.
The other options are to remove the construct from the solution and add it again or to diagnose why that permission is being added in the first place and remove it

From having a quick look around, it seems that this needs to be configured on the bucket:
blockPublicAccess: BlockPublicAccess.BLOCK_ACLS,
accessControl: BucketAccessControl.BUCKET_OWNER_FULL_CONTROL

Thanks @dontirun ,
Managed to resolve the problem by removing the construct from the stack and then adding it back, which seems to have effectively fixed the issue.


Unfortunately, <app_name> has stopped (android)

Try exactly this:
RNImageRotate.rotateImage(
  https://i.imgur.com/9qtVISH.jpg,
  90,
  (rotatedUri) => {
    console.log(rotatedUri);
  },
  (err) => {
    console.log(err);
  }
);

It crashes the entire app at me ( mobile device: Samsung S5, "react": "16.5.0", "react-native": "^0.57.1", "react-native-image-rotate": "^2.1.0" )

Obviously it crashes because we are out of memory. But it shouldn't crash, it should call the error callback function with corresponding message.
As a workaround, I modified the private Bitmap rotate(BitmapFactory.Options outOptions) function like this:
    private Bitmap rotate(BitmapFactory.Options outOptions) throws IOException {
        InputStream inputStream = openBitmapInputStream();
        try {
            // This can use a lot of memory
            Bitmap bitmap = BitmapFactory.decodeStream(inputStream, null, outOptions);
            if (bitmap == null) {
                throw new IOException("Cannot decode bitmap: " + mUri);
            }
            Matrix rotateMatrix = new Matrix();
            rotateMatrix.postRotate(mAngle);

            return Bitmap.createBitmap(bitmap, 0, 0, bitmap.getWidth(), bitmap.getHeight(), rotateMatrix, true);
        } catch (OutOfMemoryError outOfMemoryError) {
            // we are out of memory
            throw new RuntimeException("We are out of memory");
        } finally {
            if (inputStream != null) {
                inputStream.close();
            }
        }
    }

Now, in case we are out of memory, the app do not crash anymore. Instead we get the "We are out of memory" error message in the (err) => { console.log(err); } callback function.
It could be merged into the library...

Closed by #15


Update iot assisted tests

Description

Add socket communication between dut and rpi to solve syncronization issue.
Checklist:

[x] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks

Need code review. @vjjunnut @cobusve @brianfr @dongh @satyaprk-amazon @qiutongs @lundinc2

Can you try to close and reopen a PR? Let's see if it can bypass the build check.


Driving Timeout

When running a weeding automation the robot sometimes stops and the navigation raises a 'Driving Timeout' error.
I got a log for this but sadly it misses the current position and yaw, but U5 had this problem yesterday and we can try to reproduce it this afternoon.
rosys_1       | 2024-07-17 16:10:25.731 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.812, -4.259) with yaw -1.78.
rosys_1       | 2024-07-17 16:10:25.936 [INFO] field_friend/automations/implements/tornado.py:68: Target crop is not reachable
rosys_1       | 2024-07-17 16:10:25.937 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.818, -4.282) with yaw -1.78.
rosys_1       | 2024-07-17 16:10:26.092 [INFO] field_friend/automations/implements/tornado.py:68: Target crop is not reachable
rosys_1       | 2024-07-17 16:10:26.093 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.823, -4.303) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:26.248 [INFO] field_friend/automations/implements/tornado.py:68: Target crop is not reachable
rosys_1       | 2024-07-17 16:10:26.251 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.828, -4.323) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:26.425 [INFO] field_friend/automations/implements/tornado.py:68: Target crop is not reachable
rosys_1       | 2024-07-17 16:10:26.426 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.833, -4.343) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:26.574 [INFO] field_friend/automations/implements/tornado.py:68: Target crop is not reachable
rosys_1       | 2024-07-17 16:10:26.575 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.838, -4.363) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:26.773 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.843, -4.385) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:26.920 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.848, -4.405) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:27.107 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.853, -4.425) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:27.267 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.858, -4.447) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:27.421 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.864, -4.468) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:27.566 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.869, -4.487) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:27.743 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.874, -4.508) with yaw -1.79.
rosys_1       | 2024-07-17 16:10:27.921 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.879, -4.529) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:28.055 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.883, -4.549) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:28.240 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.889, -4.569) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:28.387 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.893, -4.589) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:28.547 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.898, -4.610) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:28.759 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.904, -4.631) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:28.883 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.909, -4.653) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:29.092 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.914, -4.674) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:29.249 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.919, -4.694) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:29.421 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.924, -4.715) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:29.618 [INFO] field_friend/automations/navigation/straight_line_navigation.py:44: Driving 0.02 m to Point(-0.929, -4.735) with yaw -1.80.
rosys_1       | 2024-07-17 16:10:31.620 [INFO] field_friend/automations/plant_locator.py:130: pausing plant detection
rosys_1       | 2024-07-17 16:10:31.620 [ERROR] rosys/automation/automation.py:68: automation failed
rosys_1       | Traceback (most recent call last):
rosys_1       |   File "/app/rosys/automation/automation.py", line 56, in __await__
rosys_1       |     signal = send(message)
rosys_1       |              ^^^^^^^^^^^^^
rosys_1       |   File "/app/field_friend/automations/navigation/navigation.py", line 52, in start
rosys_1       |     await self._drive(self.DEFAULT_DRIVE_DISTANCE)
rosys_1       |   File "/app/field_friend/automations/navigation/straight_line_navigation.py", line 45, in _drive
rosys_1       |     await self._drive_to_yaw(distance, start_position.direction(local_target))
rosys_1       |   File "/app/field_friend/automations/navigation/navigation.py", line 92, in _drive_to_yaw
rosys_1       |     raise TimeoutError('Driving Timeout')
rosys_1       | TimeoutError: Driving Timeout
rosys_1       | 2024-07-17 16:10:31.624 [INFO] rosys/rosys.py:69: automation stopped because an exception occurred in an automation
rosys_1       | 2024-07-17 16:10:31.624 [INFO] rosys/rosys.py:69: automation failed
rosys_1       | 2024-07-17 16:10:31.652 [ERROR] nicegui/app/app.py:118: Driving Timeout
rosys_1       | Traceback (most recent call last):
rosys_1       |   File "/home/zauberzeug/.local/lib/python3.11/site-packages/nicegui/background_tasks.py", line 52, in _handle_task_result
rosys_1       |     task.result()
rosys_1       |   File "/app/rosys/automation/automation.py", line 56, in __await__
rosys_1       |     signal = send(message)
rosys_1       |              ^^^^^^^^^^^^^
rosys_1       |   File "/app/field_friend/automations/navigation/navigation.py", line 52, in start
rosys_1       |     await self._drive(self.DEFAULT_DRIVE_DISTANCE)
rosys_1       |   File "/app/field_friend/automations/navigation/straight_line_navigation.py", line 45, in _drive
rosys_1       |     await self._drive_to_yaw(distance, start_position.direction(local_target))
rosys_1       |   File "/app/field_friend/automations/navigation/navigation.py", line 92, in _drive_to_yaw
rosys_1       |     raise TimeoutError('Driving Timeout')
rosys_1       | TimeoutError: Driving Timeout

At what distances does the error occure? Only small ones (< 1-2 cm)? Because that is the accuracy of our RTK...

At what distances does the error occure? Only small ones (< 1-2 cm)? Because that is the accuracy of our RTK...

It occurred immediately after starting the automation, when the roboter tried to drive the first time, then the automation stopped.

We tried to change the deadline from additional 2 to 5 (line 84 in navigation.py)
deadline = rosys.time() + 5

This seemed to work, but we then set the value back to 2 and the robot again seemed to drive as it should. The error still occured but I logged the error instead of raising it to keep the automation running. So, no big insights as it seems.

@rodja I saved some logs for this and the distances are indeed in the millimeter range.
rosys_1       | 2024-07-19 15:34:57.254 [ERROR] field_friend/automations/navigation/navigation.py:93: Driving Timeout at startpoint: Point(110.250, 88.245) with yaw: 6.283185307179586 and target point: Point(110.256, 88.259)
rosys_1       | 2024-07-19 15:34:59.263 [ERROR] field_friend/automations/navigation/navigation.py:93: Driving Timeout at startpoint: Point(110.256, 88.259) with yaw: 6.283185307179586 and target point: Point(110.260, 88.275)
rosys_1       | 2024-07-19 15:35:01.274 [ERROR] field_friend/automations/navigation/navigation.py:93: Driving Timeout at startpoint: Point(110.260, 88.275) with yaw: 6.283185307179586 and target point: Point(110.263, 88.291)
rosys_1       | 2024-07-19 15:35:03.278 [ERROR] field_friend/automations/navigation/navigation.py:93: Driving Timeout at startpoint: Point(110.263, 88.291) with yaw: 6.283185307179586 and target point: Point(110.264, 88.306)

for example Point(110.250, 88.245) to Point(110.256, 88.259)

I hope that https://github.com/zauberzeug/field_friend/pull/130 will fix this issue. It only performs GNSS updates between when standing still. That means that we drive 100 % by odometry data.

We figured out that the Driving Timeout occurs when the odometry heading is above 180 deg or under -180 deg.

This should be fixed with #130. I guess it is already tested on real robots today. Can we close this @LukasBaecker?

@rodja I would like to add a test for this case to make sure that the robot acts as expected when the heading is >180 or <-180.


unblock 3rd party launcher downloads

May I ask why this mod was blocked for third-party launchers? I can only assume it was so that CF's download statistics are not messed up. Can this mod be unblocked? Many people don't, or straight up can't use Overwolf's launcher due to privacy concerns, and the fact that it is not available for linux (it only supports WOW). Due to this people have to manually download this mod everytime from the website (which, imo, is pretty meh) and forgo automatic updates for good.

Here's a more detailed explanation of some of the downsides to this setting:  https://gist.github.com/copygirl/7d45bad739453d2be61138cebafce04c

Disabling 3rd party downloads doesn't magically give your mod DRM. Anyone can still go to the website, download the mod, and "steal" it, putting it up on 3rd party websites or just re-host it to make the experience smoother for their players. (For example, when hosting a private server.)
On the flip side, if you enable 3rd party downloads, you allow people to download your mod from the CurseForge platform. Presumably this still counts towards the download statistics (though I'm unsure), and there's less reason to re-host your mod off-site. You also do not lose out on the people simply avoiding your mod because you make it less available.
Again, by disabling 3rd party downloads, what you're saying is basically "use the official CurseForge client or get lost". I doubt there will be a lot of people that will go back to CurseForge just because some mods make their gaming hobby slightly more cumbersome, as they probably have bigger reasons why they don't use it in the first place, or a use-case that's not supported by it at all.
You're not going to get more reward points because you restrict downloads.
^ copied from the gist


Migration failed by "error in table task after rename: duplicate column name: message"

Gitea Version
1.15.4
Description
Many users report that the migration fails:
2021/10/16 08:45:14 ...ations/migrations.go:422:Migrate() [I] [SQL] ALTER TABLE `task` RENAME COLUMN errors TO message [] - 6.592953ms
2021/10/16 08:45:14 ...ations/migrations.go:422:Migrate() [I] [SQL] ROLLBACK [] - 113.064µs
2021/10/16 08:45:14 routers/common/db.go:33:InitDBEngine() [E] ORM engine initialization attempt #1/10 failed. Error: migrate: do migrate: error in table task after rename: duplicate column name: message
2021/10/16 08:45:14 routers/common/db.go:34:InitDBEngine() [I] Backing off for 3 seconds
2021/10/16 08:45:17 routers/common/db.go:27:InitDBEngine() [I] ORM engine initialization attempt #2/10...

Removing the message field in task table resolves this problem and can complete the migration.
The problem seems to be caused by Gitea accessed the task ORM too early (before migration), so the task table was changed (message was added while error also exists) before the migration and then the conflict occurs.

I don't understand where this could be happening - we'd need to be calling Sync2() before the Migrate function runs but I can't find any example of this.
The interesting thing is that not every user reports this - which suggests that whatever is going on is either some kind of race or it's related to something else.

Yep, I cannot reproduce this bug either. One user was using pgsql while another was using sqlite3. My only guess is whether there is some code triggering task early before a long running migration finishes.

Just to record here: we have an issue tracking this problem

https://github.com/go-gitea/gitea/issues/17531


Nuxt3 implementation

How to use it in nuxt3?

Inside a folder named "plugins" on the root of the project. You can paste a code like this:
`
import CircleProgress from 'vue3-circle-progress'
export default defineNuxtPlugin(({ vueApp }) => {
vueApp.component('CircleProgress', CircleProgress)
})
`
And its done. Just use the component normally


Add dbt/include/sqlite/profile_template.yml

See https://docs.getdbt.com/docs/contributing/building-a-new-adapter#other-files
Couldn't figure out how to do the schemas_and_paths and extensions parts
fixed:
  type: sqlite
  threads: 1
  database: "database"
  schema: "main"
prompts:
  schemas_and_paths:
    main:
      hint: '/my_project/data/etl.db'
  schema_directory:
    hint: '/my_project/data'
  extensions:
    - "/path/to/sqlean/crypto.so"

Hey @codeforkjeff! I see you started implementing features from the more recent adapter docs 👍.
I opened https://github.com/dbt-labs/dbt-core/issues/4462 and will make a PR if they're interested 🤞.

@edgarrmondragon wow, thank you so much for doing that!


MS Defender is flagging this as a PUA:Win32/Puamson

I'm sure that it's a false positive, but I wanted to flag it anyway:
Zip archive: https://www.virustotal.com/gui/file/2a69e746f280fe6aa1061c4219d35ff2ddcf4af2eacda4584da1a3cafee05fa8
Individual EXE: https://www.virustotal.com/gui/file/f0842bd0a5d8ea545edd8f8ebaf193e478da372aa3674db13f818324f401853e
EDIT: I've reported the executable as a false-positive to https://www.microsoft.com/en-us/wdsi/filesubmission/

If I gave them the benefit of the doubt then perhaps this is an automated response, or has some legitimate reason that I haven't thought of. I'm personally suspecting that they just don't like competition, and don't like their spyware being blocked

I don't know what they have, but it's starting to get on my nerves.


auxpow support

Is there any support coming for auxpow? If not then any hints on best practices to integrate into your codebase?

Just need to parse and possibly validate POW. Its pretty easy to parse, I have it working with tests passing in my fork but I think an abstraction so that blocks are processed according to the test on if auxpow is present (version bits would tell us). That would be ideal so it becomes chain agnostic.

What exactly is the use case of this and how big would the change be? It sounds like it's something to support other crypto currencies? If that's the case we'd really want to limit the scope of the changes.

the rust bitcoin crate has enough functionality to parse out auxpow headers, you just can't use the block parsing function directly. you have to parse it piece by piece. I've already written code to parse out auxpow headers in dogecoin for one of my own projects, and I'd be happy to pr it in if it's wanted.

It sounds like it would be reasonable to create a separate crate for these altcoins that reexports some of rust-bitcoin's types and adapts it where necessary (e.g. adding auxpow support). The burden on the rust-bitcoin maintainers seems too big otherwise since someone had to read up on the respective standards.
If there are certain design choices that make adapting it hard/impossible I'd be much more open to revisiting these. If extending the library is hard that's probably something we want to fix.

Closing, please let us know if library ergonomics are non-optimal.


default.wallet location issue

Found a wallet issue when creating an account.
$ dune --start test_node
Creating docker container [dune_container]
Creating node [test_node]
Using Configuration [/home/www-data/config.ini]

$ dune --create-account nodeone
Creating account [nodeone] with key pair [Private: 5K4GCQPREhc6HmJ2wWNqRHvVNSL1bZ79hu8grtmkUhGJcndUfMg, Public: EOS8DMcuK28sN7jw8Uj5gEKtH8JxdbhovhVkDaUoQAemo49RBse97]
Error 3120006: No available wallet
Ensure that you have created a wallet and have it open
Error Details:
You don't have any wallet!
Stack Trace:
wallet_manager.cpp:140 get_public_keys

In my analysis, this is caused by the script setup_system.sh which creates wallet run as root permission by the Dockerfile, and eosio-wallet is generated under /root.
But the dune script is running as the user www-data so that it is trying to find default.wallet from /home/www-data.
This is the wallet location just after run the bootstrap.sh and create the container.
$ docker exec -u root -it dune_container ls -alh /root/eosio-wallet
total 16K
drwxr-xr-x 2 root root 4.0K Jul 15 12:48 .
drwx------ 1 root root 4.0K Jul 15 12:48 ..
-rw-r--r-- 1 root root 2.9K Jul 15 12:48 config.ini
-rw------- 1 root root  311 Jul 15 12:48 default.wallet
-rw-r--r-- 1 root root    0 Jul 15 12:48 wallet.lock
$ docker exec -u root -it dune_container ls -alh /home/www-data
total 16K
drwxr-xr-x 1 www-data www-data 4.0K Jul 15 12:49 .
drwxr-xr-x 1 root     root     4.0K Jul 15 12:49 ..
-rw-r--r-- 1 www-data www-data  621 Jul 15 12:49 config.ini
drwxr-xr-x 2 www-data www-data 4.0K Jul 15 12:49 nodes

I tried to make a PR but it looks a bit complex as a user that it may related to permission issue and other features such as export/import wallet.
so I'm just leaving commands for somebody who need a simple workaround as below. You can run it just after bootstrap.sh completed.
$ dune --create-account <username> # this will fail but generate eosio-wallet structure under /home/www-data.
$ docker exec -u root -it dune_container cp /root/eosio-wallet/default.wallet /home/www-data/eosio-wallet/
$ docker exec -u root -it dune_container chown www-data:www-data /home/www-data/eosio-wallet/default.wallet

Thanks.

This should be resolved as of v1.0.0-rc1


Revert "[SMALLFIX] Merge conf address with server address"

Reverts Alluxio/alluxio#13883
Trigger merge by mistake.

LGTM, revert the unintended commit

alluxio-bot, merge this please


LW-11276 Update configuration to use Lace PostHog proxy

Checklist
Proposed solution
This PR is best reviewed as individual commits, since there's a refactor of the variable name first, then the value change.
Testing
Make a dev build then observe the HTTP requests to https://e.lw.iog.io/ succeed, and find no requests going to https://eu.posthog.com/

Allure Report
allure-report-publisher generated test report!

processReports: ❌ test report for 417593e2

passed
failed
skipped
flaky
total
result

Total
29
3
0
0
32
❌


Remove token got out of memory error

Test failure because of running suite teardown with remove token failed.
Error message OSError: [Errno 12] Out of memory.
This issue only occurred on x86_64 with security test.

Run tests with security-enabled, the edgex-taf-common container memory usage grow up to 500MB. Without security-enabled only used around 120MB until the test completed.

The issue occurred because HTTP or HTTPS session is created before sending API, but not closed after that.


Text overflowing inside tooltip

Changing parent container to another div results in tooltip ignoring placement prop and text inside overflowing

Please provide a reproduction so I can check your HTML/CSS.


Revert "Update packagecontroller install command for registry mirror"

E2E seems to be failing because of aws/eks-anywhere#4797. Revert while we investigate.

/approve
/lgtm


Fixed 'pokemon_caught' event

Short Description:
Fixes "catch error 2" appearing in telegram instead of correct catch message.
Fix removes a lot of redundant code. Tested with no errors.
Fixes/Resolves/Closes (please use correct syntax):

#5533

DO NOT MERGE... minor bug-fix to come.

pokemon_caught needs additional logic so it can be limited to only specific conditions (iv>x, cp>y etc.)
as for the other ones... shrug. Someone's personal formatting preference?

OK this should be right to merge now.

Should be OK to merge now

👍


Version >0.6.0 breaks query parameters

I haven't done extensive testing yet, but it seems like version >0.6.0 breaks query parameters as described in the documentation (https://starlite-api.github.io/starlite/usage/3-parameters/#query-parameters). It gives 404 without every executing the function.
class ApiV1Controller(Controller):
    path = "/api/v1"

    @get(path="/product/{isin:str}/rawdata")
    async def product_rawdata(self, isin: str, dataType:  Literal['profile', 'etc']) -> Any:
        raise KeyError("Test")

with create_test_client(ApiV1Controller) as client:
        print(client.get("/api/v1/product/test/rawdata").text)
        print(client.get("/api/v1/product/test/rawdata?dataType=profile").text)

Output (1.2.0):
{"detail":"Missing required parameter dataType for url http://testserver/api/v1/product/test/rawdata","extra":null}
{"detail":"Not Found","extra":null}

Output (0.6.0):
{"detail":"Validation failed for GET http://testserver/api/v1/product/test/rawdata:\n\ndataType\n  none is not an allowed value (type=type_error.none.not_allowed)","extra":null}
Traceback (most recent call last):
...
    raise KeyError("test")
KeyError: 'test'

UPDATE: seems like it does run the function, but fails with 404 if there is a KeyError; I've updated the example. This might be intended behavior but it's very confusing since it also doesn't log anything on the server-side.

Hi, it should return a status 400 not a status 404. Can you add a test marked by @pytest.mark.xfail?

thank you @i404788 . V1.2.3 has been released with a fix. Please see if it resolves your issue and if so close this issue.


use aix stats implementation for hpux as well

Added test for aix stats.

@Anirudh-Gupta thanks. I am going to fix the tests on appveyor. Once I've done it, lets rebase this PR and merge.

@Anirudh-Gupta I fixed the tests, could you please rebase on the latest master? That should give you a green light.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@arlimus

Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

@chris-rock : rebased it to latest master.

Thanks @Anirudh-Gupta


running on mac.

error[E0432]: unresolved import `metal::CoreAnimationLayer`
  --> crates/libs/vulkan/src/utils/platforms.rs:19:5
   |
19 | use metal::CoreAnimationLayer;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `CoreAnimationLayer` in the root

error[E0405]: cannot find trait `EntryV1_0` in this scope
  --> crates/libs/vulkan/src/utils/platforms.rs:76:33
   |
76 | pub unsafe fn create_surface<E: EntryV1_0, I: InstanceV1_0>(
   |                                 ^^^^^^^^^ not found in this scope

error[E0405]: cannot find trait `InstanceV1_0` in this scope
  --> crates/libs/vulkan/src/utils/platforms.rs:76:47
   |
76 | pub unsafe fn create_surface<E: EntryV1_0, I: InstanceV1_0>(
   |                                               ^^^^^^^^^^^^ not found in this scope

warning: unused imports: `Entry`, `Instance`
 --> crates/libs/vulkan/src/utils/platforms.rs:2:11
  |
2 | use ash::{Entry, Instance};
  |           ^^^^^  ^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

Some errors have detailed explanations: E0405, E0432.
For more information about an error, try `rustc --explain E0405`.
warning: `vulkan` (lib) generated 1 warning
error: could not compile `vulkan` (lib) due to 3 previous errors; 1 warning emitted
warning: build failed, waiting for other jobs to finish...

Somehow when I run cargo run or build, it failed to build with those messages.

I have never tested the code on Mac. Honestly I stole this piece of platform code from somewhere I don't remember. I should have deleted it. From the error message, it seems that  pub unsafe fn create_surface<E: EntryV1_0, I: InstanceV1_0> should be renamed to match the imports.
However, even if this part of the code gets fixed, this project still won't work on Mac because it uses Nvidia extensions of Vulkan for GPU ray tracing. As in the README, the ideal platform of this project is Linux(didnt test it on Windows) with a Nvidia RTX GPU.

Thanks for the fast feedback.
If it has been tested only on linux, can I do it WSL because i have another box at work which has RTX 3080 but it runs windows

WSL may work but it wont be easy.
Acutally Windows does work, see this: https://github.com/KaminariOS/rustracer/issues/9#issuecomment-1545267587.
He mentioned that he got it to work on Windows easily.
I never tested it myself because I don't use Windows.

Thanks..I will test it


Dialog Boxes force focus

Dialog boxes such as the one pictured below, even though there is no edit box, appear to consume key inputs and stop me from moving my character or typing anything.

Messing with the code a little the following dialog setting appears to be the culprit dialog.enterClicksFirstButton. If this is set to true then key presses are consumed, if it's set to false then I can still move my character while dialog box is on screen.
The reason I came across this was because I started using this WA https://wago.io/Mfp9UONoB which automatically swaps profiles when in certain locations and requests a reload using SAM's internal function ShowLoadProfileAndReloadUIDialog. I often find myself entering a zone and not wanting to reload straight away but first move my character to a safe spot, or I'm just entering a zone for a second and then leaving again. But I've noticed multiple times I try to move and can't because of key presses being consumed by the open dialog.
The solution to this might just be "deal with it" or "close the dialog before you move" and I'm ok with that but just thought it was odd and worth mentioning since I haven't seen this behaviour from many other addons before.
Note:
I haven't tested it much but I believe dialog boxes with editboxes such as the rename box force focus as well.
I.e., you cannot type in chat, move character, cast spells, etc. All keypresses are consumed by the editbox even if you try to click away from it.

That's working as intended, it needs to consume the keyboard to listen for the ENTER key to confirm the dialog. (enterClicksFirstButton)
I can add a parameter in that function to disable this.

Completely up to you.
I only posted because I hadn't seen this behaviour doesn't seem like standard practice for WoW addons. I haven't noticed it before (not that I really looked for it) and thought it might've been unintended. I'm happy either way. 👍


SEMMEDDB & Publication Type

In the translation step, pull across the Publication type from Medline so it can just be used later on.

I believe this is already being done.


Fix repeated appending of patch/diff links to commits

This is a fix to close #135.
Checks if there are links and doesn't add them if there are.

LGTM :+1:

@paulmolluzzo Thanks! We need to think more about back-and-forward navigation unfortunately. This fix is similar to #116. We can try to unify these checks somehow so it's easier for new DOM appends to re-use it and not discover repeated DOM bugs later.

It'll be tough to abstract it out, we use so many variations of appending. I think following a pattern like in this PR is just going to have to be kept in mind. "Check if it exists before you append."


feat(bind): factory with nested keys

A WIP to explore @voliva suggestion's  on this comment of #77

After the offline conversation that we've had, I had an idea to support optional args (and undefined values). I've put that change in a separate commit so that it's easier to appreciate what the trick is about 😄


Something wrong with the parentheses

Hello,
please review this string: "Example : user is performing certificate-based authentication (CBA) and no certificate is sent (or Proxy removes) the users certificate in the sign-in request."
I think it should be "Example : user is performing certificate-based authentication (CBA) and no certificate is sent (or Proxy removes the user's certificate in the sign-in request)." Also 'users certificate' should be 'user's certificate'
Kind regards,
Anne H., QC

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

ID: a826ee6f-f457-7109-9f77-67c57977d4e7
Version Independent ID: 11766f27-492e-a579-dced-8a42528cbb47
Content: Microsoft Entra authentication & authorization error codes - Microsoft identity platform
Content Source: docs/identity-platform/reference-error-codes.md
Service: identity-platform
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@QueryCoordinator
Thanks for your feedback! We will investigate and update as appropriate.

@QueryCoordinator
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


Spelling

This also seems to be a typo:
result = task.outout.fetch().get_bytes()

https://github.com/substantic/rain/blob/master/README.md#L83
and
https://github.com/substantic/rain/blob/master/docs/guide/quickstart.rst#L56

Thank you for your report.


[Feat]: watchFocus option

Hi David,
Firstly, thank you for an awesome package!
I went more in depth regarding my issue in this discussion:

https://github.com/davidjerleke/embla-carousel/discussions/936

Essentially I need a way to override the default slide focus behaviour for some accessibility work I've been doing.
A watchFocus option feels natural to me but curious to hear your thoughts.
Cheers,
Sam

Closes:

#936
#764
#642
#822
#854

Thanks for your contribution @S-Shingler 👍🏻,
I’m on vacation so I will review and test this when I’m back. Thank you for your patience.

No worries, enjoy your vacation!

Hi @Mitch-At-Work,
Thanks for your input. I think it's better to create a separate discussion if you're unsure about how the current focus behavior is operating. By all means, what you're mentioning could be a bug but it could also be by design and you might be misunderstanding the feature.
I think it makes sense to not aim for just opting out of this feature if it's causing you trouble, but rather creating a discussion with a CodeSandbox along with clear steps to reproduce the behavior you think is problematic. This way, if it turns out to be a bug, we can fix the bug and improve the library. If not, you might understand why it works the way it does.
With that said, this feature is on the roadmap and I will review and test this PR as soon as possible so it's upcoming:

#841

Note to self:
Test focus behavior for:

AutoScroll with links #764.
Fade.

Hi @S-Shingler,
I've made some modifications in order to align the watchFocus option structure with the other watchers like watchResize, watchDrag and watchSlides. I think this feature is ready for a release but I would appreciate if you would try it out before we do so I haven't missed anything obvious.
In you local environment, you can try any of the three playgrounds and test the new feature out:

yarn start:vanilla (starts the vanilla playground)
yarn start:react (starts the react playground)
yarn start:solid (starts the solid playground)

All environments live in this folder: <your_root_folder>/playgrounds/. Let me know how it goes!
Thanks in advance.

Hi @davidjerleke,
Everything is looking good.
Cheers,
Sam

@S-Shingler this feature has been included in the v8.2.0 release.

@S-Shingler, @Mitch-At-Work, this feature has been included in the v8.2.0 release. Thanks a lot for your contribution 💫!

That's awesome, thank you! @davidjerleke


fix: [POC] isFuncationAsync AST

Pull Request Template
Use this template to quickly create a well written pull request. Delete all quotes before creating the pull request.

Description

Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change.

Fixes # (issue)

if no issue exists, please create an issue and ask the maintainers about this first

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
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

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.

Test A
Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

Closing this as there was already a PR created for this in past and was closed by me which could be continued. https://github.com/appsmithorg/appsmith/pull/15092


Feature/calibration input validation

Project Robyn
Summary of Changes
This PR introduces a new CalibrationInputValidation class and corresponding unit tests to ensure the validity of calibration input data in the Robyn project. The validation checks include:

Date range
Lift values
Spend values
Confidence values
Metric values for each channel in the calibration input
Objective weights validation

Fixes # (issue number, if applicable)
Type of change

[x] feat: New feature (non-breaking change which adds functionality)
[x] test: Additional test coverage

How Has This Been Tested?
A comprehensive suite of unit tests has been implemented to cover various scenarios:

Valid calibration input
Invalid date ranges
Invalid lift values
Mismatched spend values
Low confidence values
Mismatched metric values
Valid and invalid objective weights

The test_validate function provides an end-to-end test of the validation process

In addition to the calibration validation i also added another function check_obj_weights which seemed important. The function implementation is in place and tested with unit tests but not called anywhere yet in calibration. Feel free to move that later to the right spot (maybe some catch all validation class) or remove if not needed.


--defaultchain flag should be removed

--defaultchain flag was removed from the latest fabric. so the docker-composer.yml file should be revised in the configuration of peer0.org1.example.com. the start command can changed from
command: peer node start --peer-defaultchain=false
to be
command: peer node start

Updated fabric-tools for latest fabric v1.1.  Thanks


emails table problem

Using aaa3d715f88a3f0, I notice after initializing with docker that no email table is added to db dev
dev=# \dt
              List of relations
 Schema |      Name       | Type  |  Owner
--------+-----------------+-------+----------
 public | comment_points  | table | postgres
 public | comments        | table | postgres
 public | logins          | table | postgres
 public | migrations      | table | postgres
 public | migrations_lock | table | postgres
 public | stories         | table | postgres
 public | story_points    | table | postgres
 public | users           | table | postgres

...so when I seed the database, I get
Starting 'db-seed'...
error: relation "emails" does not exist
    at Connection.parseE (/usr/src/app/node_modules/pg/lib/connection.js:546:11)
    ...

Relatedly, this problem was causing errors at src/passport, line 80
db_1     | ERROR:  relation "emails" does not exist at character 13
db_1     | STATEMENT:  insert into "emails" ("email", "user_id", "verified") values ($1, $2, $3)

I cannot reproduce this issue:
nodejs-api-starter git:(master) ✗ docker-compose exec api yarn db-migrate
yarn run v1.3.2
$ yarn db-migrate
Starting 'db-migrate'...
Finished 'db-migrate' after 395ms
Done in 0.72s.
$ yarn db-seed
Starting 'db-seed'...
Finished 'db-seed' after 6448ms
Done in 6.80s.

Perhaps you need to nuke your db (or remove all db tables from it) and run yarn db-migrate over again (from inside the "api" container).